Beautifying URLs, hierarchy, replacing pagealiases and improving security for 2
Posted: Wed Mar 05, 2008 5:59 pm
Hello,
Here is an out of blog followup (of my own) to http://blog.cmsmadesimple.org/2008/02/1 ... ong-again/
I very much welcome all the great work on 2.0 so far : I'd like to thank all the devs.
I have been very pleased by the reply from Maki (February 19th, 2008 at 2:47 pm) about pretty URLs and Ted's agreement to the idea. I have read the point raised by Sandro (February 20th, 2008 at 9:14 am) stating that third party code (modules) could heavyly rely on the old $node->alias trick and I'd like to share here a though about all this :
I'm not a programer and I don't know CMSms internals. I respectfully suggest(*) to the dev team that (as 2.0 opens a new era) there should be a new $->url field computed by hierarchy and the $->alias field aside should be deprecated (still useable but moduls should update to the new url).
Pros :
-each page (somewhat a leaf in the web semantic) is mapped to a unique pretty URL (hey... website, isn't it ?-)
-the list of legitimate URLs can be generated (select url from page) and allowed by .htaccess (all others denied)
Yes, there are some corner cases like pseudo-pages (/news/date1/blah2, /news/date3/blah4 etc) and uploaded files but these are easy to filter too.
Hope this helps thinking how to replace the old $->alias The Right Way(TM). Have fun designing and coding 2.0
Pierre
(*)This is a friendly message. I'm not mastering English. I hope it is clear I don't tell you what to do.
Here is an out of blog followup (of my own) to http://blog.cmsmadesimple.org/2008/02/1 ... ong-again/
I very much welcome all the great work on 2.0 so far : I'd like to thank all the devs.
I have been very pleased by the reply from Maki (February 19th, 2008 at 2:47 pm) about pretty URLs and Ted's agreement to the idea. I have read the point raised by Sandro (February 20th, 2008 at 9:14 am) stating that third party code (modules) could heavyly rely on the old $node->alias trick and I'd like to share here a though about all this :
I'm not a programer and I don't know CMSms internals. I respectfully suggest(*) to the dev team that (as 2.0 opens a new era) there should be a new $->url field computed by hierarchy and the $->alias field aside should be deprecated (still useable but moduls should update to the new url).
Pros :
-each page (somewhat a leaf in the web semantic) is mapped to a unique pretty URL (hey... website, isn't it ?-)
-the list of legitimate URLs can be generated (select url from page) and allowed by .htaccess (all others denied)
Yes, there are some corner cases like pseudo-pages (/news/date1/blah2, /news/date3/blah4 etc) and uploaded files but these are easy to filter too.
Hope this helps thinking how to replace the old $->alias The Right Way(TM). Have fun designing and coding 2.0
Pierre
(*)This is a friendly message. I'm not mastering English. I hope it is clear I don't tell you what to do.