Well yeah, its something like that. I'd like to validate that the 'path' exists and is accessible, if thats the correct way of putting it. If validation succeeds, a hyperlink will be generated. Otherwise a URL exception is thrown and will be handled in front controller.
Yes but are these actual directories/ files or are they merely names of entries in your database that simulate a page structure?
eg whyarewehere/philosophy/thequotidian
(set of words chosen to indicate heirarchichal nature of a possible name structure)
I don't see why you cant just show a generic 'page not found' if the page does not exist - i.e. if any item has incorrect wording
That can all be done from your controller - no need to handle in htaccess
Yes but are these actual directories/ files or are they merely names of entries in your database that simulate a page structure?
eg whyarewehere/philosophy/thequotidian
(set of words chosen to indicate heirarchichal nature of a possible name structure)
I don't see why you cant just show a generic 'page not found' if the page does not exist - i.e. if any item has incorrect wording
That can all be done from your controller - no need to handle in htaccess
Well the part of the query contains the controller name, which definitely exists in actual directories. The rest of the query aint associated with directories/files, such as actions and params.
I don't see why you cant just show a generic 'page not found' if the page does not exist - i.e. if any item has incorrect wording
That can all be done from your controller - no need to handle in htaccess
Build a recursive function to see if things are as you expect (in your controller)
Parse query string value pairs as you need either via QSA or your own process
Reply With Quote
Originally Posted by cretaceous
Bookmarks