Hello and thanks for reading.

I have a DNN 6.1.5 site that has some structure to it. When I export with content to a template file, the correponding .template and .resources files are created. If I unzip the .resources file I can see there are Export and Images folders that contain assets I have used to build this site. In the Export folder there are .xml files for each Tab that I have created (e.g. content.DNNHTML.ArticlesTabContent.xml). Most of these items are prefaced with "content.DNNHTML" and all and with ".xml" suffix. If I look into these XML docs, I can see the HTML that I've produced in a corresponding CDATA structure.

If I then look into the corresponding .template file, there is no reference to any of these tab files. As such, when I either a) Create a new site with this template, or b) Use the Site Wizard with this template, the new site is not correctly generated. I have used a Source installation of DNN 6.1.5 to debug the import of the template and I can see that it is expecting tabs and panes in certain areas of the import. The <tabs /> section of the template file is empty so this behavior is inline with what I'd expect to see.

Steps to reproduce:

1. Create site from Default template.
2. Add some basic HTMLPro modules and change the content within them.
3. Use the Export Site Template wizard with "Include Content" checked on.
4. Create a new site selecting the corresponding just-exported site template. NullReferenceException.
5. Create a new site selecting the default.
6. Use the Site Wizard to apply the just-exported site template to it. Critical Error.

I checked Gemini just to be certain I didn't miss any "fixes" that may already apply but nothing stood out. Any help would be appreciated.

Thanks much!

Chris,

Thanks for your reply. By the way, your DNN tutorial videos are some of the best instructions out there for using DNN. Very clear and very useful.

Unfortunately I am unable to simply upgrade my version of DNN from 6.1.5 to newer or even latest, although it is something we are considering further down the project path. In the meantime this is the version I need to work with. While I don't expect code to be fixed that may already be improved, I'd like to know if this was a problem someone else dealt with, and if so, how they dealt with it. 

Really, my single question is this: If the template export completes successfully but doesn't include in it any tabs, therefore no panes, therefore no modules, what are some things that I should look at when I know these things exist in my portal/site?

Thanks much.