Title: WP Fastest Cache error
Last modified: December 28, 2019

---

# WP Fastest Cache error

 *  Resolved [altfgcom](https://wordpress.org/support/users/altfgcom/)
 * (@altfgcom)
 * [6 years, 5 months ago](https://wordpress.org/support/topic/wp-fastest-cache-error-2/)
 * Hello,
 * This is just FYI (no need to reply):
 * The WP Fastest Cache plugin (SuperCache replacement installed today) requires
   that FVM be deactivated before it can save *any* settings.
 * As it’s only a minor annoyance, we’ve decided to keep using both plugins as is.
   Your plugin, by the way, works great. Very happy with it.
 * Again, this is only an FYI post.
 * (Note: As an aside, I did check out the “Cache Plugins compatibility” post at
   the top of this page.)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Raul P.](https://wordpress.org/support/users/alignak/)
 * (@alignak)
 * [6 years, 4 months ago](https://wordpress.org/support/topic/wp-fastest-cache-error-2/#post-12322587)
 * Thank you.
 * I am aware of the decision and I reached out a few times to explain that it works,
   provided users tick the right options.
 * WPFC should work fine, as long as you disable js, html and css merging.
    But 
   I recommend using another plugin, such as w3tc or wprocket.

Viewing 1 replies (of 1 total)

The topic ‘WP Fastest Cache error’ is closed to new replies.

 * ![](https://ps.w.org/fast-velocity-minify/assets/icon-128x128.jpg?rev=1440946)
 * [Fast Velocity Minify](https://wordpress.org/plugins/fast-velocity-minify/)
 * [Support Threads](https://wordpress.org/support/plugin/fast-velocity-minify/)
 * [Active Topics](https://wordpress.org/support/plugin/fast-velocity-minify/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/fast-velocity-minify/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/fast-velocity-minify/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Raul P.](https://wordpress.org/support/users/alignak/)
 * Last activity: [6 years, 4 months ago](https://wordpress.org/support/topic/wp-fastest-cache-error-2/#post-12322587)
 * Status: resolved