• Plugin Author Frank Goossens

    (@futtta)


    As already mentioned in previous exchanges here, I’ve started working on 1.7.0. This is on the feature-list:

    • update css & js optimization components to most recent versions
    • add css exclusion
    • remove legacy cdn & yui support, replacing CDN with something simpler
    • better lay out of the admin-page
    • update translations
    • clear cache of w3tc, hypercache, fast cache, faster cache, …

    Goal is to release a first test-version in October (maybe next week) and to push the final version out in November.

    So why do I need help?

    1. For testing the subsequent test-releases (based on trunk)
    2. To provide translations (based on a POT-file, using a gettext-compatible tool).

    If you’re interested to help out (or if you’d like to join the actual development), give us a shout-out in the reply-box! Looking forward to working with you! ??

    https://www.ads-software.com/plugins/autoptimize/

Viewing 6 replies - 31 through 36 (of 36 total)
  • Plugin Author Frank Goossens

    (@futtta)

    interesting. I think the “defer” attribute is causing this (found some evidence of this giving problems with jQuery in IE<9) and it is one of the few changes impacting standard javascript optimization.

    Can you open up wp-content/plugins/autoptimize/classes/autoptimizeScripts.php and on line 215 change

    $defer="defer ";

    into

    $defer="";

    empty the autoptimize cache and see if that solves the problem?

    Whoo-hoo! It works! I made the edit as you suggested. All plugins are enabled. Emptied cache. Generated new cache.

    ALL fine. No problems with jQueryColorbox! And bonus: the other plugin (image lazyload plugin I paid for) also now works so I don’t have to drop it! Everything is back to normal.

    BTW, and now WP YouTube Lyte works without me having enable “Add try-catch wrapping?” in Autopmitize.

    I will continue to test Autopmitize but so far, I haven’t seen any new problems. THANK YOU. THANK YOU. THANK YOU!

    Plugin Author Frank Goossens

    (@futtta)

    Great! Now the bad news; the defer has to be in there, so the edit you just made won’t be in the release. In case of any issue, an specifically (or certainly) when using jQuery (which often is a pita to optimize), you should use the option ‘force javascript in head’ instead. Can try with that option to confirm that solves the problem as well?

    No problems! Tested. Still all good!

    I reverted back to ” $defer=”defer “; ” and enabled “Force JavaScript in <head>” as you suggested. This 2nd option works better for me now… Oddly, forcing js in the head improved load performance on my blog.

    Still able to get a PERFECT 100/100 Pingdom test score on my home page.
    HOME PAGE PINGDOM RESULT: https://tools.pingdom.com/fpt/qcFfI/https://fruityoaty.com/

    And better Pingdom scores (on average, scores increased 2 to 4 points) on pages with WP YouTube Lyte + jQueryColorbox when I enabled “Force JavaScript in <head>”.

    Autopmitize + Hyper Cache play really well together. Thank you.

    I’m a happy user, indeed. ??

    Plugin Author Frank Goossens

    (@futtta)

    OK, based on FruityOaty’s experience I’ve added a warning for users who update from 1.6.x to 1.7.0 to test their site & correct config if needed. Waiting on a couple of translations, but if all goes well 1.7.0 could get released later today.

    Plugin Author Frank Goossens

    (@futtta)

    And we’re live. Great to see a bunch of people from all over the world (Canada, France, Germany, Iran, South-Africa, Sweden, …) join in to make this happen. Thanks for all the help you guys & girl!

Viewing 6 replies - 31 through 36 (of 36 total)
  • The topic ‘Version 1.7.0: features & your help needed’ is closed to new replies.