Scheduler - response.render no longer working

[Brian M]

OK, so I've had multiple scheduled tasks running for years that use response.render('path/to/template.html', dict(var= 'something')) to help build email bodies and it has been working perfectly. Now when I try to upgrade to the latest web2py trunk (was on 2.13.4 - yeah I'm a bit behind) all that has stopped working.  Below is the error I'm getting

File "C:\FMSC Webapps\web2py_master\gluon\globals.py", line 437, in render
    self._view_environment.update(self._vars)
AttributeError: 'NoneType' object has no attribute 'update'

Why isn't this working anymore? Has some backwards compatibility breaking change been made to the scheduler environment? Any advice would be much appreciated.

-Brian

PS. I've seen https://groups.google.com/forum/#!searchin/web2py/response.render$20scheduler|sort:relevance/web2py/UsUvODL07zs/HrcCsxQcCQAJ which would seem related but I'm unable to get it working by just adding from gluon.template import render

[Niphlod]

hum. Trunk has been recently updated in the management of caching code for controllers and views .... wonder if this is related to that.

[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 thought we could get rid of the line in build_environment, but it turns out that creates a problem for the scheduler (and presumably the shell), as the application code is executed via shell.env rather than serve_controller in those cases.

I'll open an issue and propose a fix.

Anthony

[Anthony]

The issue: https://github.com/web2py/web2py/issues/1485

[Brian M]

Seems to be working now. Thanks Anthony