Author URI: http://www.fiftyandfifty.org/
Purge your entire Cloudflare cache from within WordPress.
Author: | Bryan Shanaver @ fiftyandfifty.org (profile at wordpress.org) |
WordPress version required: | 3.0.1 |
WordPress version tested: | 4.2 |
Plugin version: | 1.2 |
Added to WordPress repository: | 01-04-2013 |
Last updated: | 14-04-2015
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|
Rating, %: | 86 |
Rated by: | 3 |
Plugin URI: | |
Total downloads: | 13 588 |
Active installs: | 200+ |
Click to start download
|
Purge your entire CloudFlare cache, or an any specific URL, manually - or automatically everytime a post has been updated!
This plugin was not built by CloudFlare, it was built by Fifty & Fifty - a humanitarian creative studio located in San Diego, California.
Screenshots
Settings
FAQ
Do I need to have a CloudFlare(R) account to use this plugin?
Yes, setting up a CloudFlare account is free and can take less than 5 minutes.
Does it purge anything on page/post creation?
Yes, if you set ‘Auto Purge on Update’ in the admin it will fire on WordPress’ ‘publish’ hook which includes new pages/posts. Typically the page/post url won’t exist in you CloudFlare cache yet so just the homepage would get purged.
If you set posts/pages to auto-purge on add/update, does the homepage URL get purged as well?
Yes, we assume that you have a blogroll that would need to be updated on the homepage.
Are any other URLs purged automatically if I set ‘Auto Purge on Update’?
No, just the page/post permalink & the homepage. You would have to manually purge any other pages that need to get updated.
ChangeLog
1.0.0
- Initial WordPress.com version
1.0.1
= 1.0.2
* Multisite domain mapping support – thanks Ed Cooper
= 1.0.3
* Small php notice fix
= 1.0.4
* Hide logs from public-facing pages
= 1.0.5
* Update CloudFlare(R) branding
= 1.0.6
* Add more FAQ items
= 1.0.7
* Fix ajax error on post update
= 1.1
* Add option to disable logging
* Verify for WordPress 4.1
= 1.2
* Don’t die() on WordPress remote post error in API call – log instead
* Verify for WordPress 4.2