I’m not sure why velocity is preventing wp fastest cache from saving.
It’s not FVM, it’s WPFC that shows you that message, when they detect that FVM is installed. There is nothing on FVM preventing anything, or even related to WPFC.
We always supported any cache plugin, with the only advice for people to disable html, js and css minification everywhere else, for FVM to be able to do it’s work properly.
WPFC decision to mark it as incompatible was unilateral, and I have reached out a few times to their support to seek out some joint solution for whatever issue they were having with FVM, but they never removed the restriction.
https://ww.wp.xz.cn/support/topic/message-stating-that-fast-velocity-minify-needs-to-be-deactivated/
I see, that’s sad to hear as it’s a very good combination in my opinion.
Wp fastest cache is enough for our needs for caching but velocity is way better in terms of handling css / js. I guess I’ll give it a shot there too to make them understand that if one has to go it’s going to be their plugin as there are plenty caching plugins out just as easy to setup.
Out of your experience, which caching plugin is most compatible with FVM?
I’ll also raise a ticket about an issue faced with DIVI theme’s files not being taken into account if I don’t manage to see why it’s happening.
In my opinion, wp rocket with fvm is also a great combination.
Alternatively, WP Super Cache or W3TC also should work great for any site.
I used WPFC in the past with some sites together with FVM and it was all good, until they decided to add the block. Then I can no longer recommend or use their solution.
Merhaba,
Ben FVM ve WPCF birlikte kullanıyordum çok harikaydı.Ancak son bir kaç haftadır FVM çalışmıyor gibi görünüyor.Çözülebilir bir sorunmudur?
İyi Çalışmalar
@tncykdz english please.
According to google translator… well, it depends if WPFC did any change.
Did they post anything on the changelog or put up some update recently.
In that case, you should ask for their support, as FVM doesn’t prevent WPFC to work in any way.