#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 vytisb):
I have tried to reproduce this issue and I think that it is unrelated to
"Select all X objects". Admin already uses a single POST parameter to
specify that "Select all X" was clicked. I have seen 4 fixed POST params
and at most one page worth of object IDs.
I only managed to receive the error with non default values of
`list_per_page` and/or `list_max_show_all`. Clicking the corner checkbox
to select the whole page and running an action was sufficient to invoke
the error in this case.
Maybe a system check to notify the user when `max(list_per_page,
list_max_show_all) + 4 > DATA_UPLOAD_MAX_NUMBER_FIELDS` would solve this
issue?
--
Ticket URL: <https://code.djangoproject.com/ticket/26810#comment:4>
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.d4dff4b6a19a2064723ff5f987ac84b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
