Well, I got routes.py logging working, but today I can't reproduce any of my strange behaviour from yesterday. I have no idea what could have been causing it. I was moving around a lot between different servers/configurations/domains/webfaction applications, so perhaps something was being cached along the way?
Alec (who started this thread) - are you still having any troubles with routes.py? You can probably close the issue for now. I'll keep a close on on things, and let you know if it happens again. Thanks to everyone for their help - hoping to launch (www.ai-therapy.com) later this week! Learning web2py has been a pleasure. On Saturday, July 21, 2012 10:06:32 PM UTC+1, Jonathan Lundell wrote: > > On 21 Jul 2012, at 1:38 PM, Neil wrote: > > I can confirm that I can't reproduce the behaviour using the same web2py > code locally with Rocket on windows. Also, I tried adding: > > logging = 'debug' > > and > > default_ logging = 'debug' > > to routes.py, and I couldn't get any logged info (on either platform). > > > Try logging = 'warning' (there is no default_logging, I don't think, in > this context). Seems the default threshold for logging is a little higher > than I thought. This will log to the console, assuming that you're running > in a mode where console logging works (it does running in the foreground > with Rocket). If not, you'll need to configure logging.conf to send logging > to a file. > > > --
