Aahan Krish

XML Sitemap Feed isn’t a great idea, I think, looking at its specs. So, I’ll will be staying away from it, and instead use an older version of WordPress SEO by Yoast itself for now. ??

UPDATE – 2: I just tried the development version… still no luck!

UPDATE: This is weird. Initially the news sitemap was showing a 404 error page (generated by WordPress), but now, it shows up just fine — but there are no posts. So, in a way, the issues still stand.

Just in case it helps, here’s a list of plugins I currently use.

@mattwkelly Before you have the changes made, I’d like to direct you to this (which sheds some light on the issue) so that you can take a proper decision.

We’re going to open up the repo for contributions though.

That’d be great!

Do you want to make the change when that happens? ??

Unfortunately, I don’t know how to use those version control systems (I’m learning, and it’ll take a while). ?? I’d be glad to help if there’s any other way.

Thanks!

Although I am not really sure, I don’t think using display: none; is a good idea. It is said that some browsers (Firefox?) simply don’t load images that are hidden using display: none;. Again, I am not sure.

So, I had to think a bit, and finally decided to go with this:

body > img {
    position: absolute;
    top: -1px;
}

Reason(s): The image is not really an image, so it really can’t be seen. But it takes 1px area, where it’s positioned. So, I see no reason why the CSS code I used (as shown above) would be a bad choice.

But I am free to suggestions. So, please feel free to share what worked for you. :^)

Otto has posted his reply here.

BOOM! The fix worked like a charm! ??

Hi Joost, I don’t know if this is a bug, but all my posts show the same image (the “featured image” of the latest post — as per the published date). For example, please take a look at this (source): view-source:https://whatthenerd.com/post-sitemap.xml

Sorry I didn’t realize it early enough.

Updated this morning. You beat my expectations with that really quick update. Again, thank you. ??

Great news, thank you Joost.

I have the same problem too, which I reported a few days ago. No reply from the plugin author yet. ??

@dirtystylus : According to Mark, this was fixed in v1.1.2.

UPDATE: By the way, it looks like mostly (NOT only) posts with ‘pre’ code blocks are affected.