Can you try downloading and installing a fresh copy of the plugin?
Hi @vupdraft,
Yes I tried that but there are same warnings after some time
Do you have any other caching plugins activated, if so can you try deactivating them?
No, I don’t have other caching plugins. In addition, this does not happen when reverting to the previous update. It occurs only when updating to 3.3.2.
Would you be able to post your full error log using a tools such as pastebin.com?
Are you using wget to run cron from the server?
Hi @vupdraft,
The full error log only contains multiple logs regarding the same warning, so I think it’s useless to post it.
I don’t use wget to run cron from the server, but maybe this happens when opening .php pages that contains these:
header('Content-Type: application/json; charset=utf-8');
header("Cache-Control: no-store, no-cache, must-revalidate, max-age=0");
header("Cache-Control: post-check=0, pre-check=0", false);
header("Pragma: no-cache");
I’m not sure since I downgraded to the previous version, where this issue does not occur. It is only my assumption.
Can you list your plugins and theme?
Thank you for your patience and for providing such detailed information about the issue you’ve encountered with the WP-Optimize plugin.
We have successfully replicated the error on our end, and I’ve forwarded all the relevant details to our development team for further investigation.
They’re now working on identifying the root cause and will aim to deliver a fix as soon as possible.
We appreciate your effort in helping us improve our plugin and apologize for any inconvenience this may have caused. We’ll keep you updated on the progress and notify you once a resolution is implemented.
We truly appreciate your patience and cooperation.
Our development team has acknowledged the issue and it has been slated for resolution in an upcoming release.
We are committed to continually improving our plugin and ensuring it meets the needs and expectations of our users.
We deeply appreciate your contribution to improving WP-Optimize and thank you very much for being a part of our family 🙂
Hi @wpmansour
FYI: this exact issue persists as of today June 15th 2024 and has been for over 2 months now when the plugin was updated to 3.3.2
Please provide any updated status on your acknowledgement of the issue and your work to provide any update:
We have successfully replicated the error on our end, and I’ve forwarded all the relevant details to our development team for further investigation. They’re now working on identifying the root cause and will aim to deliver a fix as soon as possible.
Thank you @wpmansour
Hi @wpmansour,
The 3.4.0 update has been released but I still experience the same issue. We thank you for the dedication the team puts into this plugin, but please note that we have already been waiting for 2 months and our logs are starting to contain many of these warnings. I hope for a release of the fix as soon as possible…
Thanks.
@wabetainfo
@wpmansour
I’m here to confirm that upgrading to latest release 3.4.0 did not resolve this issue. It persists exactly as it has for the past 2 months.
Hi @wabetainfo and @hooter ,
Apologies for the confusion and the inconvenience caused by this persistent issue. I have checked the status of the release, and I can confirm that the patch to fix this issue is currently in progress. It is slated to be included in the upcoming release, which should be version 3.4.2.
We appreciate your patience and understanding. I will post an update here as soon as the fix is released.
Thank you for your continued support and cooperation.
Thank you for this update!
Yes, thank you @wpmansour ! 🙂
