Version 3.2.6 incompatible with Elementor plugin

Any development on this subject?

You have a good plugin but since version 3.2.3 the caching functionality has been a disaster.

Hi,

Apologies for the delay on this, are you using the free or premium elementor plugin. Can you check your file permissions using this guide: https://www.malcare.com/blog/wordpress-file-permissions/
If the issue is only present on one site and not another then it sounds like the issue is to do with that particular setup.

Are the themes, WP versions, PHP versions and plugins all the same in both versions?

I checked the permissions and everything is fine.

I remember the facts, again:
– 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.

Hi @webpart

Do you see this header? WPO-Cache-Status: not cached in the served pages?

If you enabling debugging do you see any entries in the debug.log files?

As I sent you about 3 weeks ago, 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

Hi @webpart

Thanks. It is just warning thrown during testing webp conversion tool.
We’ll investigate this cache issue further.

Any development on this subject?

We’re still stuck with version 3.2.3 because the cache doesn’t work in later versions.

@webpart We are unable to reproduce the issue at our end. So there is no development on this subject. Cache is working fine for other users. Even if there is an issue with upgrading from 3.2.3 to new version, if you disable/enable cache or deactivate/activate plugin, the issue should be resolved.

I mean, those actions will add WP_CACHE constant to wp-config.php file, advanced-cache.php file is generated, etc. ie. everything that is needed for caching will be generated once you deactivate/activate the plugin.

We can only proceed when there is a way to reproduce the issue

After upgrading to version 6.1 of wordpress, I tried again to update your plugin to version 3.2.9.
To my amazement, the cache finally worked right away without even having to disable/enable the cache or the plugin.

However, following your suggestion, I tried to disable/enable the cache as well as the plugin.
In either case, the cache stopped working.

This is crazy. I definitely lost confidence in the plugin !!!

Do you have nothing to say about what has been reported?
Have you given up on putting the cache to work?

I did some more tests, and these are the verified facts:

1) after reverting to version 3.2.3, it is necessary to disable/enable the cache and save for the cache to work in this version.

2) after updating to version 3.2.9, the cache is working without doing anything else after the update; however, if you purge the cache (clicking on purge cache or doing the disable/enable of the cache) it will not work.

It is not possible to keep reverting to 3.2.3 and later updating to 3.2.9 whenever the cache is purged (for example after updating any plugin).