Closed jeherve closed 8 years ago
@jeherve I don't think that the featured image is big enough in this case (352 × 235px). We're looking for a minimum of 600px width to display a banner.
@bluefuton this is also one of those "one-liner" cases... I wonder if we should ditch those until the refresh comes out..
I don't think that the featured image is big enough in this case (352 × 235px). We're looking for a minimum of 600px width to display a banner.
That makes sense 👍
The other issue here is that the featured image isn't appearing in the full post view. I think we may be suppressing small ones, incorrectly.
I have a similar report in 2785611-t
https://wordpress.com/read/blogs/115053861
Featured images stopped appearing for my posts newer than August 10, 2016
The image on http://www.selfdistractsequence.com/the-museum-of-grind/ is 840 x 480
Got another report. Featured images for this site were showing earlier, but not anymore for new posts.
It has a featured image set but it doesn't show up. Feed: https://wordpress.com/read/feeds/48698434
I don't see an issue with featured image size as the previous ones which do show up are similar in size as the new ones.
Looks like that site is having problems with the new Jetpack sync, which is causing us to miss the featured images. In contact with jpop support to see what we can do.
Ah, that wasn't the problem. The issue here is two-fold: 1) this isn't really a featured image, the image is actually in the content and 2) the image is not in the content that's in the feed (see http://www.cookingfromheart.com/feed/ ) so we can't pick it up with our current system
To get featured images in the reader, the author can either use featured images on the posts, or they can turn off summary feeds for the site.
Is there a possible work-around, when:
You can find 2 examples here: https://wordpress.com/read/feeds/8020695
It seems to me like the Featured Image should always be the first choice when choosing a cover image in the Reader, even if that Featured Image isn't used in the post.
@jeherve looks like the problem there is that werewp.com isn't properly associated with your jetpack site in the feedbag. Looking into that.
This looks resolved now, at least on original Reader view for https://wordpress.com/read/blogs/67272686
Testing with staging, Mac-n-Chrome:
If there are other related bugs that still need addressing, let's open new issues for them separately.
Steps to reproduce