This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit

eZ Community » Forums » Install & configuration » node doe not exist (after upgrade)

node doe not exist (after upgrade)

node doe not exist (after upgrade)

Tuesday 16 September 2014 12:13:12 pm - 5 replies


I updated my ez publish from v.4.7 to 5.1. I pointed my DocumentRoot to ezpublish_legacy/folder.

In the site admin, in the dashboard tab and in the content structure tab, the node tree doesn't appear (http://mysite/ezflow_site_admin/content/view/full/2).

Why ?

Wednesday 17 September 2014 7:42:05 am

Hello Dominique,

Normally your DocumentRoot should be set to the 'ezpublish_legacy' folder not 'ezpublish_legacy/folder'.

Here is the official exampel virtualhost configuration for eZ Publish:

If your still having the problem, can you post a screenshot of the error with debug output enabled? Also worth looking at var/log/error.log entries for more information on the problem.

In any case more information would really help troubleshoot this problem.

I hope this helps!


Modified on Wednesday 17 September 2014 7:43:55 am by // Heath

Wednesday 17 September 2014 11:58:52 am

Heath, thanks for your help.

If my DocumentRoot is set to /home/web/my_site/ezpublish_legacy, all is ok. happy.gif Emoticon

If my DocumentRoot is set to /home/web/my_site/web, I have the tree problem.

So, which is the correct parameters to use the new possibilities from ez publish 5 version ?



Wednesday 17 September 2014 12:18:18 pm

It depends on what you want/need:

1. If you point docroot to mysite/ezpublish_legacy, you are in effect using the "pure-legacy" kernel. You have all of the functionality of eZ4, and none of the functionality of eZ5. You run cronjobs and command-line scripts from the mysite/ezpublish_legacy directory as well.

2. If you point docroot to mysite/web, you will be using the eZ5 kernel, which "wraps" the eZ4 one. You will have the eZ5 functionality available (you will be able to develop using Symfony bundles etc). You will need to run cronjobs and command line scripts via the Symfony console command.

For option 2, you will have to set up eZ5 configuration in yml format in mysite/ezpublish/config. This is probably what is missing/broken in your current setup.

Note also that with option 2, if you never use a single eZ5 functionality, you are taking a performance hit on every page. Not a big one, but still it might be useless.

Wednesday 17 September 2014 12:20:55 pm

ps: if you are using option 2 above, and root node is not 2, these are the docs for proper config:

Thursday 18 September 2014 9:40:14 am


My error was due to a rule in my virtual host configuration. With EZ4 config, I was :

RewriteRule ^/([^/]+/)?content/treemenu.* /index_treemenu\.php [L]

I deleted that line and now I have the tree menu with EZ5 configuration.

Thanks you both.



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

36 542 Users on board!

Forums menu

Proudly Developed with from