On Feb 3, 2012, at 7:46 AM, VP wrote: > Thanks. I just emailed you my routes.py. > > But routes.py might not be the cause, because I have just removed it > (without using routes.py), the problem still existed.
Did you restart web2py? Until you do, it won't recognize the change. I added unit tests for the kind of thing you're seeing to both router tests (pattern & parametric) and they seem to be working OK. There was a (possibly minor) problem with your routes.py. I suggest that you fix it, using router.example.py as the basis, update the routes.py doctest to work with your changes, and then add a doctest for the failing conditions. (FWIW, I'm doing my testing in the trunk, but I don't think there's a relevant change from 1.99.4.) > > > > On Feb 3, 9:27 am, Jonathan Lundell <jlund...@pobox.com> wrote: >> On Feb 3, 2012, at 7:20 AM, VP wrote: >> >>>> Is it possible that you're invoking different routers on the two systems? >>>> Or enabling routes on one and not the other? >> >>> Jonathan, >> >>> One configuration difference between the server and the personal >>> computer is that on the server, I use routes.py, which routeswww.mysite.com >>> and mysite.com to the appropriate app. >> >>> Could this be the problem? If so, how to fix it? >> >> Please post (or send me privately) your routes.py.
