You will soon find out if it fails when you do the import. I think it's really dependant on what modules you have installed on your portal. The blog module for instance will generally stop you from importing a template into a new portal.

If the import fails you can generally delete the dodgy portal that has been created by manually adding in a portal alias (anything will do), and then hitting the delete button.

I can't offer any more advise than that.
Let us know how you got on and what DNN versions you used.

Cheers!

Alex

p.s. The good news is that DNNP-3708 has been moved from DNN Core Framework [PUBLIC] forum to the DNN Core Framework forum, so it has at least been observed; although nobody appears to have had the time to look at it yet.

If you download the documentation in the download area the installation guide should answer the question for you. There are some gotchas so look carefully (esp with web.config and file permissions). On the whole the process is pretty straight forward. If you follow the instructions it should simply upgrade the version without any serious issues (chances are there will be a few minor issues). Whatever you do back everything up including the database.

This is just my personal opinion but you might do better waiting for the 4.3.5 stability release before you decide to upgrade (maybe even 4.3.6). I think that the software is still too buggy at the moment, but it will be the best thing since sliced bread once all the issues are ironed out. Then again you may have to upgrade because 4.3.4 contains a major security update. Only you can assess that and I have no idea when these updates are to be available (although at the moment it appears we are getting a release every month or so).

Cheers

Alex

Wonderful news. Thanks Charles.

I really hope the fix is in the next release. For me and a lot of people it's already broken and I can't go live until this issue is fixed. My business model heavily relies on this functionality.

Perhaps in the meantime you could support two different types of portal templates when exporting? One legacy and one with the improved fixed version. Have a tick box say for "Legacy template, supports 4.3.4 and below". You could get rid of this on the next DNN major release.

Perhaps you could introduce an XML header tag in the template file that shows the version number of the template so that DNN would able detect what that file is and how to parse the XML file upon import. That way if the issue reoccurs on future releases there could be a way of avoiding the breaking of the functionality.

Additionally you could give the template file format a different file name extension (say .template2), that way the earlier versions won't be able to see it when trying to import it.

Also could this help: on future releases?: DNNP-3688. This could help make sure that nothing gets broken if the wrong type of file gets imported.

I'm on tender hooks here, it's make or break for me. I really hope you can fix it for this version (no pressure :)

Thanks

Alex