[Improvement] Cache purge by IDs for any post type

[aldair-meneses]

Currently, the purge by IDs functionality only supports the default post type.
This means that when trying to purge cache for pages or custom post types, the plugin doesn’t include their paths in the invalidation request.

In some cases, related content (e.g., a page that displays a list of posts or custom post type entries but is not an archive) may remain cached even after updates, since the purge process after update doesn’t cover these cases. Would be great if possible, to purge manually.

Steps to reproduce:

• Create a page (e.g., with ID 4583).
• Attempt to purge the cache by ID.
• Notice that only / is purged, and the actual page path is ignored.

Expected behavior:
The purge by IDs should support any registered post type, not just post, so that the correct paths are invalidated.

It’s common for sites to have pages or custom post types tied to dynamic content. Without proper purge support, outdated cache can cause inconsistencies for end users.

A Pull Request has been submitted to address this issue by extending purge support to all post types: #173

[dosubot]

You're right—the current purge-by-ID feature only reliably targets the default "post" type and doesn't handle pages or custom post types, which can leave related content cached and out of sync. This is due to the plugin's logic making assumptions about post types and URL structures, so it doesn't always resolve the correct paths for non-default types, especially when purging by ID.

There isn't a Pull Request #173 in the repository that addresses this yet. However, you can work around this limitation by using the c3_invalidation_items filter to add custom invalidation paths for any post type or specific content scenarios. The documentation provides examples for targeting custom post types and related paths, which can help ensure the right URLs are purged when needed [docs: filters].

If you want purge-by-ID to work for all post types out of the box, the codebase would need to generalize how it resolves post URLs and invalidation paths, ensuring it queries posts of any type and maps their permalinks correctly. For now, customizing via filters is the most reliable approach.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[hidetaka-dc]

Thank you for your contribution!
We released a new version of this plugin.
Please upgrade the plugin to v7.3.0.

Diff: https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3366827%40c3-cloudfront-clear-cache&old=3346059%40c3-cloudfront-clear-cache&sfp_email=&sfph_mail=

Thanks.