Venkat Raj

Hi @andrearossonero

It appears you are using Page Speed Ninja plugin and they may have to removed psi_EnableGzipCompression option from their Config.

That said, we’ll fix the issue in the next release

Hi @edsolman

Please ignore the previous reply. The query is
SELECT COUNT(*) FROM ok_postmeta pm LEFT JOIN ok_posts wp ON wp.ID = pm.post_id WHERE wp.ID IS NULL;

Make sure you are querying against the correct database, as you query should also return that number of rows with all columns.

• This reply was modified 1 year, 2 months ago by Venkat Raj. Reason: additional info

@stavrosomo Apologies for the inconvenience caused. The issue has been fixed, and you can reset password now.

Thanks for confirmation. It sounds like all files are not overwritten at once during the update

@sophiehikeseo You could go to Dashboard => WP-Optimize => Minify => Advance tab and see list of processed files. You can click on show info link and exclude your script from being processed.

Hi

If you turned on Serve cached pages to logged in users option (which tooltip says Enable this option if you do not have user-specific or restricted content on your website) You may have see admin bar at the top of page.

Here is what happens, The first visitor to a particular page is a logged in user. The page is cached with admin bar. Then when another user visits the page, the cached page (with admin bar) is served to the user. This is a bug and will be fixed in the next release.

However, you claim that it is a security breach which is not the case. Even though there is admin bar, if you try to visit the profile or dashboard, you’ll be greeted with login page, not restricted page/content.

The only possibility I see is that, you are using the same browser for two or more different user accounts. In that case the login cookies are stored in your browser, so you won’t be greeted with login page because you are already a logged in user according to your browser.

Hi @surferking,

All caching plugins add a comment to cached pages stating that it was cached by specific plugin. It is not a backlink and is never our intention, it is just an HTML comment.

Having said that in version 3.3.0 we made a change to add cache comment irrespective of WP_DEBUG value. We add reason for not being cached when WP_DEBUG is set to true

This issue does not happens when you have a robots.txt file. Unfortunately, it happens when there is no robots.txt, WordPress creates one and WP-Optimize caching script adds the comment to newly created file.

The issue has been fixed in the latest release 3.3.1

In short, it was not intentional, and we thank you for pointing it out to us.  

Please could you revise your 1* rating?  This will really encourage us to continue to improve the product and provide ongoing support.

@harwooje It seem like your (auto) updating from version 3.3.0 to 3.3.1 is incomplete. WP-Optimize no longer uses WPO_WebP_Cron_Scheduler class and it seems the update removed that class file successfully, but didn’t update the file that calls it.

Please do a manual overwrite of /wp-content/plugins/wp-optimize folder or do fresh install