![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
#38530 closed defect (bug) (duplicate)
Uploading a 512x512 site icon creates a "cropped" duplicate in media library
| Reported by: | adamkheckler | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Customize | Version: | 4.3 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
To reproduce:
- Install latest stable WP (4.6.1 currently) using Twenty Sixteen theme. No plugins.
- Find an image that's exactly 512x512 pixels.
- In the Customizer, go to Site Identity and click Select Image in the Site Icon section.
- Upload the 512x512 image you prepared in Step 2.
- Your site icon is uploaded. Click Save and Publish.
- Look in your Media Library.
Expectation: one image present, which should be the image you just uploaded at the recommended size.
Reality: your original image is there, but there's also a duplicate prepended with "cropped-".
IMAGE1
I don't understand why an image that's already 512x512 needs to be cropped. The resulting images are exactly the same dimensions and filesize.
Here's what it looks like in the uploads directory:
IMAGE2
At first glance, I thought this was a recurrence of this ticket:
https://core.trac.wordpress.org/ticket/33011
... but the filenames aren't quite the same, so I suspect it's a new bug.
Attachments (2)
Change History (6)
#2
@
5 years ago
- Milestone Awaiting Review
- Resolution → duplicate
- Status new → closed
- Version 4.6.1 → 4.3
This is in fact the intended behavior as further discussed in #33011. The term "cropped" is used for consistency with cases where the image was actually cropped, but in reality means that there is a duplicate attachment post specifically representing the site icon and its associated cropped/resized variations.
Confirmed. I have noticed this before and find the behaviour rather annoying! Having read #33011 I got the impression it might be intentional, but I don't understand the reason why we need to duplicate the media item in this manner. Yes, we might be pre-generating more image file "sizes", but as far as I can see these shouldn't conflict with other uses of the image. In any case, this image file generation is really just a performance optimisation that WordPress should be able to manage automatically in the background and without making it visible to the user by duplicating the media item.