Check and see if you have had a deadline exceeded error 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.
I am not seeing any deadline exceeded error during the instance startup,
but I was able to successfully reproduce this problem, steps below.
1. Make sure no server instances are started in GAE (shutdown any already
running)
2. Go to a page that does not exist in the app (i.e.
Hi
I would look at how you 404 handler is initialized 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
Below is the log data from the 404 error
Traceback (most recent call last):
File
/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.5.2/webapp2.py,
line 1529, in __call__ rv = self.router.dispatch(request, response)
File
So that part of it looks fine.
The question is does your code that initialises the globals
'globals': {
'uri_for' : webapp2.uri_for
},
ever get called when it goes through this path, and if it doesn't maybe
what is happening is webapp2 is now initialised (partly)
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
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 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
Vinny, Thanks for your answer. I have looked into the suggestion but can
find difference with my code.
I get the error only when i upload a new code to the app engine. If i
restarted it manually it works.
Error 500: 'uri_for' is undefined
any ideas? Thanks
On Tuesday, January 14,
On Tue, Jan 14, 2014 at 2:13 AM, Roninio azac...@gmail.com wrote:
I have looked into the suggestion but can find difference with my code.
I get the error only when i upload a new code to the app engine. If i
restarted it manually it works.
Usually the fix outlined in the Stack Overflow
hi
having same problem. I am using the boilerplate
https://github.com/coto/gae-boilerplate;
did you resolve this issue?
On Monday, July 16, 2012 10:34:35 AM UTC+3, Thomas Marban wrote:
Ever since including webapp2.uri_for in my webapp2_extras.jinja2 config via
'globals': {
On Sun, Jan 12, 2014 at 4:30 AM, Ronen Azachi azac...@gmail.com wrote:
having same problem. I am using the boilerplate
https://github.com/coto/gae-boilerplate;
did you resolve this issue?
On Monday, July 16, 2012 10:34:35 AM UTC+3, Thomas Marban wrote:
Ever since including webapp2.uri_for
12 matches
Mail list logo
