ClassicFlare does one thing: it keeps the copy of your site that Cloudflare holds at the edge in\nstep with your content. Publish, update or trash a post, approve a comment, and the pages that\nchanged are purged from Cloudflare, along with every page that shows them.<\/p>\n\n
It does not change anything in your Cloudflare zone: no cache rules, no zone settings, no page\nrules. It only ever asks Cloudflare to forget cached files.<\/p>\n\n
ClassicFlare is built for ClassicPress 2 and works the same on WordPress. It is not affiliated\nwith or endorsed by Cloudflare, Inc. or the ClassicPress project.<\/p>\n\n
The plugin talks to one outside service, the Cloudflare API, to clear the copy of your pages that\nCloudflare holds. Nothing else leaves your server: no update checker, no licence check, no\nanalytics.<\/p>\n\n
Only contacted once you have configured an API token. Without one, nothing is sent.<\/p>\n\n
What it sends, and when:<\/p>\n\n
It never sends visitor data, personal data or post content.<\/p>\n\n
Cloudflare, Inc. provides the service. Their terms and privacy policy:<\/p>\n\n
To learn which sitemap files exist, the plugin reads your own sitemap index twice a day, on\nWP-Cron. That request goes to your own site and involves no third party.<\/p>\n\n
No custom tables. Settings live in the options table: one small autoloaded option, plus a few\nthat only load on the settings screen (the token, the zone details, the extra paths, the\nsitemap list and the result of the last purge). WP-Cron refreshes the sitemap list and runs\nretries.<\/p>\n\n
Turning on \"Delete data on uninstall\" removes all of it when you delete the plugin. Leave it off\nand nothing is removed, so deactivating to debug a conflict does not cost you your configuration.<\/p>\n\n
Licensed GPL-3.0-or-later. ClassicFlare is derived from Oh My Cache! by Buti\u00e1 Labs, keeping only\nits Cloudflare integration. That code in turn reimplemented ideas from App for Cloudflare by\nDigital Point (GPL-3.0, https:\/\/wordpress.org\/plugins\/app-for-cf\/) and Nginx Helper by rtCamp\n(GPL-2.0-or-later, https:\/\/github.com\/rtCamp\/nginx-helper). Nothing third party is bundled.<\/p>\n\n\n
Add this to or set the production token.<\/p>\n\n\n Yes. It is written for ClassicPress 2 and needs nothing from the block editor. On WordPress it also\ncatches block editor saves, after categories and tags have been written.<\/p><\/dd>\n The Global API Key can do anything to every zone in your account and cannot be limited. A token\ncan be limited to purging the cache of one zone, and revoked on its own.<\/p><\/dd>\n Comments posted from the front end are purged a few seconds later, on WP-Cron, so the visitor\ndoes not wait on a call to Cloudflare. If your site sets DISABLE_WP_CRON, make sure a system cron\ncalls The hostname in your site address is not proxied by Cloudflare (grey cloud), or belongs to another\nzone. Those URLs are reported as skipped, not failed, and are not retried.<\/p><\/dd>\n Yes, through functions or actions that do nothing if ClassicFlare is not installed:<\/p>\n\n The wp-config.php<\/code>:<\/p>\n\ndefine( 'CLASSICFLARE_CF_API_TOKEN', 'your-token' );\n<\/code><\/pre>\n\nCLASSICFLARE_CF_API_TOKEN<\/code> in the environment. The token is then never written to the\ndatabase, so it stays out of backups and staging copies, and the settings screen stops offering\na field for it. CLASSICFLARE_CF_ZONE_ID<\/code> does the same for the zone, skipping discovery.<\/p>\n\nCLASSICFLARE_DISABLE set to true switches automatic purging off, for a staging copy that shares\n<\/code><\/pre>\n\n\n
Does it work on ClassicPress?<\/h3><\/dt>\n
Why a token and not my Global API Key?<\/h3><\/dt>\n
A visitor's comment did not clear the page straight away<\/h3><\/dt>\n
wp cron event run --due-now<\/code> every minute.<\/p><\/dd>\nCloudflare says some URLs are \"not in this zone\"<\/h3><\/dt>\n
Which WP-CLI commands are there?<\/h3><\/dt>\n
\n
wp classicflare purge <url>...<\/code><\/li>\nwp classicflare post <id> [--dry-run]<\/code><\/li>\nwp classicflare purge-all [--yes]<\/code><\/li>\nwp classicflare connect [<token>]<\/code><\/li>\nwp classicflare test<\/code><\/li>\nwp classicflare status<\/code><\/li>\n<\/ul><\/dd>\nCan other plugins trigger a purge?<\/h3><\/dt>\n
do_action( 'classicflare_purge_url', [ 'https:\/\/example.com\/page\/' ] );\ndo_action( 'classicflare_purge_post', $post_id );\ndo_action( 'classicflare_purge_all' );\n<\/code><\/pre>\n\nclassicflare_purge_urls<\/code> filter adjusts the final list before it is sent, and\n classicflare_sitemap_urls teaches it about a sitemap generator it does not know.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.0<\/h4>\n\n
\n