#18018: MessageFailure in Django 1.4 admin
-------------------------------------+-------------------------------------
Reporter: Simon | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 1.4
Severity: Normal | Resolution: invalid
Keywords: admin, messages, | Triage Stage:
failure | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by anonymous):
Thanks for the hint. Obviously this changed over the last Django version,
since up to now, we neither had the required message context processor,
nor middleware or app installed. For only *one* occurrence of the messages
framework inside the admin code this is actually quite some overhead.
IMHO, it would make sense to make this optional and simply check
availability of the framework here:
contrib/admin/options.py
{{{
messages.info(request, message)
}}}
Best,
Simon
--
Ticket URL: <https://code.djangoproject.com/ticket/18018#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
