Option to purge after update?

Hi,

That is a good idea (we had this on older versions), but it would break your site if you have a cache plugin that is not supported.

For example, we could clear our cache but the old files would still be referenced on the full page cache. Unfortunately, each caching plugin has it’s own method of purging their cache, so I can only support those that are the most popular (list is on the faqs page).

I recommend people to purge the cache manually (both the plugin and any other cache plugins) after major updates, to make sure everything runs smooth.

Yea, but now also break site if someting is updated (eg. via auto update).
– I propose new option in settings panel for this – default disabled.
– Next, maybe define some action after purge for others?
– or hook in fastvelocity_cache_purger() ?

Something to make it easier to work with other plugins.

It won’t break anything if you auto update, because the same js and css files will be shown for a week or until you purge them manually.

Also the upgrader_process_complete doesn’t always work. There are a few scenarios where updating or installing doesn’t trigger anything (it’s not that simple).

If you want to programmatically purge our cache, either from another plugin or manually, you can do it using this code:

# Purge WP Super Cache
if (function_exists('fvm_transients_purge')) {
    fvm_transients_purge();
}

This forces new files to be generated, but keeps the old files intact for a few more days, just in case they are referenced somewhere else.