jetpack icon indicating copy to clipboard operation
jetpack copied to clipboard

Sitemaps fail to update with images inside a slideshow block

Open cuemarie opened this issue 2 years ago • 2 comments

Impacted plugin

Jetpack

Quick summary

@vparkhere reported this issue on her site where the sitemap won't update despite adding images to a post, specifically via a slideshow block. She gave the sitemap 12 hours to update on its own, but it still didn't update properly with the images that added to the post.

Here's the test post with the slideshow: https://vpat001.wordpress.com/2017/04/19/first-blog-post/ Test site's sitemap: https://vpat001.wordpress.com/sitemap.xml

Steps to reproduce

  1. Make sure site is public, then add a slideshow block with images to either a new post or published post. Publish/Update.
  2. Check site map at URL/sitemap.xml
  3. Wait for a while, at least 10 minutes, and check site map again. Still will not show images that were added to the post despite lastmod date being updated to latest publish/update date.

A clear and concise description of what you expected to happen.

Images added to the post to appear in the sitemap

What actually happened

Images were not updated in the sitemap.


Screenshot of sitemap with no images for the post https://vpat001.wordpress.com/2017/04/19/first-blog-post/:

screenshot

Impact

One

Available workarounds?

There is no user impact

Platform (Simple and/or Atomic)

Simple

Logs or notes

Originally reported here: https://github.com/Automattic/wp-calypso/issues/80973#issuecomment-1718048615

cuemarie avatar Sep 14 '23 20:09 cuemarie

📌 REPRODUCTION RESULTS

  • Tested on Simple – Replicated

📌 FINDINGS/SCREENSHOTS/VIDEO

The issue can be replicated exactly as described above.

The post below has a slideshow block. (Ignore the blog post URL 😄 )

LEw8rr.png

I also tried adding a new image below the block, but I still don't see the sitemap being updated except for its lastmod info.

x3rSVM.png

karenroldan avatar Sep 15 '23 17:09 karenroldan

This issue has been marked as stale. This happened because:

  • It has been inactive for the past 6 months.
  • It hasn’t been labeled `[Pri] BLOCKER`, `[Pri] High`, `[Type] Feature Request`, `[Type] Enhancement`, `[Type] Janitorial`, `Good For Community`, `[Type] Good First Bug`, etc.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

github-actions[bot] avatar Mar 20 '24 00:03 github-actions[bot]