[wp-trac] [WordPress Trac] #63284: _prime_post_caches is getting called unchunked
WordPress Trac
noreply at wordpress.org
Tue Apr 15 20:57:51 UTC 2025
#63284: _prime_post_caches is getting called unchunked
--------------------------+------------------------------
Reporter: ckeeney | Owner: joemcgill
Type: defect (bug) | Status: reviewing
Priority: normal | Milestone: Awaiting Review
Component: General | Version: 6.7.2
Severity: major | Resolution:
Keywords: | Focuses:
--------------------------+------------------------------
Comment (by joemcgill):
@ckeeney I've followed the steps you've outlined with a few noted
exceptions and am not able to reproduce this currently with a regular Core
set up.
1. I've started up a fresh site, using `@wordpress/env` running WP 6.8.
2. I've installed Query Monitor and Redis Object Cache (Note: Redis is not
enabled in the environment)
3. I've activated the Twenty Seventeen theme on the site.
4. I've registered a custom post type that is hierarchical and supports
'page-attributes'. (Note: I've registered this post type in a custom mu-
plugin rathe than via ACF.)
5. I've generated 1000 posts for that post type via CLI
6. When visiting the list table for the post type, `_prime_post_caches()`
is only being called with 20 IDs (the number being displayed in the list
table).
Two main differences I see:
1. I'm not using ACF to register the post type. @ckeeney Could you try
registering a custom post type using code directly in the theme or an mu-
plugin without ACF?
2. Redis Object Cache is active but the drop in is not installed, since no
Redis connection could be established. @tillkruess any chance the plugin
is filtering something about the queries on this page? I can try
reproducing with an active Redis connection, but wanted to eliminate the
obvious things first.
Any other ideas welcome
--
Ticket URL: <https://core.trac.wordpress.org/ticket/63284#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list