Opened 2 years ago
Last modified 11 months ago
#16164 new defect (bug)
"You are not allowed to delete this post." - While Deleting a Media Library Item
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | General | Version: | 3.1 |
| Severity: | normal | Keywords: | has-patch dev-feedback |
| Cc: | mikeschinkel@…, bpetty |
Description
While deleteing 999 media library items, the request timed out. Resending the same request triggered an error message:
You are not allowed to delete this post.
For me as a programmer, I know that those library items are technically a post, but for communicating with the user, the error message is misleading.
Attachments (1)
Change History (9)
Somewhat related: If you delete a bunch of media items of which some have been already deleted by some other thread, it will stop at the first one that is not able to delete (e.g. because it already has been deleted).
As the request was to delete a post, it could be considered successfull if that post had been already deleted. So it's possible worth to just skip (or count the number of successful deletions) and try further instead of stopping.
This might especially make sense if multiple users are making use of the backend and do some clean-up work. To more gracefully deal with (already) non-existant posts while deleting.
comment:3
mikeschinkel — 2 years ago
- Cc mikeschinkel@… added
- Keywords needs-patch added
- Milestone changed from Awaiting Review to Future Release
As the request was to delete a post, it could be considered successfull if that post had been already deleted. So it's possible worth to just skip (or count the number of successful deletions) and try further instead of stopping.
Seems fine.
comment:5
solarissmoke — 2 years ago
- Keywords has-patch dev-feedback added; needs-patch removed
comment:6
solarissmoke — 2 years ago
Actually, see the patch on #16165 which includes this as well as other improvements to bulk handling.
I have posted an updated patch on #16165, which like the previous comment, includes a fix for this ticket as well.

Related: #16162