Perhaps the issue is a bit different as I don't see that same behavior.
On Thursday, June 30, 2016 at 6:56:54 AM UTC-4, larry@gmail.com wrote:
>
> It seems like in 1.6 template code like this:
>
> {% if error %}
> ...
> {% endif %}
>
> Was OK. But in 1.9 if error is not defined it throws a
It seems like in 1.6 template code like this:
{% if error %}
...
{% endif %}
Was OK. But in 1.9 if error is not defined it throws an exception. So
in 1.9 what is the proper way to check to see if a variable is defined
or not?
On Tue, Jun 28, 2016 at 4:03 PM, Larry Martell wrote:
> I had a 1.6 a
Did you upgrade Django version by version as suggested in our upgrade guide
[0] and fix deprecation warnings along the way? That might help alert you
to the issue.
[0] https://docs.djangoproject.com/en/dev/howto/upgrade-version/
On Tuesday, June 28, 2016 at 4:05:06 PM UTC-4, larry@gmail.com
I had a 1.6 app and I updated to 1.9. Now when I try to login it fails
and I see this in the logs. This works in 1.6. Any ideas what the
issue is?
[28/Jun/2016 17:43:51] DEBUG [django.template:923] Exception while
resolving variable 'STATIC_URL' in template 'registration/login.html'.
Traceback (mo
4 matches
Mail list logo
