Venkat Raj

Hi @insee77,

If you enable cache, there won’t be any log messages. If you don’t want to use caching feature, we will fix this in the next release.

But it is not recommended to turn on WP_DEBUG_LOG in production site.

Hi,

Sorry to hear that. I see that you have solved the issue. Please use latest version 3.2.5 which fixes the issue.

For others who may come across this,

Please connect to your hosting server using FTP and then rename the folder wp-optimize in wp-content/plugins to something else like wp-optimize-bk

Now, you’ll be able to connect to your WP site and you can install latest version (3.2.5) which fixes the error.

Hi @linkurs,

Sorry to hear that. I assure you nothing is lost.
Please connect to your hosting server using FTP and then rename the folder wp-optimize in wp-content/plugins to something else like wp-optimize-bk

Now, you’ll be able to connect to your WP site and you can install latest version (3.2.5) which fixes the error.

Hi,

We sincerely apologize for the inconvenience cause by the update.
We have release an update (Version 3.2.5) with fix

@mraghavboob Could you please check stat function’s (PHP) return value? If it returns false rather than an array, you may end up with 755

Hi Graham,

No worries and Sorry for the delay from my side.
I believe, you have updated WPO using FTP at some point.
You need to delete an option named updraft_semaphore from your _options table to fix it.

If the problem still persist, please submit a support request here
https://getwpo.com/ask-pre-sales-question/

As I may need to take a look at your WP Dashboard

Regards,
Venkat

@grl570810 Could you please deactivate and then activate WP Optimize? That should fix the issue.

If not, please install WP Crontrol plugin and see if autosmush_process_queue event is scheduled. Even though it is a single time event, it should be there persistently.

Let me know the outcome