Problem with full-sized images in Library after updating to WP 4.5

[Pixeldrummer]

When placing images into posts/pages they appear medium sized. I selected the image to show in full-size but the preview image appeared like a broken link (in the library) and the image could not be changed to full-size in the post. That is true for all images.

In another site the background image, which was full-size looked 'corrupted' in all browsers, completely shredded in Safari on Mac. Not usable!

As a temporary work around go to the Library, find the image(s) in question and edit each image by scaling it down very slightly. I.e. I changed that background image from 2000px x 2000px to 1950px x 1950px and saved it. Or changed a smaller image from 223px to 220px. As soon as you edit in this way that image will render properly and show the preview in the library. I won't be updating any other sites to 4.5 until this is fixed.

[swissspidy]

Hey there,

Thanks for creating this ticket and welcome to WordPress trac!

Can you elaborate a bit more on how you upload the images and how they get displayed? Screenshots or perhaps even a short screencast would be very helpful.

Also, which image sizes are configured in Settings -> Media?

That's the first time I've heard of such a bug, so any additional steps to reproduce it would be very helpful. Usually, you should try it using a default theme with all plugins disabled to make sure it's indeed a bug in WordPress core and not another part of your site.

[Pixeldrummer]

large image renders in Safari on Mac

[Pixeldrummer]

wp 4.5 image renders in FF on Mac

[Pixeldrummer]

wp 4.5 large image in Safari not rendering

[Pixeldrummer]

The first two images are a development site, where WP was updated before starting to work on it. So the problem in Safari was not obvious until I worked on my Mac and tested the display.

The third image was 'fixed' for all browsers when I scaled it down, as described in my original report, but it does not render properly in Safari on Mac. Safari Version 9.0.3 (11601.4.4), and yes I cleared history and cache. Am starting to think that images without specific size definitions are those with the problem. I converse with some of my peers online and others have noticed problems with this upgrade. One reported this:

I've found two other problems with 4.5 so far. One is related: I updated a site and when I uploaded new images, I get the generic "file" image in Media Library. The images are there, if I put them into a page they're fine, but the image thumbnail in Media Library wont' display. Apparently I'm not the only one.

Always comes back to the media library.
image settings are 100 x 100, 300 x 300, 1024 x 1024
I drag images into the library.
Just to mention those problems did not show up until the moment I updated to 4.5.
Just installed and tested on WP theme 2016. Same problem in Safari.

[kirasong]

@Pixeldrummer Thanks for the report!

Do I understand correctly from your previous note that this was an issue even with a clean install and Twenty Sixteen? (sounds like yes?)

Presuming so, could you please:

• Post the PHP, Imagick and ImageMagick version numbers from a phpinfo() script on your server?
• Attach an example image that has this problem when uploading, for testing?

[Pixeldrummer]

Thank you for your reply. WP 4.5 and 4.5.1 has a definite impact on the way images are handled in the Media Library. But I have now found out that this is happening specifically when X-Theme (Theme.co) is active. These issues, now also reported here: https://core.trac.wordpress.org/ticket/36677 do not appear in sites with X-Theme and WP versions earlier than 4.5.

I have now posted in the X-Theme support site: ​https://community.theme.co/forums/topic/wp-4-5-and-4-5-1-cause-media-library-and-placement-problems-in-x-theme/. Testing in a site with WP 4.5.1 and another theme, everything works as it should. Am still reluctant to upgrade all sites to WP 4.5.1. I can find work-arounds, average users might not.

The rendering of the images as posted here has sorted itself out.

[joedolson]

Based on the initial reporter follow-up, I'm closing this ticket as invalid, because it appears to mostly be a theme issue, and has had no follow ups since 2016.