Harshad
Forum Replies Created
-
@samdobrow WP-Optimize generates cache files from your site pages/posts, so I’d request you to run a malware scan on your site including database and check for any malware on your site
@shecky Sorry to hear about your issue. for now please rollback to version 3.2.3 we are going to release a new version soon.
@chansen051341234324 It looks like some core WP-Optimize files are missing, could you please try to upload the plugin files via FTP/SFTP and then check if you still get the same error?
@telex95 Sorry to hear about your issue, for now rollback to version 3.2.3 we are going to release a new version soon which fixes the issue.
@mygumboyahoocom For now please rollback to version 3.2.3 we are going to release a new version soon.
@visureclic You can set the Cache Lifespan from WP-Optimize > Cache to 24 hours so after 24 hours the cache will be automatically purged and new cache files will be generated.
@samdobrow I suspect that’s a false positive alarm, however for security reason, I’d suggest you run a malware scan and check for the cached files.
@spiros Where do you see this Warning in PHP error logs or WordPress admin dashboard or frontend?
@schoolreadinglist For now please rollback to previous version 3.2.3, We are looking into the issue and will launch a new version soon.
@marcrix Sorry at the moment there are no logs available for database optimization.
@n1fdadmin Please go here: https://wordpress.org/plugins/wp-optimize/
And click on Advanced view on the right hand side: https://prnt.sc/4vHxi0rIIHn_
Once you are on Advanced View page scroll down to Previous version and select 3.2.3 from the dropdown: https://prnt.sc/3A8wBmSOKNyb
@clairporium Sure thing We will keep you posted.
@awmanon For now rollback the version 3.2.3, I’ll report this issue to our development team, we will release the new version soon.
@webpart @francoc30 We are looking into the issue, please rollback now to 3.2.3 version, as soon as the new version is released we will update you.
@n1fdadmin We are looking into the issue and will be fixed in next release until then could you please rollback to 3.2.3 version and check if it helps to fix the issue?