Another thing that needs to be pointed out (at least this is the case in Windows) that modifications to this file require a full web2py server shutdown/restart. If you use the tk UI to "stop" server and then "start" server, it will not pick up changes in the file -- perhaps this is obvious to some, but it can throw people in a loop if they are not aware.
On Fri, Mar 16, 2012 at 11:09 PM, Anthony <abasta...@gmail.com> wrote: >> ok removing those and re-starting web2py worked (well it broke, but that's >> a good thing). Thx all for your help. If it's not on to-do list: maybe it >> should be to improve (or to make clearer in the docs) how the routes.py >> works and that you need to comment our routes_app in order for it to work. > > > Maybe we could make the sample file more clear, but I think the book has it > right: > > Application-Specific URL rewrite > > routes_app > When using the pattern-based system, an application can set its own routes > in an application-specific routes.py file located in the applications base > folder. This is enabled by configuring routes_app in the base routes.py to > determine from an incoming URL the name of the application to be selected. > When this happens, the application-specific routes.py is used in place of > the base routes.py. > > The format of routes_app is identical to routes_in, except that the > replacement pattern is simply the application name. If > applying routes_app to the incoming URL does not result in an application > name, or the resulting application-specific routes.py is not found, the base > routes.py is used as usual. > > > > Though that last half sentence may not be correct (rather, it probably > should be correct, but there may be a bug). > > Anthony
