Last update dont works well in backend

My mistake,

Please update to 2.7.6 and it will work again.

Thanks

Thx! Now is fine!

We are on the latest version but are experiencing an inconsistent behavior here.

We are using Woocommerce, on the Cart page when logged in, FVM works fine.

But on the Checkout page, also logged in, FVM is not adding the CSS inline or doing anything at all.

It’s weird that in some logged in pages it works, and in other doesn’t.

@fariazz that’s the default behavior.

We don’t process the checkout page for compatibility reasons.
The logged in pages are also disabled by default, for the same reason.

Merging scripts and doing speed optimization very often triggers errors and stuff doesn’t always work on the frontend without changes, especially javascript.

We don’t want to let people install the plugin, not knowing how it works or how to configure it, and then complain later that they don’t have any sales because the checkout page is not working as it should.

Even if you are a developer, we don’t know if in the future you or your client is going to add some other plugin that changes the checkout page, and may break due to merging and minification.

In addition, many people use page editors which means, when they edit pages using those, javascript will again cause issues (merging should be disabled).
You can forcefully disable FVM deactivation for logged in users by disabling the fix page editors option, but make sure everything works and that you know what you are doing.

Thanks for the quick response @alignak ! And yes we know what we are doing, and have extensive WordPress experience ?? Appreciate you checking this is the case as I agree this can cause issues.

Just to clarify, we are logged-in on BOTH the Cart and Checkout pages of Woocommerce, using the same browser/user session. See the screenshot here: https://www.screencast.com/t/dxUfzBUx

However FVM injects inline CSS ONLY in the logged-in Cart page, but not on the logged-in Checkout page.

We’ve had the setting that you mention disabled all along: https://www.screencast.com/t/t4UiwS99Ig6

I think you must check fix page editors…

@fariazz

Just to clarify, we are logged-in on BOTH the Cart and Checkout pages of Woocommerce, using the same browser/user session. See the screenshot here: https://www.screencast.com/t/dxUfzBUx

However FVM injects inline CSS ONLY in the logged-in Cart page, but not on the logged-in Checkout page.

That’s what I said. We forcefully disable minification on the checkout page, but we allow it anywhere else if you disable that fix page editors option (the cart page usually causes no issues, only the checkout page).

I will consider adding an option on the next version to change this behavior, and allow you to also merge and minify on the checkout page.
I agree that some users may want to enable minification on the checkout, despite the risk.

If you need to test this right now, you can edit the plugin inc/functions.php file on line 766 from:

if(function_exists('is_checkout') && is_checkout() === true || is_preview() || is_customize_preview()) {

to

if(is_preview() || is_customize_preview()) {

Then it will work on the checkout page as well… though I advise waiting for my next release.

@alignak thanks for your reply here! Finally getting that “mystery solved” feeling ??

It would be good to have such setting as our checkout is heavily modified and we rely on CDN caching, which means even when we clear our CDN, local ISPs still keep serving the old files and that’s caused us some minor headaches with the default behavior of the checkout page. By using FVM inline CSS we don’t have that problem.

Will wait for the setting and test thoroughly when that’s released.

Thanks so much for the work with this plugin! it’s been the best minification solution we’ve encountered