iamonlythird

Ah interesting! I still think you should go with the standard of using the html tag loading="lazy". This plugin is used specifically for optimisation and improvement on UX, so in 2022 and onwards, loading="lazy" has become the standard for lazy loading images.

@kovshenin

Testing this now as we speak, so a follow-up question.

If the cookie is present, will it still display the cached version of the page? So for example, if I load up the page (as a guest), and custom cookie named ‘_hello’ exists, will it display the non-cached version of the page?

Thanks!

Thanks. So I can simply set the javascript cookie as followed:

document.cookie = "_prefix_mode=dark; max-age=129600; path=/;";

And it will work with Surge.

Will this issue be fixed by next update? If not, please let us know as we will need to swap to a different plugin. Our users are continuously complaining about this. Thanks.

Also, the solution you posted at the other thread is not working.

To recreate this issue:

On wp-login screen, type username and the wrong password. Hit the login button. Then the recaptcha icon will hover over the login button as shown here:

View post on imgur.com

Also, why are you adding an About page linked to the Dashboard, and not under the myCred (points) menu? I mean, what are you even thinking?

That is just another example of how spammy this plugin is.

It didn’t used to be like this when they previous developer was running it.

This is correct, as noted by Google here:
https://webmasters.googleblog.com/2016/11/mobile-first-indexing.html

The local thumbnail version works fine and appears to validate.

Frank, I suggest you add a note about this issue for other users, because as it stands currently, all sites using this plugin who do not have the local cache option ticked are received these error messages.

Thanks again for the very prompt communication. High five!

I have investigated this further and it appears that Google is sending this error message to all platforms, meaning, this is very likely affecting all sites running this plugin.

Please have a look at the video on this article: https://bit.ly/397tl3A

There you have one example of a video that Google flagged.

Frank, I don’t think this should be overlooked. Please let me know what I can provide you to troubleshoot this issue further.

Google has a guide here that may be very relevant: https://developers.google.com/search/docs/data-types/video

• This reply was modified 5 years, 1 month ago by iamonlythird.

I believe you may be right, please see these:
https://stackoverflow.com/questions/51255283/autoplay-iframe-youtube-video-in-safari-11

https://stackoverflow.com/questions/48601937/safari-mobile-youtube-iframe-api-autoplay

However, this answer seems to offer a solution:
https://stackoverflow.com/a/48707260

And we have multiple solutions on this Q&A (not the accepted answer which is dated):
https://stackoverflow.com/questions/46745684/muted-autoplay-videos-stop-playing-in-safari-11-0

Any chance you could test this out and see if you can implement it into next version? Thanks again for the awesome plugin.

Frank, can you please ensure this bug is fixed in the new version? I am running the github version on a high trafficed production site.

Frank, the man!

Frank, we are indeed using domain mapping via the “WordPress MU Domain Mapping” plugin. I have implemented the fix (posted on the other thread) and it is working, and files appear to be compressed properly.

Is there any way you could implement this fix into the next update of this plugin?

Checked the logs with my host (this is a dedicated server so I have access to everything), the mod_security rule that is broken is the brute force one. The login screen reloads a few times and the rule is triggered.

After countless of testing, my host advised to stop using this plugin.

Obviously, I don’t want to unless if it is the only way. This has been a great reliable plugin until now. =)

Is there anything else I, or we, could do to resolve this issue?

I found this thread here where you stumbled upon this issue apparently:

https://www.ads-software.com/support/topic/autotimize-is-returning-406-error/

How would I disable JS/CSS/HTML when I can’t accept wp-admin of the sub-sites with Autooptimize enabled?

I have a feeling this issue is not local and affects other installations on multisite. Can you please verify if it works on multisite environment for you?

EDIT: The error only appears when you try to access wp-admin of a sub-site, with this plugin enabled.

• This reply was modified 6 years, 1 month ago by iamonlythird.
• This reply was modified 6 years, 1 month ago by iamonlythird.

Thank you!