#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 vytisb):
* cc: vytis.banaitis@… (added)
Comment:
@timgraham, I see it now. Previously, I used a custom action without
intermediate pages.
So this affects the delete action intermediate page and any custom action
intermediate page that mimics the behavior of delete action.
For the delete action a possible solution would be to make the
intermediate page form send the same params as the action form in
changelist.
However, this solution has a problem when new objects are created between
the rendering of confirmation page and user confirming the deletion --
objects would be deleted that the user did not confirm.
The current implementation avoids this for direct objects but not for
related objects that would be cascade-deleted.
--
Ticket URL: <https://code.djangoproject.com/ticket/26810#comment:6>
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.ca54963f2288b9514829ccddf648d993%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
