Share » Forums » Setup & design » content structure menu in admin...

content structure menu in admin interface empty

content structure menu in admin interface empty

Thursday 26 June 2008 11:06:13 pm - 5 replies

Author Message

Piotrek Karaś

Friday 27 June 2008 2:11:34 am

What about .htaccess file entries?

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

Greg McAvoy-Jensen

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

Greg McAvoy-Jensen

Friday 27 June 2008 7:16:15 am

I should have said, "I tried copying .htaccess_root to .htaccess".

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

Greg McAvoy-Jensen

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

Piotrek Karaś

Saturday 28 June 2008 1:04:48 pm

<i>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>
That's true, but then you can still forget about .htaccess files messing things up, for example. Still, that was my only thought.

<i>But clearing the cache from the admin interface after republishing the root node did fix it.</i>
Interesting. It's good to know that this could be a potential solution to similar problems.... weird though... Please share if you discover more.

Cheers,
Piotrek

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu