Root node of a menu

Previous topic

Setup & design

Next topic

Author	Message
Mathieu Bouquet	Monday 04 June 2007 3:21:58 pm Hi, I am running two different sites on one single 3.9.2 ezPublish (using URI mapping). So, I have http://localhost/index.php/site1 and http://localhost/index.php/site2 I use the same templates for both sites, but I would like to have two different menus (I mean, for the content, not for the design), based on two different nodes. I have seen that there used to be a parameter of treemenu() which could have been helpful in previous versions, but it has been deprecated in 3.9.x. So, what is the new way to specify the root of a menu? I am a beginner in ezPublish, so I have been looking for a solution on the forums and in the documentation for some hours, but I can't find anything related to my problem. I am a little bit hopeless. As I guess it is not so complicated, I am sending an SOS... Thanks in advance.
Greg McAvoy-Jensen	Monday 04 June 2007 4:06:12 pm I've not done this before it looks like the process may be to create a file called <b>contentstructuremenu.ini.append.php</b> in ezpublish/settings/siteaccess/site1. Put this in the file: <?php /* #?ini charset="iso-8859-1"? [TreeMenu] RootNodeID=x */ ?> Replace "x" with the root node ID for site1. Then create a similar file for site2. Then clear the caches. Again, since I haven't done this I don't know if there would be any unintended results. For more information, see http://ez.no/doc/ez_publish/technical_manual/3_9/reference/configuration_files/contentstructuremenu_ini/treemenu/rootnodeid. However, if you just want different sites for different languages only, then see "Using several public siteaccesses" at http://ez.no/doc/ez_publish/technical_manual/3_9/features/multi_language/configuring_the_site_languages. 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

Author

Message

Mathieu Bouquet

Monday 04 June 2007 3:21:58 pm

Hi,
I am running two different sites on one single 3.9.2 ezPublish (using URI mapping).

So, I have
http://localhost/index.php/site1
and
http://localhost/index.php/site2

I use the same templates for both sites, but I would like to have two different menus (I mean, for the content, not for the design), based on two different nodes. I have seen that there used to be a parameter of treemenu() which could have been helpful in previous versions, but it has been deprecated in 3.9.x.

So, what is the new way to specify the root of a menu?

I am a beginner in ezPublish, so I have been looking for a solution on the forums and in the documentation for some hours, but I can't find anything related to my problem. I am a little bit hopeless. As I guess it is not so complicated, I am sending an SOS...

Thanks in advance.

Greg McAvoy-Jensen

Monday 04 June 2007 4:06:12 pm

I've not done this before it looks like the process may be to create a file called <b>contentstructuremenu.ini.append.php</b> in ezpublish/settings/siteaccess/site1. Put this in the file:

<?php /* #?ini charset="iso-8859-1"?

[TreeMenu]
RootNodeID=x
*/ ?>

Replace "x" with the root node ID for site1. Then create a similar file for site2.
Then clear the caches. Again, since I haven't done this I don't know if there would be any unintended results. For more information, see http://ez.no/doc/ez_publish/technical_manual/3_9/reference/configuration_files/contentstructuremenu_ini/treemenu/rootnodeid.

However, if you just want different sites for different languages only, then see "Using several public siteaccesses" at http://ez.no/doc/ez_publish/technical_manual/3_9/features/multi_language/configuring_the_site_languages.

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