webheadcoder

<p>W3 Total Cache and WP Super Cache are great caching plugins, but they do not know when a widget is updated.  WPEngine is the best place to host your WordPress installation, but their caching system is no smarter when it comes to updating widgets and menus.  I created this plugin because my website did not see any changes when saving widgets or menus using these caching systems.  Clear Cache For Me will purge ALL your cache each time you do a save without having to press an additional button.  It may be overkill, which may be why it’s not built in, but some people need simplicity.</p>
<p>In addition to clearing those pesky caching engines, Clear Cache for Me can force your browser to reload your current theme’s CSS and JS files.  I modify my theme’s CSS and JS files every so often and always have trouble with the browser not getting the latest version.  So now after clicking on the “Clear Cache Now!” button on the dashboard the browser will be forced to reload the current theme’s CSS and JS files.  If you do not click the “Clear Cache Now!” button, the browser will cache the CSS and JS files like it normally does.</p>
<p>The popular Qode themes has a options to set your own custom CSS and JS.  Sometimes you may not see your changes for a long while because your browser is trying to get the cached file.  Whenever you save your Qode’s options, the CSS and JS files will be forced to reload in the browser on the public side.</p>
<p>Works with the following caching plugins:</p>
<ul>
<li>Autoptimize</li>
<li>Breeze Cache</li>
<li>Cache Enabler</li>
<li>GoDaddy Cache</li>
<li>Kinsta Cache</li>
<li>LiteSpeed Cache</li>
<li>Elementor (CSS cache)</li>
<li>Premium Addons for Elementor</li>
<li>SiteGround SuperCacher</li>
<li>Super Page Cache</li>
<li>WP Fastest Cache</li>
<li>WP Optimize Cache</li>
<li>WP Rocket</li>
<li>WP Super Cache</li>
<li>W3 Total Cache</li>
<li>WPEngine Cache</li>
</ul>
<p>Clears all cache for following actions (requires a caching system above to be active):</p>
<ul>
<li>When Widgets are saved.</li>
<li>When Customizer is saved.</li>
<li>When Menus are saved.</li>
<li>When a fields in Advanced Custom Fields are saved.</li>
<li>When a Contact Form 7 form is saved.</li>
<li>When a Formidable Form form is saved.</li>
<li>When WooThemes settings are saved.</li>
<li>When NextGen Gallery albums and galleries are updated (beta – may not clear cache on all actions).</li>
<li>When Qode options are saved this plugin forces browsers to reload the custom css and custom js.</li>
<li>When a WP Forms forms or settings are saved.</li>
<li>When WooCommerce settings are saved. (Cache should already be clearing when products are saved.)</li>
<li>When settings from the Insert Headers and Footers plugin by WPBeginner are saved.  </li>
<li>When Settings from a settings page is saved.  This includes settings from WordPress core, Yoast SEO, and most other plugins using the Settings API.</li>
<li>When WordPress is updated.</li>
<li>When plugins are updated, activated, and deactivated.</li>
<li>When WordPress, plugins, and themes are automaticallly updated.</li>
</ul>
<p><a href="https://webheadcoder.com/clear-cache-for-me/" rel="nofollow ugc">See the plugin’s homepage for more details</a>.</p>
<p>Note:  Since some caching systems run in the <code>shutdown</code> hook, this plugin also runs in that hook.  This means if PHP does not have enough time, some code including any hooks within the <code>ccfm_clear_cache_for_all()</code> function are not guaranteed to run.  If you need code to run, consider using the <code>ccfm_clear_cache_for_me_setup</code> hook.</p>
<h3>Developer Options</h3>
<h4>ccfm_supported_caching_exists</h4>
<p>Use this filter to determine if this plugin should do anything including showing the button on the dashboard.  Return true if a caching system is supported.<br />
Default: True if any of the supported caching systems is active.<br />
See Example 1 below.</p>
<h4>ccfm_admin_init or ccfm_init_actions</h4>
<p>Use this action to add hooks when cache is to be cleared.  Or do any other setup activity.</p>
<h4>ccfm_clear_cache_for_me_before</h4>
<p>Use this action to clear cache from an unsupported caching system before the default caching systems clear their cache.</p>
<h4>ccfm_clear_cache_for_me</h4>
<p>Use this action to clear cache from an unsupported caching system after the default caching systems clear their cache.</p>
<h4>Example</h4>
<p>If you were using an unsupported caching system you’ll need to identify the caching plugin’s class or function which clears the cache.  As an example, if the unsupported caching system called the <code>MyOtherCache::clear_all()</code> function, you would use the following code to get this plugin to clear the cache.</p>
<pre><code><?php
function my_other_cache_enable( $return = false ) {
    if ( class_exists( 'MyOtherCache' ) )
        return true;
    return $return;
}
add_filter('ccfm_supported_caching_exists', 'my_other_cache_enable');

function my_other_cache_clear() {
    if ( my_other_cache_enable() )
        MyOtherCache::clear_all();
}
add_action('ccfm_clear_cache_for_me', 'my_other_cache_clear');
</code></pre>


Clear Cache for Me

Purges cache on WPEngine, W3TC, WP Super Cache, WP Fastest Cache when widgets, menus, settings update.  Forces browsers to reload CSS and JS files.

Yassineh

<p>Since we’ve been using WPEngine we found no way to limit access to the LIVE website. We had problems with users mistakenly editing the live website and messing up the HTML. This plugin basically adds a checkbox to the users (allow login on LIVE) and compare the get_bloginfo(‘url’) to the one setup on the plugin’s setting page. If it matches, it means it’s live environment and will prevent users who are not specifically authorized to login into the live environment. You can bypass this check (in case you log yourself out of live) by setting up a simple cookie. This is not a security plugin, this is just to avoid stupid mistakes. The URL meta value is base64 encoded before storage to avoid the Search and Replace generally done by the “One Click” live push.</p>
<h3>Arbitrary section</h3>
<p>Please let me know if you have any suggestions or questions.</p>


Staging Users Control

A plugin to prevent certain users from logging into the back-end in the LIVE environment. You can let your users edit staging but not live.

Clear Cache for Me vs Staging Users Control