Seems like you completed the call Charles! Excellent news.
The byproduct is there is even more reason for people to upgrade to 4.3.5 now.

Quite understandable as the export wasn't creating the template properly.

That's why I think this different call: DNNP-3688 is so important. My opinion is that if a portal can't be created properly (from a dodgy template or whatever) then it should not be created. It should roll back as though nothing has happened so no portal and any assoiciated garbage gets created (database/files whatever).

I suppose in addition once the host is informed that the portal cannot be created you could offer reasons why it happened in the error message, and then offer the host another attempt at creating the portal without trapping or rolling back the error (in case they prefer to hack themselves out of the issue, if this is indeed possible). Then again this might not be necessary or a good idea at all (jury is out).

I've updated DNNP-3688 to reflect the recent fix.

Cheers and thanks Charles

Alex

Hi,

That issue was also identified in those posts:

http://dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/106/threadid/33368/scope/posts/Default.aspx

and

http://forums.asp.net/thread/1127519.aspx

I had identified 2 causes of import crash linked to duplicate moduleid:

MultiDefs modules and reference copied modules.

I can not see any reference to the second cause. Was this fixed earlier?

Cheers