On Feb 22, 2011, at 10:25 PM, pbreit wrote: > Oh, boy, I just tried it again without that line and it does seem to work > fine. I have no idea what has been going on. So at this point it all seems to > be working correctly and I'm probably an idiot. Maybe a caching issue > somewhere? Once again, sorry for the false alarm.
Caching, or maybe not restarting web2py after a routes change? Easy to do when you're making tweaks to the configuration.
