Version 3.2.6 incompatible with Elementor plugin

@webpart Could you please try to check the option “Asynchronously load CSS files from Google Fonts” from WP-Optimize > Minify > Fonts and check if it helps to fix the issue?

Yup. The problem disappears.
So, should I check this option permanently?

@webpart Yes, you’ll have to check the option “Asynchronously load CSS files from Google Fonts” from WP-Optimize > Minify > Fonts

Very good. Thanks.

I also take the opportunity to ask if there is any known problem of incompatibility with the Elementor plugin, or any other, at the cache level, since it doesn’t work correctly in version 3.2.6.
Apparently it preloads but it doesn’t actually cache.
Clicking on pages also does not cache.

I reverted to version 3.2.3 where everything is OK.

Thank you for information and directions.

@webpart There no issues reported with Elementor and should work fine with Elementor plugin, could you please try to purge the cache and preload again and check if it generates the cache files?

I purged the cache and preloaded it again.
I also clicked several times on each page.
It is confirmed, with version 3.2.6 it does not cache.

I deactivated each of the plugins used and the situation remains. Does not cache.

I reverted back to version 3.2.3 and everything works fine again.

Thank you for analysis and information urgently.

@webpart Okay, I’ll report this to our development team for further investigation and update you soon.

Thank you for your time and patience.

Any development on this subject?

Even today I tried to update to version 3.2.6 and did countless experiments (purge the cache several times, save settings, …) and nothing worked.
As soon as I reverted back to version 3.2.3, the cache immediately started working again.

I await your news urgently.

Is the resolution for this issue included in the now released version 3.2.7?

Hi @webpart

Sorry for the delay. This thread was slipped out from my watch list.

There has been a fix related to google fonts in version 3.2.7

FIX: Correctly recognizeinheritin google fonts async loading

If you still experience some issues, could you please provide more information?

I mean, details like
1. which widget/block in elementor causes issue
2. Steps to reproduce

When we have these details, we will surely release an update with a fix to the issue. Thanks for your time.

Today I tried to update to version 3.2.7 and did again countless experiments:
– I purged the cache and preloaded it again several times
– I saved the settings several times
– I also clicked several times on each page
and nothing worked.

It simply does not cache any pages.
It has nothing to do with Elementor because I disabled all plugins and the problem remains.

As soon as I reverted back to version 3.2.3, the cache immediately started working again.

But then I did another experiment that intrigued me.
I made a duplicate of the site using the Duplicator Plugin.
And in that duplicate, the cache works correctly in version 3.2.7.
Is it because it is a new installation? What will it be?

Hi @webpart

The only possibility I can think of is file permission issues. May be your setup doesn’t allow WPOptimize to create folder and files?

Add define('WP_DEBUG', true); define('WP_DEBUG_LOG', true) to your wp-config.php file and let me know entries you have found in wp-content\debug.log file

The content of the debug.log file is as follows:

[09-Oct-2022 10:08:48 UTC] PHP Warning: unlink(C:\PARTEICO_wwwroot\PARTEICOBCS/wp-content/uploads/wpo/images/wpo_logo_small.png.webp): No such file or directory in C:\PARTEICO_wwwroot\PARTEICOBCS\wp-content\plugins\wp-optimize\vendor\rosell-dk\webp-convert\src\Convert\Converters\BaseTraits\DestinationPreparationTrait.php on line 73

@webpart This warning has no relationship with caching feature. But still reveals that your hosting setup has some file permission issues. May be the disk is full?

Make sure you have permalinks enabled and properly set.

Permalinks are enabled and properly set.
Nothing detected on the web server (disk, permissions, …).

I remember the facts:
– with version 3.2.3 the cache works fine;
– on a test site, made with the Duplicator plugin after the source site has been updated to version 3.2.9, and installed on the same web server, the cache also works fine.

Something is wrong with upgrading from version 3.2.3 to a later version on existing installations.