March 8, 2018 at 22:12 UTC - Views: 49 #53752
All the feature images on https://www.bajanthings.com/ have disappeared after the most recent update.
All that is showing is a blank space.
PeterMarch 8, 2018 at 22:27 UTC - Views: 49 #53753
I can confirm that it is the update from 3.1.12 to 3.2. I have just rolled back my files to the pre-update backup.
Feature images now showing up
PeterMarch 8, 2018 at 23:15 UTC - Views: 49 #53755
I can’t reproduce this behaviour on my test sites.
There were no changes that should have affected featured images.
I notice the Featured Images are being cached by JetPack. Perhaps if you disable that feature, they might come back with 3.2.March 9, 2018 at 02:26 UTC - Views: 59 #53758
JetPack has two cache features – both of these are on.
JetPack – Settings First tab Writing
Speed up your site Section
Serve images from our servers
Jetpack will optimise your images and serve them from the server location nearest to your visitors. Using our global content delivery network will boost the loading speed of your site.
Lazy load images <- this was launched a few weeks ago
Improve your site’s speed by only loading images visible on the screen. New images will load just before they scroll into view. This prevents viewers from having to download all the images on a page all at once, even ones they can’t see.
I can replicate the issue with 3.2
If Serve images from our servers is on the feature images show.
If both Serve images from our servers & Lazy load images are on then Feature images do not show. If I turn off Lazy load images then the feature images come back.
This was not an issue with 3.12 and has only come to life only after updating to 3.2
BajanThings had both Serve images from our servers & Lazy load images on for 3.12
What is happening is the the blank image is loading….
Hope that helps in tracking down the issue.
PeterMarch 9, 2018 at 02:32 UTC - Views: 43 #53759
Heading to bed – I have just turned back on the Lazy load images so you can see it in action.
PeterMarch 9, 2018 at 02:37 UTC - Views: 39 #53760
I have the same issue on http://www.polywogg.ca. However, I wondered if it was the theme update or the extra plugin support update for Weaver causing the issue.
PolyMarch 9, 2018 at 02:40 UTC - Views: 42 #53761
Addendum — same settings issue in Jetpack — if I alter the “serve images from our servers”, it makes no difference (if they were loading before, they’ll load now; if they weren’t loading, they won’t load still). The setting on my site is definitely “load lazy images”. If I turn it on, no FI; if I turn it off, up they pop.March 9, 2018 at 04:38 UTC - Views: 36 #53763
I don’t know why the lazy load would break the theme – nothing in the new version changed the old code. But now that you seem to have pinned it down to lazy load images, I can test it on the test site. But at the least, it might reveal an issue with lazy load that I can report, or it might be some little tweak possible.
I won’t be able to get to this until next week sometime, so for now, you should disable it. Lazy load isn’t all that helpful anyway since modern browsers already do most of that on their own – load the top of the page images first.March 20, 2018 at 20:36 UTC - Views: 24 #53953
Should we also expect a new version that solve this bug?March 21, 2018 at 01:41 UTC - Views: 20 #53960
I have been unable to find what this issue might be in the theme.March 21, 2018 at 12:27 UTC - Views: 19 #53969
I had to disable both “Serve images from our servers” and “Lazy load images” in JetPack to make the images visible. Both FI and the pictures in the posts were not visible. Now it works.March 21, 2018 at 21:25 UTC - Views: 11 #53975
I would ask on the WP JetPack support area to ask about this. I had an issue with JetPack image serving in the past when I update my images (if I remember correctly, I resized all my different image sizes with a resize image plugin). That totally freaked the JetPack image server.
I haven’t found it, but what JetPack needs is some way to re-sync all the images it is serving.
You must be logged in to reply to this topic.