content structure menu in admin interface empty

Thursday 26 June 2008 11:06:13 pm

We're using 3.10.0 (recent upgrade from 3.9.4) and on my development installation I can see my admin left content structure menu just fine. But on the same server I have a staging installation, and the menu has no nodes. Same is true on the production (remote) server. PHP is not running as CGI. Apache sites-available entries are identical except for paths and server names/aliases. I've got dynamic set to disabled on both. The two installations use separate databases, but the root node is, of course, 2 on both. contentmenustructure.ini's are identical. Cleared caches --clear-all and --purge for both. No error or warnings get noted. URL alias-related problem? Where do I look next?

Many thanks!

Granite Horizon, Certified Developer of eZ Publish Web Solutions
Provider of the SaaS Solution Granite Horizon In The Cloud | http://granitehorizon.com/cloud
http://granitehorizon.com | +1 916 647 6350 | California USA | @granitegreg
Blog: http://granitehorizon.com/blog

Friday 27 June 2008 7:15:23 am

Thank you. Yes, I had forgotten to mention that neither have .htaccess (not necessary if you have access to the /settings/sites-available files, I thought).

I had tried:
RewriteRule content/treemenu/?$ /index_treemenu.php [L]
in the apache2 sites-available entry on the testing server to with no effect (either dynamic disabled or enabled, clearing caches with --clear-all --purge each time).

I had also tried adding the .htaccess_root to the testing installation, both with and without dynamic enabled, clearing caches fully both ways--again, it didn't help.

Other thoughts?

Granite Horizon, Certified Developer of eZ Publish Web Solutions
Provider of the SaaS Solution Granite Horizon In The Cloud | http://granitehorizon.com/cloud
http://granitehorizon.com | +1 916 647 6350 | California USA | @granitegreg
Blog: http://granitehorizon.com/blog

Friday 27 June 2008 3:13:03 pm

It appears the solution was in fact to republish the root node. I had done that, and cleared the cache with:

$ bin/php/ezcache.php --clear-all --purge

That didn't work, though.

But clearing the cache from the admin interface after republishing the root node did fix it.

My guess is it's a permission problem, and that I needed to run ezcache.php as root. No errors were reported by ezcache.php, however.

Granite Horizon, Certified Developer of eZ Publish Web Solutions
Provider of the SaaS Solution Granite Horizon In The Cloud | http://granitehorizon.com/cloud
http://granitehorizon.com | +1 916 647 6350 | California USA | @granitegreg
Blog: http://granitehorizon.com/blog