Download the PHP package soderlind/cache-tags-for-cloudflare without Composer
On this page you can find all versions of the php package soderlind/cache-tags-for-cloudflare. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download soderlind/cache-tags-for-cloudflare
More information about soderlind/cache-tags-for-cloudflare
Files in soderlind/cache-tags-for-cloudflare
Package cache-tags-for-cloudflare
Short Description Adds Cache-Tag HTTP response headers for singular WordPress content and purges Cloudflare by tag when content changes.
License GPL-2.0-or-later
Homepage https://github.com/soderlind/cache-tags-for-cloudflare
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package cache-tags-for-cloudflare
Cache Tags for Cloudflare
Precise Cloudflare cache purging for WordPress: adds Cache-Tag headers and purges only affected posts, pages, and terms.
- Requires: WordPress 6.8+, PHP 8.3+
- Works on any Cloudflare plan — the
Cache-Tagheader and purge-by-tag are available on all plans (Free, Pro, Business, Enterprise); purge API rate limits scale with your plan.
WP-CLI
What it does
The plugin has two independently toggleable parts:
| Context | Responsibility |
|---|---|
| Tagging | Emits a Cache-Tag response header on singular posts/pages/CPTs. |
| Purging | Calls the Cloudflare API to invalidate the affected tags when content changes. |
See docs/adr/ for the key architectural decisions.
Default tags
For singular content:
Example: Cache-Tag: content,b1,b1-p42,b1-pt-post,b1-t5
Term tags use the numeric term ID (b1-t5), so they stay stable when a term is renamed or its slug changes.
Installation
-
Install the plugin using one of:
- WordPress.org — install directly from the plugin directory via Plugins → Add New and search for "Cache Tags for Cloudflare".
- Release zip — download the latest
cache-tags-for-cloudflare.zipfrom the Releases page and upload it via Plugins → Add New → Upload Plugin. -
Composer — for Composer-managed WordPress sites (Bedrock, etc.). The
wordpress-plugintype installs it into your plugins directory automatically (viacomposer/installers):The plugin has no runtime dependencies and ships its compiled
build/assets, so no build step is needed. If it isn't on Packagist yet, add the repository first: - Git checkout — clone into
wp-content/plugins/(the compiledbuild/assets are committed, so no build step is required):
- Activate Cache Tags for Cloudflare on the Plugins screen (or network-activate on multisite).
- Add your Cloudflare API token and Zone ID — via
wp-config.phpconstants or under Settings → Cache Tags (see Configuration).
Configuration
Provide a scoped Cloudflare API token (Zone → Cache Purge) and a Zone ID. Constants in wp-config.php are preferred and take precedence over the settings UI:
Otherwise configure them under Settings → Cache Tags (see Admin UI below). Saving valid credentials automatically verifies the Cloudflare connection and unlocks the purge tools.
Admin UI
Settings → Cache Tags is a React app (@wordpress/components) with two tabs:
- Purge — manual, on-demand purges by group: a whole post type (
b{id}-pt-{type}), a taxonomy term (b{id}-t{term_id}), everything on this site (b{id}), or raw comma-separated tags. The purge tools stay locked until valid credentials have been saved and verified. - Settings — toggles for header emission, auto-purge, and debug logging, plus the API token and Zone ID (read-only when defined via constants). Save settings persists the values and automatically verifies the connection; a Test connection button is also available.
Automatic purging
When Auto-purge on changes is enabled (and valid credentials are set), the plugin purges the affected tags automatically on these events:
| Event | Purges |
|---|---|
| Post published, updated, trashed, or untrashed (any transition to or from the published status) | b{id}-p{ID} + the post's b{id}-t{term_id} tags |
| Post published (draft/scheduled going live, or any save while published) | the post's permalink, purged by URL |
| Post permanently deleted | b{id}-p{ID} + its b{id}-t{term_id} tags |
| Taxonomy term edited or deleted | b{id}-t{term_id} |
Details:
- Only public post types and taxonomies are considered; revisions and autosaves are ignored.
- Tags from all triggers in a request are de-duplicated and sent as a single batched purge on
shutdown(split into Cloudflare's 30-tags-per-request batches), off the editor's critical path. - On publish, the permalink is also purged by URL in a separate request. This is the one case tag-based purging cannot cover: a response cached before the content existed (e.g. a cached
404at a URL that later becomes a real post) carries no cache tag, so only a URL purge invalidates it. URL purges must match the cached request exactly — scheme, host, trailing slash, and query string all matter. - Not triggered by: draft-only edits, comments, menu/widget/theme changes, or plugin/core updates. Use the Purge tab, WP-CLI, or the
cache_tags_for_cloudflare/purge_tagsfilter for those. - Static files (e.g. images under
wp-content/uploads/) are served outside WordPress, so they are not tagged or purged by tag.
Extensibility
The plugin exposes hooks for customizing tags and purging from your own code:
- Filters:
cache_tags_for_cloudflare/tags,cache_tags_for_cloudflare/purge_tags - Result actions:
cache_tags_for_cloudflare/purged,cache_tags_for_cloudflare/purge_failed,cache_tags_for_cloudflare/purged_urls,cache_tags_for_cloudflare/purge_urls_failed - Programmatic purging:
cache_tags_for_cloudflare/purge_post,.../purge_terms,.../purge_post_type,.../purge_all,.../purge,.../purge_urls
See the Developer guide for full documentation and examples.
WP-CLI
On multisite, --all (and the everything group / purge_all hook) purge only the current subsite via its b{id} tag. To purge every site sharing the Cloudflare zone at once, purge the global content tag directly: wp cache-tags purge --tags=content.
External services
This plugin connects to the Cloudflare API (https://api.cloudflare.com) to verify your credentials and to purge cached content by cache tag. Cloudflare is required for the purging feature; the tagging feature (emitting Cache-Tag headers) works without contacting any external service.
Requests are made only after you provide a Cloudflare API token and Zone ID:
- Verifying credentials — saving credentials or running
wp cache-tags verifycallsGET https://api.cloudflare.com/client/v4/user/tokens/verify, sending your API token (in theAuthorizationheader) so Cloudflare can confirm it is valid. - Purging cache — auto-purge on content changes, manual purges, and
wp cache-tags purgecallPOST https://api.cloudflare.com/client/v4/zones/{zone-id}/purge_cache, sending your API token (in theAuthorizationheader), your Zone ID (in the URL), and either the list of cache tags or the list of URLs to purge (in the body). No post content, personal data, or visitor information is sent.
Cloudflare is a third-party service provided by Cloudflare, Inc. By using the purging feature you agree to Cloudflare's Terms of Service and Privacy Policy.
Development
Build tooling, hooks, programmatic purging, and how to test purging (including without a public site) are documented in the Developer guide.
License
GPL-2.0-or-later.
