clear-cache-everywhere
Last commit date
inc
3 months ago
clear-cache-everywhere.php
3 months ago
index.php
3 months ago
readme.txt
3 months ago
readme.txt
156 lines
| 1 | === Clear Cache Everywhere === |
| 2 | Contributors: apos37 |
| 3 | Tags: cache, clear cache, flush cache, performance, admin bar |
| 4 | Requires at least: 5.9 |
| 5 | Tested up to: 6.9 |
| 6 | Requires PHP: 7.4 |
| 7 | Stable tag: 1.2.1 |
| 8 | License: GPLv2 or later |
| 9 | License URI: http://www.gnu.org/licenses/gpl-2.0.txt |
| 10 | |
| 11 | Clear all cache sources in one click from the WordPress admin bar, including WP cache, transients, sessions, browser cache. |
| 12 | |
| 13 | == Description == |
| 14 | |
| 15 | **Clear Cache Everywhere** allows administrators to instantly clear various cache sources directly from the WordPress admin bar. This ensures changes are reflected immediately without waiting for cache expiration. |
| 16 | |
| 17 | **Features:** |
| 18 | |
| 19 | - **One-Click Cache Clearing:** Clears multiple cache layers across WordPress, server, and browser. |
| 20 | - **Individual Clear Actions:** Run specific cache clearing actions independently. |
| 21 | - **Admin Bar Access:** Quick purge button in the WordPress admin bar (eraser icon). |
| 22 | - **Hosting Integration:** Supports clearing hosting-level cache via configurable purge URL. |
| 23 | - **Third-Party Support:** Clears cache for supported plugins and services. |
| 24 | - **Detailed Logging:** Logs execution time for each action. |
| 25 | - **Developer Hooks:** Add additional cache clearing actions via developer hooks. |
| 26 | |
| 27 | By default, clearing the cache will execute the following actions: |
| 28 | |
| 29 | - **Rewrite Rules** – Flushes WordPress rewrite rules so permalink and routing changes apply immediately. |
| 30 | - **WordPress Object Cache** – Clears the in-memory object cache used to store database query results. |
| 31 | - **Transients** – Deletes all transients, forcing temporary data to regenerate on next load. |
| 32 | - **OPcache Reset** – Resets PHP OPcache so compiled scripts reload from disk. |
| 33 | - **Varnish Cache** – Sends a purge request to Varnish to invalidate reverse proxy cached pages. |
| 34 | - **Redis / Memcached** – Flushes persistent object cache if Redis or Memcached is active. |
| 35 | - **Fragment Cache** – Clears cached template fragments generated by themes or plugins. |
| 36 | - **REST API Cache** – Removes cached REST responses to ensure endpoints return fresh data. |
| 37 | - **Sessions** – Destroys active PHP sessions. Users may need to log in again. |
| 38 | - **Cookies** – Removes site-related browser cookies set by WordPress or plugins. |
| 39 | - **Browser Cache** – Forces browsers to revalidate and reload cached static assets. |
| 40 | - **Hosting Cache** – Triggers a configured purge endpoint to clear host-level caching. |
| 41 | |
| 42 | **Integrations:** |
| 43 | |
| 44 | The plugin already supports clearing cache for the following third-party plugins: |
| 45 | |
| 46 | - Cornerstone |
| 47 | - Elementor |
| 48 | - WP Super Cache |
| 49 | - W3 Total Cache |
| 50 | - WP Rocket |
| 51 | - LiteSpeed Cache |
| 52 | - SiteGround Optimizer |
| 53 | - Cloudflare |
| 54 | - Autoptimize |
| 55 | - Swift Performance |
| 56 | - Comet Cache |
| 57 | - WP Fastest Cache |
| 58 | - Hummingbird |
| 59 | - Nginx Helper |
| 60 | - WP-Optimize |
| 61 | |
| 62 | This plugin is ideal for developers, content managers, and site owners who need immediate cache flushing across multiple layers. |
| 63 | |
| 64 | == Installation == |
| 65 | |
| 66 | 1. Upload the plugin files to the `/wp-content/plugins/clear-cache-everywhere/` directory. |
| 67 | 2. Activate the plugin through the 'Plugins' menu in WordPress. |
| 68 | 3. The **Clear Cache** button will appear in the admin bar. |
| 69 | |
| 70 | == Frequently Asked Questions == |
| 71 | |
| 72 | = How does this plugin clear cache? = |
| 73 | It executes multiple cache-clearing actions across WordPress core, object caching systems, server-level caching, browser cache, and supported third-party plugins. Individual actions can be triggered independently. |
| 74 | |
| 75 | = Why does it take so long to clear the cache sometimes? = |
| 76 | |
| 77 | Clearing cache is not just a single action. When you click “Clear All,” the plugin may be flushing multiple cache layers: object cache, persistent cache (Redis/Memcached), OPcache, reverse proxies like Varnish, REST caches, transients, sessions, and third-party integrations. Each layer operates differently and may require disk I/O, memory resets, or network requests. |
| 78 | |
| 79 | On larger sites, clearing cache can take longer because: |
| 80 | |
| 81 | • Persistent object caches may contain thousands of keys that must be invalidated. |
| 82 | • OPcache must reload compiled PHP scripts into memory. |
| 83 | • Reverse proxies and CDNs require network-based purge requests. |
| 84 | • Transients and fragment caches may involve large amounts of stored data. |
| 85 | |
| 86 | After cache is cleared, the site must rebuild it. Themes and plugins will: |
| 87 | |
| 88 | • Re-run expensive database queries. |
| 89 | • Recompile templates. |
| 90 | • Regenerate CSS/JS assets. |
| 91 | • Rebuild REST responses. |
| 92 | • Recreate transients and computed data. |
| 93 | |
| 94 | This recaching happens on the next page load and can temporarily slow down the first request after a purge. That is expected behavior. |
| 95 | |
| 96 | If you find that clearing everything takes longer than you prefer, certain actions (such as Transients) can be disabled from the “Clear All” button and admin bar in the settings. They can still be cleared independently from the settings page when needed. |
| 97 | |
| 98 | In some cases, you may not need to clear every layer. For example, content edits typically do not require transients or OPcache to be reset. Selectively clearing only what is necessary can significantly reduce execution time. |
| 99 | |
| 100 | = Does this work with all hosting providers? = |
| 101 | This depends on your hosting provider. If they offer a cache purge URL, you can configure it in the plugin settings. For example, if you have GoDaddy's Website Security and Backups, you can navigate to Firewall > Settings > Performance > Clear Cache, then grab the Clear Cache API link to put in your settings. |
| 102 | |
| 103 | = Will this force browsers to load fresh content? = |
| 104 | Yes! The plugin sends cache-control headers to prompt browsers to reload updated content. |
| 105 | |
| 106 | = Can I add custom cache clearing actions? = |
| 107 | Yes. Developers can hook into the clearing process to add custom actions or settings. Full developer documentation is available here: |
| 108 | |
| 109 | https://pluginrx.com/docs/plugin/clear-cache-everywhere/ |
| 110 | |
| 111 | = Is there a function to trigger clearing cache everywhere? = |
| 112 | Yes! A helper function is available for you to use: `cceverywhere_clear_all( $log_results = false )`. |
| 113 | |
| 114 | The function returns the results of the cache clearing processing. Optionally, you can log the results by setting the `$log_results` parameter to `true`. This will log the results to the debug log. |
| 115 | |
| 116 | = Where can I request features and get further support? = |
| 117 | We recommend using our [website support forum](https://pluginrx.com/support/plugin/clear-cache-everywhere/) as the primary method for requesting features and getting help. You can also reach out via our [Discord support server](https://discord.gg/3HnzNEJVnR) or the [WordPress.org support forum](https://wordpress.org/support/plugin/clear-cache-everywhere/), but please note that WordPress.org doesn’t always notify us of new posts, so it’s not ideal for time-sensitive issues. |
| 118 | |
| 119 | == Demo == |
| 120 | https://youtu.be/wjCEGl2sSzQ |
| 121 | |
| 122 | == Screenshots == |
| 123 | |
| 124 | 1. Settings page and admin bar button. |
| 125 | |
| 126 | == Changelog == |
| 127 | = 1.2.1 = |
| 128 | * Update: Added option to clear Cloudflare cache |
| 129 | |
| 130 | = 1.2.0 = |
| 131 | * Update: Added `cceverywhere_before_clear` and `cceverywhere_after_clear` hooks |
| 132 | * Update: `cceverywhere_before_clear_cache` and `cceverywhere_after_clear_cache` removed |
| 133 | * Update: `cceverywhere_custom_settings` hook updated to accept `run_context` and `callback` hooks, please see updated developer docs |
| 134 | * Update: Added animated border to admin bar while it's clearing cache |
| 135 | * Update: Moved some actions to ajax while leaving sessions, cookies, and browser cache for page reloads |
| 136 | * Update: Added descriptions to each action |
| 137 | * Update: Added individual clear buttons to each action |
| 138 | * Update: Added logging of last results, displayed on settings page |
| 139 | * Update: Removed notices and `show_skipped_notice` hook |
| 140 | * Update: Added opcache_reset, varnish, redis_memcached, fragment_cache, and rest_api_cache |
| 141 | |
| 142 | = 1.1.1 = |
| 143 | * Tweak: Update admin bar spacing |
| 144 | |
| 145 | = 1.1.0 = |
| 146 | * Update: New support links |
| 147 | |
| 148 | = 1.0.2.1 = |
| 149 | * Fix: Sanitized cookie names |
| 150 | * Update: Moved scripts and styles to enqueue |
| 151 | |
| 152 | = 1.0.2 = |
| 153 | * Update: Updated author name and website per WordPress trademark policy |
| 154 | |
| 155 | = 1.0.1 = |
| 156 | * Initial Release on March 19, 2025 |