Make WordPress Core

Opened 9 years ago

Closed 9 years ago

#31452 closed defect (bug) (invalid)

Creation and Deletion of Media Not Occurring in Some Cases

Reported by: fa123's profile FA123 Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.1.1
Component: Media Keywords:
Focuses: Cc:


I have noticed a couple issues with media deleted via "Delete Permanently" in the media library:

1) the "Delete Permanently" does not remove the file, only the listing in the media library. For instance I uploaded a PDF, discovered the error and deleted it in the media libary. However, if you view the link below you will notice that the PDF is still very obviously up on the site. (I made sure it was not a cached copy I was seeing)

2) Some media uploads do not create a working link. For instance I tried to upload an image name partner_logos_6. The upload was successful. It created what would be the correct URL (ie http...partner_logos_6.jpg). However, when one attempts to link or go to the image, it generates a 404 error.

Normally, I would assume this is because media with that name and URL was previously on the site and taken down via the broken "Delete Permanently" feature.

However, when I deleted a PDF and uploaded a new one with the same name, generating the same URL, (the PDF in issue #1) this forced the link to go to the initial upload of the content, ignoring the newer version, the only version listed as on the site by the media library.

As a result I am at a bit of a loss to explain what is going on here. The workaround is pretty easy--don't delete anything so unique URLs are forced--but a fix for this would be most welcome.

Change History (7)

#1 @FA123
9 years ago

Hi. Is anyone actually working on this?

#2 @wonderboymusic
9 years ago

  • Keywords reporter-feedback close added

Are you running trunk? This works for me in trunk.

#3 @FA123
9 years ago

What is trunk?

#4 follow-up: @FA123
9 years ago

Hi...are you willing to explain what that is? Even some documentation would be fantastic.

#5 in reply to: ↑ 4 @DrewAPicture
9 years ago

Replying to FA123:

Hi...are you willing to explain what that is? Even some documentation would be fantastic.

"Trunk" refers to the bleeding-edge development version of WordPress. For instance, right now, the latest trunk version is 4.2-alpha-31546-src because we're in the middle of the 4.2 development cycle.

For more information on trunk and how to get set up locally for WordPress core testing and development, check out the Installing WordPress Locally article and related pages in the Core Contributor Handbook.

Hope that helps :-)

#6 @FA123
9 years ago

@DrewAPicture Thank you!!

I guess this support is crowd sourced. I thought one person was handling this and they were being paid for it. That explains the long wait times. Sorry for the extra comments all! :)

@wonderboymusic No. I am using the latest stable version, 4.1.1, hence why I am rather surprised to find a bug like this.

#7 @DrewAPicture
9 years ago

  • Keywords reporter-feedback close removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

I can also confirm this seems to be working fine in trunk as well as 4.1.1.

@FA123: Please feel free to reopen if you continue to see problems after 4.2 is released.

Note: See TracTickets for help on using tickets.