I'm using Django 1.0, so it may be that your advice doesn't apply to
me. In case it does, I tried following what you're saying.
Unfortunately, I'm find it quite difficult to understand what you
think the problem is. I get your point about how there's some config
in settings.py that sets what
So, I finally tried installing version 1.3.4 of the SDK, which was a
bit of a headache, because my dev site would not start up after I did
this. I think this is due to
https://code.google.com/p/google-app-engine-django/issues/detail?id=161
. To work around the issue, I added ipaddr supplied with
After upgrading my sdk (to 1.3.4) and google-app-engine-django (to
r105), I'm still having problems with sporadic TemplateDoesNotExist
errors.
On Jun 18, 3:03 pm, allyourcode allyourc...@gmail.com wrote:
So, I finally tried installing version 1.3.4 of the SDK, which was a
bit of a headache,
Thanks. But I worked around the solution by adding a empty app to the
INSTALLED_APPS that points to an empty .py file. Seems to work, but I get some
random errors from my custom filers file saying that they don't exists.
When searching around I found that it's a bit confusing for many
This import is causing massive headaches on App Engine deployments
with TemplateDoesNotExist sporadic messages. Assuming you have Django
1.1 setup correctly, the global_settings.py file will setup
TEMPLATE_LOADERS to load from both the project dir (/templates) as
well as any INSTALLED_APPS dir.
I have a similar problem. When I updated to django 1.1 I get
TemplateSyntaxError: Template u'../index.html' cannot be extended, because it
doesn't exist.
It seams that the problem lies in that the TEMPLATE_DIRS is not set wrong. But
I don't know how set in as a relative path.
Anyone
I think the problem is that my TEMPLATE_DIRS gets cleared at some
point, even though my app doesn't do that, at least not directly. My
guess is that this is happening somewhere in the SDK or Django helper
to implement the admin pages, but I can't tell which piece is doing
the manipulation :/.
