I am taking a lot of heat for this. After upgrading DNN 05.06.03 to 06.00.02, my child portal menus, in the child portals, sometimes direct to the page, but on the parent portal.


Here is my portal setup.


Parent Portal
http://www.parent.com/


Child 1
http://www.parent.com/child1/


Child 2
http://www.parent.com/child2/


Sometimes, not always, all the menu links in a child portal, will direct the user back up to the parent portal.


So, a top level Menu item, Events, that should go to http://www.parent.com/child1/events.aspx will take the user to http://www.parent.com/events.aspx.


This seems to happen after the web site has been running for 12-24 hours without intervention. To fix it, I have to either restart the server, or host admin restart the application. The second option doesn't always work.


Is there anything I can do? I'm afraid that if this isn't fixed that my superiors will start talking about other CMS's.

This issue has been making me think it's a cache problem, so I went looking at various cache settings. 

I found that the scheduled task to purge cache was disabled. From what I can tell, this scheduled task is enabled by default. I know I didn't disable it, so would the DNN6 upgrade disable it?

DotNetNuke.Services.Cache.PurgeCache

Bump...

Had to revert to 5.6...