#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
-------------------------------+--------------------------------------
Comment (by Adys):
Likely correct. I triggered it with 1136 items.
I think the correct solution would be to rewrite the "select absolutely
everything" bit to work with a single POST parameter or for the "select x"
to work with a comma-separated single parameter (disclaimer: Haven't
looked at the code). However, given that 1.10 is already in beta 1, that
might not be an option - if so, adding a TooManyFieldsSent handler for
that particular scenario and failing gracefully in case of a large
selection would be good enough.
--
Ticket URL: <https://code.djangoproject.com/ticket/26810#comment:2>
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.5c86fa1ea3744ecbea19e4f6309b2218%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
