PHPackages soderlind/cache-tags-for-cloudflare - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Caching](/categories/caching) 4. / 5. soderlind/cache-tags-for-cloudflare ActiveWordpress-plugin[Caching](/categories/caching) soderlind/cache-tags-for-cloudflare =================================== Adds Cache-Tag HTTP response headers for singular WordPress content and purges Cloudflare by tag when content changes. 1.5.2(3w ago)19↓75%[1 PRs](https://github.com/soderlind/cache-tags-for-cloudflare/pulls)GPL-2.0-or-laterPHPPHP >=8.3CI failing Since Jul 15Pushed 3w agoCompare [ Source](https://github.com/soderlind/cache-tags-for-cloudflare)[ Packagist](https://packagist.org/packages/soderlind/cache-tags-for-cloudflare)[ Docs](https://github.com/soderlind/cache-tags-for-cloudflare)[ RSS](/packages/soderlind-cache-tags-for-cloudflare/feed)WikiDiscussions main Synced 1w ago READMEChangelog (10)Dependencies (18)Versions (19)Used By (0) 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-Tag` header and purge-by-tag are available on all plans (Free, Pro, Business, Enterprise); purge API rate limits scale with your plan. [What it does](#what-it-does) · [Default tags](#default-tags) · [Installation](#installation) · [Configuration](#configuration) · [Admin UI](#admin-ui) · [Automatic purging](#automatic-purging) · [Extensibility](#extensibility) · [WP-CLI](#wp-cli) What it does ------------ [](#what-it-does) The plugin has two independently toggleable parts: ContextResponsibility**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 [`CONTEXT-MAP.md`](CONTEXT-MAP.md) and the per-context glossaries for the domain model, and [`docs/adr/`](docs/adr/) for the key architectural decisions. Default tags ------------ [](#default-tags) For singular content: ``` content b{id} # site scope: b1 on single site, b{blog_id} on multisite b{id}-p{ID} b{id}-pt-{post_type} b{id}-t{term_id} # for every public taxonomy term the post belongs to ``` 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 ------------ [](#installation) 1. Install the plugin using one of: - **WordPress.org** — install directly from the [plugin directory](https://wordpress.org/plugins/cache-tags-for-cloudflare/) via **Plugins → Add New** and search for "Cache Tags for Cloudflare". - **Release zip** — download the latest `cache-tags-for-cloudflare.zip` from the [Releases](https://github.com/soderlind/cache-tags-for-cloudflare/releases) page and upload it via **Plugins → Add New → Upload Plugin**. - **Composer** — for Composer-managed WordPress sites (Bedrock, etc.). The `wordpress-plugin` type installs it into your plugins directory automatically (via `composer/installers`): ``` composer require soderlind/cache-tags-for-cloudflare ``` 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: ``` { "repositories": [ { "type": "vcs", "url": "https://github.com/soderlind/cache-tags-for-cloudflare" } ] } ``` - **Git checkout** — clone into `wp-content/plugins/` (the compiled `build/` assets are committed, so no build step is required): ``` git clone https://github.com/soderlind/cache-tags-for-cloudflare.git \ wp-content/plugins/cache-tags-for-cloudflare ``` 2. Activate **Cache Tags for Cloudflare** on the Plugins screen (or network-activate on multisite). 3. Add your Cloudflare API token and Zone ID — via `wp-config.php` constants or under **Settings → Cache Tags** (see [Configuration](#configuration)). 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: ``` define( 'CACHE_TAGS_CF_API_TOKEN', 'your-scoped-token' ); define( 'CACHE_TAGS_CF_ZONE_ID', 'your-zone-id' ); ``` Otherwise configure them under **Settings → Cache Tags** (see [Admin UI](#admin-ui) below). Saving valid credentials automatically verifies the Cloudflare connection and unlocks the purge tools. Admin UI -------- [](#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 ----------------- [](#automatic-purging) When **Auto-purge on changes** is enabled (and valid credentials are set), the plugin purges the affected tags automatically on these events: EventPurgesPost 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}` tagsPost published (draft/scheduled going live, or any save while published)the post's **permalink**, purged by URLPost permanently deleted`b{id}-p{ID}` + its `b{id}-t{term_id}` tagsTaxonomy 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 `404` at 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_tags` filter 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 ------------- [](#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](docs/DEVELOPER.md) for full documentation and examples. WP-CLI ------ [](#wp-cli) ``` wp cache-tags purge --post-type=page wp cache-tags purge --taxonomy=category --terms=news,sport wp cache-tags purge --post=42 wp cache-tags purge --tags=b1-t5,content wp cache-tags purge --urls=https://example.com/hello-world/ wp cache-tags purge --all wp cache-tags verify ``` 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 ----------------- [](#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 verify` calls `GET https://api.cloudflare.com/client/v4/user/tokens/verify`, sending your API token (in the `Authorization` header) so Cloudflare can confirm it is valid. - **Purging cache** — auto-purge on content changes, manual purges, and `wp cache-tags purge` call `POST https://api.cloudflare.com/client/v4/zones/{zone-id}/purge_cache`, sending your API token (in the `Authorization` header), 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](https://www.cloudflare.com/website-terms/) and [Privacy Policy](https://www.cloudflare.com/privacypolicy/). Development ----------- [](#development) Build tooling, hooks, programmatic purging, and how to test purging (including without a public site) are documented in the [Developer guide](docs/DEVELOPER.md). ``` composer install composer check # PHPCS + PHPStan + PHPUnit npm install && npm run build # rebuild the React admin UI ``` License ------- [](#license) GPL-2.0-or-later. ### Health Score 44 — FairBetter than 90% of packages Maintenance95 Actively maintained with recent releases Popularity8 Limited adoption so far Community6 Small or concentrated contributor base Maturity57 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~2 days Total 10 Last Release 25d ago ### Community Maintainers ![](https://avatars.githubusercontent.com/u/1649452?v=4)[Per Søderlind](/maintainers/soderlind)[@soderlind](https://github.com/soderlind) --- Top Contributors [![soderlind](https://avatars.githubusercontent.com/u/1649452?v=4)](https://github.com/soderlind "soderlind (54 commits)") --- Tags cloudflare-cachewordpress-pluginwordpresscachecloudflarecdnpurgecache tag ### Code Quality TestsPHPUnit Static AnalysisPHPStan Type Coverage Yes ### Embed Badge ![Health badge](/badges/soderlind-cache-tags-for-cloudflare/health.svg) ``` [![Health](https://phpackages.com/badges/soderlind-cache-tags-for-cloudflare/health.svg)](https://phpackages.com/packages/soderlind-cache-tags-for-cloudflare) ``` ### Alternatives [wp-media/wp-rocket Performance optimization plugin for WordPress 7691.4M4](/packages/wp-media-wp-rocket)[helsingborg-stad/municipio A bootstrap theme for creating municipality sites. 4028.8k10](/packages/helsingborg-stad-municipio)[nexxai/laravel-cfcache A handful of Cloudflare cache helpers for Laravel 13920.8k](/packages/nexxai-laravel-cfcache)[b13/proxycachemanager TYPO3 Extension that automatically flushes cached URLs within a proxy / CDN. 10114.8k](/packages/b13-proxycachemanager) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)