Images no longer resized after Wedge update

Hello Leane-

Thanks for reaching out! I agree it would be very frustrating to go crop each one of your images again.

I clicked around your site, and I didn’t spot any images that looked out-of-place. Did you already solve this issue? If you did, would you mind sharing the solution you found in case anyone else has the same issue? If not, can you specify a page with one of the images that’s having the problem?

I did get in touch with the developers of the Wedge theme, and they weren’t able to think of anything off the top of their heads that might have caused a problem like this, particularly just on desktops and not other devices.

It’s conceivable that you may need to clear your cache via WP Super Cache, look for the Delete Cache button in your top admin bar.

Hi Leane-

Thanks for pointing me in the right direction!

I can see that those images have explicit “square” sizes of 150×150, but they’re not being displayed that way.

One possibility that occurs to me is that the images might have some interference coming from the Jetpack Site Accelerator. According to this documentation, Jetpack uses some logic to alter the image sizes when you “switch themes,” and I can imagine that the upgrade might have fooled it somehow.

To test this theory, I recommend temporarily disabling Site Accelerator for your images, and clearing your cache to make sure the changes take effect (Jetpack recommends waiting several minutes as well). Check to see if they look right (use a private browsing window to make sure no browser cache is interfering), and if so re-enable Site Accelerator to see if the CDN will start serving the right sizes.

You can find that setting in Jetpack > Settings > Performance and specifically look for the option to Speed up image load times.

Hi Leane-

Thanks for the update! I’m glad they’re showing correctly now, but I agree that you’ll want to have some kind of speed optimization for your images. The good news is that at this point, we know what’s actually going wrong.

This is new to me, because in my past experience the Jetpack Image CDN “just works.” According to the limitations noted here, there’s not really a method to “invalidate” or clear the image cache (other than going in and changing each image’s filename).

Here are a couple things we can try. Since we know that Jetpack uses some logic to figure out the image sizes whenever the theme is changed, it might help to try that. Re-enable Site Accelerator for images, then navigate to Appearance > Themes and briefly activate one of WordPress’ default themes (one that starts with “Twenty-“). Clear your cache, wait a few minutes, switch back to Wedge, and clear your cache once more.

Another option I’m gleaning from the Jetpack documentation is to simply leave Site Accelerator disabled for a period of time. According to them,

Any images that are removed […] will eventually “expire” and be removed from the CDN.

Unfortunately, they don’t specify how long to wait, but I’d try a week as a first guess.

Finally, it might be worth reaching out in Jetpack’s support forums to see if their team has experience with this issue. I did skim the first few pages of search results in the forum for similar problems, but I didn’t find any that were specifically about this same issue.

As always in WordPress, there are other ways to accomplish the goal of speeding up your image load times as well. While most CDN’s are paid services, CloudFlare offers a free tier and Optimole has a free tier for sites with fewer than 25K monthly users. Very soon, we’ll also be offering this service via W3 Total Cache (although that’s still in early development).