y.
>
> Hence the error.
>
> I have never used webapp or webapp2 or jinja so I have no personal
> experience in this area, but the symptons really look like an incomplete
> initialisation.
>
> T
>
> On Friday, January 17, 2014 12:28:41 PM UTC+8, Jeff Potter wrote:
&g
ialized and if it has different
> imports/initialization phases to your regular handler.
> My guess is something isn't being imported correctly.
>
> Are you using appengine_config.py for all your path setups and any global
> init ?
>
> T
>
> On Friday, January 17, 201
or during instance
> startup, prior to the instance exhibiting this problem.
>
> T
>
> On Wednesday, January 15, 2014 11:06:55 PM UTC+8, Jeff Potter wrote:
>>
>> I am having this problem with coto-boilerplate right now. Stacktrace for
>> the problem below. Stoppin
I am having the same problem with a gae-boilerplate site.
ur_for is defined in basehandler.py as so...
def jinja2_factory(app):
j = jinja2.Jinja2(app)
j.environment.filters.update({
# Set filters.
# ...
})
j.environment.globals.update({
# Set global variabl
I am having this problem with coto-boilerplate right now. Stacktrace for
the problem below. Stopping and starting a new instance fixes the problem.
Traceback (most recent call last):
File
"/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.5.2/webapp2.py",
line 1529
I get the same problem (UndefinedError: 'uri_for' is undefined) with my
coto-boilerplate website.
It happens on the first uri_for call in a template. I had canonical links
in the header which called uri_for but caused errors so I removed them, but
now the errors are happening in my navbar html.