[web2py] Re: Scheduler - response.render no longer working

2016-10-09 Thread Brian M
Seems to be working now. Thanks Anthony On Monday, October 3, 2016 at 11:29:52 AM UTC-5, Anthony wrote: > > The issue: https://github.com/web2py/web2py/issues/1485 > > On Monday, October 3, 2016 at 12:17:15 PM UTC-4, Anthony wrote: >> >> Actually, we broke it here: >>

[web2py] Re: Scheduler - response.render no longer working

2016-10-03 Thread Anthony
The issue: https://github.com/web2py/web2py/issues/1485 On Monday, October 3, 2016 at 12:17:15 PM UTC-4, Anthony wrote: > > Actually, we broke it here: > https://github.com/web2py/web2py/commit/b4acfd0724845633f667a55e593a15576379554d > . > > Previously, response._view_environment was created at

[web2py] Re: Scheduler - response.render no longer working

2016-10-03 Thread Anthony
Actually, we broke it here: https://github.com/web2py/web2py/commit/b4acfd0724845633f667a55e593a15576379554d. Previously, response._view_environment was created at the end of build_environment, and then again very shortly thereafter in serve_controller (right after executing the models). We

[web2py] Re: Scheduler - response.render no longer working

2016-10-03 Thread Niphlod
hum. Trunk has been recently updated in the management of caching code for controllers and views wonder if this is related to that. On Monday, October 3, 2016 at 5:15:18 AM UTC+2, Brian M wrote: > > OK, so I've had multiple scheduled tasks running for years that use >