#009021: Using undocumented RootNode setting in content.ini causes __1 as node path, corrupting it

I have also posted this on related thread in forum at http://ez.no/community/forum/general/1_or_2_appears_in_url . Copy from there:

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.

Either the above behaviour should be fixed or RootNode and related settings in content.ini should be properly documented. At least a warning should be added as ini comment, stating that strange stuff happens if it is set to anything else than 2.

Version: 3.8.4
PHP Version: php4.4
Webserver: apache2
Database: mysql5