#26810: DATA_UPLOAD_MAX_NUMBER_FIELDS not taken into account in admin mass
actions
-------------------------------+--------------------------------------
Reporter: Adys | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I think the idea is that individual apps shouldn't strive to adapt to this
setting but rather projects should either raise the value of setting as
needed and/or customize `handler400` with a more-friendly message. That
said, disabling the "select all items" button if the changelist contains
some really large number of items seem reasonable to me, independent of
the new setting.
With the current default of `DATA_UPLOAD_MAX_NUMBER_FIELDS = 1000`, it
requires selecting more than ~1000 items (minus a few for other fields on
the deletion form) to trigger this, doesn't it?
--
Ticket URL: <https://code.djangoproject.com/ticket/26810#comment:1>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.b63933de0cf11111a312451ca3893b78%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
