#26810: DATA_UPLOAD_MAX_NUMBER_FIELDS not taken into account in admin mass
actions
--------------------------------------+------------------------------------
Reporter: Adys | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.admin | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by timgraham):
* component: Uncategorized => contrib.admin
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
On [https://groups.google.com/d/msg/django-
developers/UwkkZ4h0dVA/pbmeOgwjBQAJ django-developers], Tom Christie
suggests:
Most realistic in immediate future: Accept it as a current limitation
(possibly handle TooManyFieldsSent)
Someday later, perhaps: Allow a "select everything" that does not use
individual POST fields
--
Ticket URL: <https://code.djangoproject.com/ticket/26810#comment:8>
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.400645276e4d3e19fa356f7da199d773%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
