__1 or __2 appears in url

Tuesday 05 September 2006 2:13:26 am

Hi,

I'm not involved in this stuff but maybe you will find a solution here:
http://ez.no/community/forum/general/getting_rid_of_1_in_urls
http://ez.no/community/forum/developer/whats_1_in_url
http://lists.ez.no/pipermail/sdk-public/2006-July/002183.html
http://lists.ez.no/pipermail/sdk-public/2006-July/002184.html

Best regards,
Sveta

Tuesday 05 September 2006 6:42:22 am

Hello, (I Work with Sébastien on this issue),

on ezpublish Sdk-public mailing list, somebody told us the problem comes from this part of code in the function pathWithNames in kernel/classes/ezcontentobjecttreenode.php :

$ini =& eZINI::instance( 'content.ini' );
$contentRootID = $ini->variable( 'NodeSettings', 'RootNode' );
if ( $node->attribute( 'node_id' ) != $contentRootID )
{
<snip>
}
else
{
  $nodePath = '';
}

because when somebody edit the root node, it is like having an empty name on the root node.
If I edit the root node (change name 'ezpublish' to 'Home page' for ex.) I can reproduce the bug on an ezp 3.8.3 installation but on another server with ezp 3.8.1, there is no problem.
Do you know why and how to repair it ?

Thanks for help

Friday 15 September 2006 6:05:53 pm

I have a experience which is related to above problem i think.

I am setting up a multisite system on one database.

Each subsite gets assigned a separate subtree and siteaccess. IndexPage, DefaultPage and PathPrefix are used to make each subsite to start on its own indexpage and to remove /subsitename/ path from URLs.

Also I did set RootNode in content.ini to point on the subsite indexpage, as I thought this was its function. That ini setting is totally undocumented though. I was using it in templates to make menus start at right level etc.

However this appears to have been a mistake. At first look everything worked fine until I edited the subsite root page (in user siteaccess, where RootNode setting was in power. After that the path for all nodes in subtree was broken. Subsite root that used to be "/subsite/rootpage" had become "__1" and pages under it "/subsite/rootpage/subpage" -> "__1/subpage" etc.

The mangled paths can be fixed again by editing that node in admin where RootNode still points to 2.

Apparently the RootNode setting should not be used by developers for anything at least until its function is documented and clear. I will also file a bug on this.

Certified eZ developer looking for projects.
zurgutt at gg.ee