Environment Details<\/p>\n\n\n\n
Description<\/p>\n\n\n\n
When bulk editing posts via the WordPress admin dashboard (e.g., selecting multiple drafts and changing their status to “Published”), the Redis object cache for As a result, frontend archive pages, the homepage blog loop, and category lists continue serving the stale post list from Redis.Steps to Reproduce<\/p>\n\n\n\n Expected Behavior<\/p>\n\n\n\n The frontend post list \/ archive should immediately display the newly published posts, as the query cache holding the post lists should be invalidated upon status transition.Actual Behavior<\/p>\n\n\n\n Troubleshooting & Diagnostic Findings<\/p>\n\n\n\n To isolate the exact point of failure, I conducted the following tests:<\/p>\n\n\n\n Core Refactor Suspicion & Technical Context<\/p>\n\n\n\n I recall that recent WordPress 7.x release notes highlighted major refactoring around the admin post list table (modernizing list architecture \/ Data Views \/ batch processing pipelines)<\/strong>.<\/p>\n\n\n\n It is very likely that the updated post list table altered how batch updates and lifecycle hooks are dispatched during bulk operations:<\/p>\n\n\n\n Could you please investigate compatibility with the refactored WP 7.x post list workflows and ensure a listener for <\/p>\n","protected":false},"template":"","class_list":["post-19014528","topic","type-topic","status-publish","hentry"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/19014528","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/19014528\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=19014528"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}WP_Query<\/code> \/ post lists is not invalidated.<\/p>\n\n\n\n\n
\n
\n
redis-cli flushall<\/code>) immediately resolves the issue and the frontend post list shows the updated posts. This confirms the stale query results are strictly held in volatile Redis memory rather than persistent database storage\/transients.<\/li>\n\n\n\n\n
WP_Query<\/code> caches results in the persistent object cache using posts_last_changed<\/code>.<\/li>\n\n\n\nwp_cache_set_posts_last_changed()<\/code> is not invoked at the end of the routine, leaving the posts<\/code> cache group’s last_changed<\/code> key untouched in Redis while the MySQL records have already updated.<\/li>\n<\/ul>\n\n\n\nbulk_edit_posts<\/code> (or reliable execution of wp_cache_set_posts_last_changed()<\/code>) is tied into the bulk update completion?<\/p>\n\n\n\n