I have suddenly encountered a very strange problem. After running my DNN site for years (http://www.thehway.com) I noticed today that if I update a page's settings, that page suddenly stops working from the main menu's navigation; the menu item itself still displays, but clicking on it doesn't load the specific page. I can update page content just fine, but if I update a page's settings (such as the page name or description), that page continues to display within the main menu navigation but when I click on it nothing happens. 

For example, I've been running the page at http://www.thehway.com/Overview/WhyTu... for years, and until today it was very easy to click from the navigation's main menu (Overview, Why Turn to Us?). After updating the page's settings, however, now I can't click on the page from the menu system. Note that I can log in, go to Admin / Page Management, right click on the page and select "View Page" and browse the page just fine--I know it's there. I just can't click on it from the navigation system anymore.

Incidentally, the problem seems to now exist across all of my portals (I'm running several dozen). It seems that as soon as I update a page's settings, that page no longer works from the portal's navigation menu. I'm also running a new DNN 7 instance and I tested that as well; the DNN 7 instance works just fine, so it appears that something happened to my DNN 6 instance very recently.

While I've been running this DNN 6 instance for years, I've had two things change recently:

• Upgraded to DNN 6.2.5 (from 6.2.4)
• Upgraded to SQL Server 2008 (from 2005)

Any ideas out there? I poked around in the database directly but didn't discover anything glaringly obvious. The pages are there and I can edit them--I just can't navigate to them once I update their properties.

Oh, if only it were that simple. No, the pages aren't set to be disabled, although that IS the type of behavior I'm seeing. It's as if updating a page's settings somehow tells DotNetNuke to make those pages disabled. Unfortunately, I haven't been able to figure-out what database values are causing this problem, or if perhaps there's some sort of bug in 6.2.5 that's causing my instance to behave like this. Again, the behavior has only manifested itself very recently, and I've been running the instance for years.

I could try upgrading the entire instance to 7.0, but the newer version doesn't seem quite ready for prime time yet.