As posted on the Etcetera forums:
> My problem is this -- about a week ago, we noticed that the> navigation menus that run vertically down the left side of the> page have disappeared ... sort of. The menu can be viewed in> "admin" mode, but not if you're a visitor. I have checked the> obvious -- which includes permissions, and also verified that the> pages are not hidden from the navigation. Everything checks> out. Is there anything else I should be looking for?
I have the exact same problem! It definitely used to work, but now it doesn't - not sure whether it was a recent change that slipped through the testing, but this is affecting our website also and extremely frustrating.
This has manifested itself in a couple of different ways here - so I'm really confused as to what's going on. In one case the user is simply not seeing the navigation item at all - basically the whole nagivation item is invisible (and no html generated for it) as far as they're concerned. They ARE able to navigate directly to that navigation object's url though.
In the second manifestation - the user cannot see several entries in the navigation tree - they simply don't appear for that user. They can navigate to the pages in question - but as there is no other way of navigating the subpages other than the navigation menu then it really screws things up.
In both cases I've had - it's not affected visitor, only registered users - but I guess visitor is simply another user too.
There is a very rare bug that to our knowledge only one other client has seen. Please email me a zipped mysqldump of your database (jt at plain black dot com) and I'll take a look to see if that's it. When you email me that, please provide me with title, url, or anything else you can about the asset that you're having problems with. I'll be able to test and see if this is the same problem or something else.
Please note, I'm not guaranteeing anything. But if this is a bug, and I'm able to duplicate it, then we can solve it.
Interestingly enough, Ive just tried duplicating this on a virtual machine setup here and cannot seem to, even with the same database and same /data directory.
Could it be a dodgy perl module that's causing it (this machine is another debian testing box, but was installed slightly differently)?
Tis wierd.
After looking at your database I can tell it is definitely not the bug that my other client was reporting. Though I didn't look at it in great detail, I don't see any problems with your database.
It very well could be that you're experiencing a bug in a perl module, perl, mysql, or who knows what. I don't know if you've tried deleting your cache or not, but I think that would be prudent as you may have a corrupt file cache.
