Hi,

There is no fight, please don’t misunderstand.
I’ve reached a few times to WPFC support forum, but their approach was simply to deny compatibility, to the point where they implemented a notice on wp-admin telling users to remove FVM.

Plugins on wordpress.org are free and open source. Simply WPFC has no interest in sort things out, therefore I see no reason why I should include their plugin in the list of supported plugins as well.

FVM will still work fine with WPFC but it won’t purge their cache anymore when you purge FVM. If you want to continue using WPFC, feel free to do so. It’s just that if you need to purge FVM caches, you now also need to purge WPFC after that.

That is and has always been the standard steps needed for any cache plugin (or server cache), not yet supported by FVM.

I’m not adding any notifications to tell people to remove WPFC… it’s simply, not officially supported by FVM anymore.

If you want to use a cache plugin that is automatically purged by FVM, we have a list on the description:

Auto purging of cache files for W3 Total Cache, WP Supercache, WP Rocket, Cachify, Comet Cache, Zen Cache, LiteSpeed Cache, Nginx Cache (by Till Krüss ), SG Optimizer, HyperCache, Cache Enabler, Breeze (Cloudways), Godaddy Managed WordPress Hosting and WP Engine

Just remember, to disable any features related to HTML, JS and CSS merging/minification on that cache plugin, and any cache plugin will work fine.