Hi Cornelius, My Pylons knowledge is fading, but I believe there are two possible causes:
1) The routes are matched in the order you list them, so in Pylons it's generally best to put the '/' route right after your error controller routes. If you put '/' at the end of the list, there's a chance that a more generic route above it is matching first and returning a different controller/action. 2) The more likely culprit is a default index.html file in your public directory. If I remember right, Pylons checks that directory for static files before checking mapped routes, and if it finds index.html it displays it as the default page instead of whatever you configured in routing.py. There's an explanation of the behavior here: http://pylonsbook.com/en/1.1/exploring-pylons.html#static-files Hope this helps! Eric 2012/1/19 Cornelius Kölbel <[email protected]> > Hi there, > > I am still using pylons 0.10 and got a routing problem. > > In my routing.py i create some user defined routes like > > map.connect('/config/', controller='config', action='index' ) > > But I also want to create a route for the case, when no url is given. So > I do > > map.connect('/', controller='setup', action='index' ) > > Every time I do not pass any url I get to the default pylons welcome page. > On another project this just works fine. > > Do you got any hint, what I am missing? > > Thanks a lot and kind regards > Cornelius > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
