#289: Patch: more details with "Please correct the errors below."
---------------------------------------------+------------------------------
Reporter: brantley ([EMAIL PROTECTED]) | Owner: adrian
Type: defect | Status: reopened
Priority: normal | Milestone:
Component: Admin interface | Version:
Severity: normal | Resolution:
Keywords: error please correct |
---------------------------------------------+------------------------------
Changes (by ubernostrum):
* resolution: wontfix =>
* status: closed => reopened
Comment:
Maybe the best option here would be to have the following setup:
* At the top of the page, "Please correct the errors below", with a
control underneath that can be clicked to expand, in place, a full list of
the errors.
* Down in the fieldsets themselves, continue matching error messages with
fields as before.
This way the full error list doesn't take up a huge amount of space unless
a user asks to see it, but is still there for confused developers who
don't realize they've left a field out of the admin. Getting the human-
readable fields for the error names in the full list up top wouldn't be
hard, considering we already do it for the fieldsets.
I think it'd also be a good idea to have the model validator print
something to the console -- but not error out -- if a model has a required
field that won't be listed in the admin.
--
Ticket URL: <http://code.djangoproject.com/ticket/289>
Django <http://code.djangoproject.org/>
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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
