This item has already been deleted (Media library error)

  • Hi! This is strange, because I can’t find a single topic about this issue. I hardly ever delete images inside media library, so maybe this problem is old, but certainly not fixed. I tried in 5 different servers of my own and a couple of testing WordPress sites (wp taste, etc) and the problem persists.

    In media library list view, when I delete a file (image or video) the screen goes white with the text “This item has already been deleted (Media library error)”
    The console says
    GET https://comeswim.s2-tastewp.com/wp-admin/post.php?action=delete&post=6&_wpnonce=75c0199ab9 500 (Internal Server Error)

    If I go back (and check the server) the file is effectively deleted, but I have never noticed that text.
    This does not happen in grid view or if I select and delete more than 1 file (in bulk).

    I tried several WP versions from 5 to 6.6.2, no plugins, several themes, etc.

    Any idea?
    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator James Huff

    (@macmanx)

    Do the files still exist on the server before you delete them from the Media library?

    Do you have any website’s previous backups?

    • This reply was modified 5 months, 2 weeks ago by Jorge Luiz. Reason: spelling
    Thread Starter carlosvai

    (@carlosvai)

    Thanks for the replies!
    @macmanx yes, the file is deleted. Same happens with the themes, if I delete a theme it gives en error as it would have already been deleted, but in reality it gets deleted exactly when the error sign appears.

    @jluizsouzadev yes, and I have tried everything, backups from 2 months, previous WordPress versions, everything.

    What waffles me he most is that it happened in a fresh sandbox (tastewp) and now I created a new WordPress in that site and it does not give me the error (same php version and all).

    I will keep testing, the problem is I don’t get any relevant error in the debug.log-

    It is possible that a PHP error occurs that is so hard that it is not documented in the debug.log. Depending on the server settings, it could be found in the error log of the server itself. Or in a global server log file.

    Do the systems and projects where you are experiencing this have anything in common apart from this error? Is it only with TasteWP or also with other hostings?

    Have you tried it with a different browser? Just a thought …

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.