Support » Plugin: Autoptimize Beta » 1.9.0 breaks JS

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Frank Goossens

    (@futtta)

    Now that is one great support request Elise, thanks for the detailed info!

    It seems -not sure why yet- autoptimize adds a semi-colon where it should not. i propose to start out adding “mytheme_urls” to the comma seperated JS exclusion list (and if that doesn’t work, maybe “potentialAction” as well).

    I’ll run some tests and come back with here once I know why the semi-colon got added.

    Hey!
    I can confirm this behaviour, but as I’ve found on my installation, it seemed to be caused not by update of Autoptimize, but by the update of WordPress SEO plugin, that “Implemented new sitelinks search box json+ld code” (according to their changelog).

    In their latest update they added a script of type "application/ld+json" which was inproperly processed by Autoptimize.

    I’m not sure this is the same case, though, yet the symptom is the same. ^^’

    Plugin Author Frank Goossens

    (@futtta)

    Thanks for confirming Grief-of-these-days, this might be the reason for most issues I’ve seen mentioned the last couple of days. I’ll investigate and might push out a version which excludes “potentialAction”.

    Plugin Author Frank Goossens

    (@futtta)

    Pushing out 1.9.1 now, which will exclude WP SEO’s “potentialAction” by default.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘1.9.0 breaks JS’ is closed to new replies.