Some more digging on this issue. After cleaning up my custom templates to
work with Django behavior changes, and still getting exceptions from /admin
and a contact form, I've been able to repro the same exceptions in a clean
Mezzanine generated project by adding this logger
'django.template': {
'handlers': ['console'],
'level': 'DEBUG',
'propagate': False,
},
None of these template exceptions break unit tests, and the issue has been
reported elsewhere,
e.g.
https://github.com/tomchristie/django-rest-framework/issues/3736
We'll keep testing but can't see any impact on the app itself so might just
ignore these. Welcome a 2nd opinion and not clear
Exception while resolving variable 'this_is_the_login_form' in template
'admin/login.html'.
> Note also that the admin login form has been updated to not contain the
this_is_the_login_form field (now unused) and the ValidationError code has
been set to the more regular invalid_login key.
http://django.readthedocs.org/en/1.7.x/_sources/releases/1.7.txt
Exception while resolving variable 'REQUEST' in template 'admin/login.html'.
> Note that runserver
<https://docs.djangoproject.com/en/1.9/ref/django-admin/#django-admin-runserver>
strips all headers with underscores in the name, so you won’t see them in
META.
https://docs.djangoproject.com/en/1.9/ref/request-response/
--
You received this message because you are subscribed to the Google Groups
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
