Hello,
I'm running Post Grid (free, v2.3.23) together with Combo Blocks - Pro (v3.3.18) on WordPress, site: kameraverleih-mannheim.de
Bug: Any Post Grid instance filtered by a taxonomy term (category) that was created after the Combo Blocks Pro license was activated returns "No post found" on the front end -- even though the posts exist, are published, and are correctly assigned to that category. This happens regardless of item layout (default/empty layout or a custom Layout Editor layout).
Confirmed NOT the cause:
- Missing featured images (all affected posts have a featured image set)
- Server/page caching (reproduced on brand-new, never-cached draft pages, while logged in, bypassing Varnish)
- Corrupted taxonomy data -- WordPress's own category archive page and the REST API (/wp-json/wp/v2/posts?categories={id}) both correctly return all posts for the affected category
- Plugin conflict resolved by disabling one plugin -- deactivating "Post Grid" (free) breaks the [post_grid] shortcode entirely, confirming Combo Blocks Pro depends on it rather than replacing it
- A simple deactivate/reactivate of the plugins -- this did not resolve it
Reproduction steps:
1. Create a new category (e.g. via Posts -> Categories), assign it to at least one published post
2. Create or duplicate a Post Grid instance, set its "Post Taxonomies & terms" filter to this new category
3. Embed the grid via [post_grid id="X"] on any page (even a brand-new, never-viewed page)
4. Result: "No post found" -- even though the same grid configuration works perfectly for categories that existed before Combo Blocks Pro was activated
I tested this precisely: duplicating a working grid (filtered by an old, pre-existing category, correctly displaying images) and changing only the category filter to a newly created one immediately breaks it, with no other setting touched. This strongly suggests the plugin caches or snapshots the list of valid/known taxonomy terms somewhere (e.g. a transient or option) at some point around license activation, and this cache isn't invalidated when new categories are created afterward -- the term shows correctly in the admin term-selector dropdown (which reads live data) but is not recognized when the actual front-end query runs.
Could you confirm whether this is a known caching issue, and how to force the plugin to refresh its taxonomy term cache? A workaround or patch would be very helpful.
Thanks,
Louis Stöter