So suppose you have one page/ post which for whatever reason you don’t want Autoptimize to act on? Simply add this in the post content and AO will bail out;
<!-- <xsl:stylesheet -->
Some extra info:
- Make sure to use the “text”-editor, not the “visual” one as I did here to make sure the ode is escaped and thus visible
- This bailing out was added 5 years ago to stop the PHP-generated
<xsl:stylesheet from Yoast SEO from being autoptmized, if I’m not mistaking Yoast generates the stylesheet differently now.
- The xsl-tag is enclosed in a HTML comment wrapper to ensure it is not visible (except here, on purpose to escape the HTML tags so they are visible for you to see).
Failure is the prequel to success!
Sorry about that, I’m new to CI-testing and quite exited about seeing how useful it can be. Carry on!
Took a ride to the future earlier today. Rather pleasant, but for the time being we’ve got to make do with our past … :-)
So I love Firefox’ quantum leap, huge improvement, but the way they’re plugging Pocket was bugging me. I ended up diving under the hood (as in about:config) and setting extensions.pocket.enabled to “false” seems to hide Pocket nicely. Now back to work!
[Updated 23/06 to reflect newer versions 2.1.2 and 2.2.1]
Heads-up: Autoptimize 2.2 has just been released with a slew of new features (see changelog) and an important security-fix. Do upgrade as soon as possible.
If you prefer not to upgrade to 2.2 (because you prefer the stability of 2.1.0), you can instead download 2.1.2, which is identical to 2.1.0 except that the security fix has been backported.
I’ll follow up on the new features and on the security issue in more detail later today/ tomorrow.