I don't know why this is happening, but I do wonder whether having that many levels of "nesting" is a good idea. Is it really necessary, for your site? Have you tried a simpler solution with users and found that they're deeply unhappy? I'd be suprised if anyone really needed that.
Sorry, am a real noobie with SS: the SiteTree::enable_nested_urls(); method is really appealing: is this available in the current stable release, or only in 2.4?
If it is possible to get in the current stable release, is there a module I can/should/need to download? I tried adding the directive listed above to the _config.php with a default install of the latest stable, and understandably it caused a white screen error.
Thanks for the heads up. I've downloaded the branch from http://svn.silverstripe.com/open/phpinstaller/branches/nestedurls/ and am just about to go and get some dependencies (specifically I'm up to getting sapphire).
Again, a bit of a noob question, but is there version parity between sapphire and silverstripe? I've already got sapphire as part of the latest stable build from a couple of days ago, but since the SVN path doesn't include a version number, I'm not sure whether I should be getting a new sapphire (and I think the same will go for TinyMCE stuff I've seen mentioned as a separate external import that's needed later) for this branch, or can I use the sapphire I already have?
Got the nestedurls branch installed, but using the existing sapphire from stable wasn't good enough: the install process happened, but then when it came to loading the page, there are just white-screens and the error:
PHP Fatal error: Call to undefined method SiteTree::enable_nested_urls() in /data/www/silverstripe-nested/mysite/_config.php on line 29, referer: http://silverstripe-nested/install.php
Sorry for peppering you all with these (probably very basic questions): it is just that without hierarchal URLs, I'm going to have to do some massive mod_rewrite experimenting, so I'm keen to get this POC sorted from the nested branch...