17488 Posts in 4473 Topics by 1978 members
|Go to End|
18 November 2008 at 9:57pm
If nested urls do become part of the core (as I hope), has there been much thought as to what to do with functions? /page/function wouldn't work too well as sub-pages might step on needed functions (or vice-versa).
Maybe there could be an option to specify how we want functions to be delimited? Some examples would be:
18 November 2008 at 10:04pm
By default, if there is a conflict, the page takes priority over an action. However, if you define an $allowed_actions on your controller (a good idea), any action conflicts found in this will be automatically rewritten.
19 November 2008 at 9:38am
I suggest to introduce a default "index" function to somewhat emulate the standard of delivering an index.html when a directory is called.
A request to root/page/subpage/ would be handled by that default function and simply display the content of subpage (just as root/subpage would do right now), while root/page/subpage/add would execute the specific add function on subpage (root/subpage/add in SS 2.2).
In other words: a slash at the end of the URL simply displays that page, while anything after the last slash is a specific function. This way, pages can be nested as deep as one wants and still have a function, both with pretty and meaningful URLs.
30 November 2008 at 2:35am
Now that 2.3rc1 is out. Has anyone attempted to work with the Sublevel Url issue with it? I have it installed on my test server but obviously the old hack isn't compatible...
30 November 2008 at 7:55am
There is a nestedurl branch in subversion which you can use. I haven't used it, so not sure which core version it is based off of.
That's about it really until it gets merged and made official.
30 November 2008 at 10:31am
ajshort's maintaining the nestedurls branch, and it is based of trunk.
|Go to Top|