Hi Joe, What other urls is your site going to have?
If you are also going to have any other 'base' urls (http://www.example.com/about) and unknown usernames (which is assumed) then you will find it hard to create a route that will allow you to cater for your other controllers/pages as well as a username. How are you structuring the controller and method that will return the results for the example url? It may be easier to hijack the url in the bootstrap, and modify it if it matches a regex so that http://www.example.com/username/2006-5-7/post-title-goes-here/ becomes /controller/method/username/2006-5-7/post-title-goes-here/ and http://www.example.com/about is left as is. Or are you looking for something that will assume it is a username if it doesn´t match a pre-existing route? In this case you could create your own error controller and based on the url either requestAction (/controller/method/username/2006-5-7/post-title-goes-here/ ) or fall through to real error messages. HTH, AD7six --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
