I went to add a new parent portal to my DNN 4.4.3 production web site and the Add Portal hangs for several minutes and I end up with an un-accessible half completed portal that I have to delete.  No exceptions are logged.

While looked for a 'quick fix" I upgraded a localhost clone of the site to DNN 4.5.5. to see if the upgrade might replace a failing dll or something else and be a "quick fix".

To my surprise my Snapsis "NavList' in the skin that I use to access Admin and Host pages only lists the Admin Pages.  Thinking that this was an incompatability between NavList  and DNN 4.5.5 I switched to the DNN-blue skin and still only can see the Admin Pages and NOT the Host pages.

I need to add the portals to my site for customers so this is important to my and my company. At some point I'd like to upgrade to 4.5.5, but clearly can't if I loose the Host Pages.

Help?

The initial Can't Create Portal  problem appears to work with the DNN template, so I am not dead in the water, but do have to the portals from scratch. I have edit web.config as well as done an app restart.

When I upgraded to DNN  4.5.3 I tested out both creating templates and Portals both on a localhost before the upgrade and on my PowerDNN production site after. So this appears to be something new. 

The PowerDNN support people want to claim that this is a known bug that was introduced in 4.5.4, and hopefully will be fixed in 4.5.6 - go figure, since I am running 4.5.3.  They also suggested that I upgrade my account to a more costly one, I'd like to see how that will fix the problem ;=}

As for the localhost upgrade to 4.5.5 and losing Host, I didn't bother to troubleshoot that yet.

Thanks, for the suggestions.  The portal stuff in DNN always scares me, most people to use it and it doesn't appear to get tested well in the new releases. That is why I always check

Dave,

AFAIR there have been issues in several versions of DotNetNuke with new properties, that were exported, but not accepted during import. Following the latest core changes, I assume, this will be solved in next version (4.6.0)