Inspecting the element shows that there is an issue with malformed HTML in the ss element for the Pinterest icon.
Screenshot of code: https://www.evernote.com/l/AG0EePTwY8ROwJCzlZ4h26_0dv1CN4o4O4w
I was able to determine that this is being caused by Autoptimize. I can exclude scripts and CSS from Autoptimize, but I’m not sure which ones to exclude. Can someone tell me which script is being corrupted through the optimization?
Answering myself again, I found that unchecking “Optimize HTML code” solved the problem.
Hi there,
I am unable to reproduce this scenario at my end. You would like to try clearing the website cache. If that doesn’t help try keeping only this plugin active to check if some other plugin is causing the problem.
Answering myself again, I found that unchecking “Optimize HTML code” solved the problem.
Glad to know you figured it out.
I have the same problem. I use a different caching plugin (W3 Total Cache) and am able to solve it by disabling HTML minify but would prefer to keep that option enabled.
Is it possible to fix this within the plugin itself? I don’t notice the issue with any other images – just Pinterest.
Thanks!
Hey all; I’m the developer of Autoptimize and I can confirm there’s a pretty serious issue with W3TC which also impacts Autoptimize (technical info available is requested) when both are installed. I, as many others I’m sure, am anxiously awaiting a W3TC update to fix that nastiness 🙂
frank
@optimizingmatters – Thanks for the additional information. I’ll be watching for an update from W3TC. Can you point to a relevant thread discussing the impact on Autoptimize? I am using the two plugins on two sites.
https://wordpress.org/support/topic/issue-with-custom-share-buttons-with-floating-sidebar-csbwfs-plugin/#post-11133660 has some info.
The technical info; AO & W3TC use the same minifier components (Mr Clay’s Minify) so those minifiers load with the same class-name. Autoptimize uses autoload to load classes when needed and if a class is already available (such as HTML minify or JS minify in W3TC) is will not try to load it again, so in that case AO uses the classes as loaded by W3TC.
FYI; some more info including workarounds in this blogpost I just wrote.
Helpful post – hopefully W3TC will get their act together quickly.
@theworldwasherefirst As @optimizingmatters mentioned, let’s wait for W3TC to fix it.
Thanks everyone. I don’t actually use Auto Optimise (just W3TC) however will wait and see if it resolves itself in the next update.
I have the same issue too.
