New Feature Options

  • Resolved kbowson

    (@kbowson)


    5 years, 11 months ago

    Hey there,

    The new feature ‘Defer jQuery and other non-aggregated JS-files?’ that was released in the latest build was awesome. It seemed to speed things up CONSIDERABLY. But, as I’m guessing was expected, it broke a few things.

    Any way you could add some sort of exclude functionality there (just like with the original AO plugin)? Or is there some way to make this work via the original AO plugin? Was breaking out menu + a sticky widget feature

    K

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    Hey kbowson; not sure exclusions can fix this as the main goal of this is to defer jquery, chances are that it’s that deferring that breaks your menu/ sticky widget. maybe have a look at the browser console to see what JS errors you’re getting?

    Thread Starter kbowson

    (@kbowson)

    Hey there,

    Well that shows my knowledge of this stuff :). I was just thinking if it could be excluded from deferral it might prevent the breakage.

    Looked in the browser console. The only errors I saw were unrelated (one with a social sharing plugin + one with our cookie notice)

    Any way you could take a look?

    theunbox[dot]com/vinebox/

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    had a quick look, menu seems to work (tested on FF & Chrome), no?

    for the sticky widget; maybe excluding wp-content/plugins/q2w3-fixed-widget/js/ from JS optimization fixes this?

    Thread Starter kbowson

    (@kbowson)

    Sorry, should have given more context. The menu is supposed to be sticky, then when you scroll down disappear. Think it uses headroom.js. What’s also weird is that if you load the page… then refresh the page, the menu usually starts to work correctly.

    So, does excluding in the main AO settings potentially fix the issues here? I tried doing that, but might need to mess with it more.

    K

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    indeed;
    * initial load; header is sticky, widget is not
    * 2nd load; header is not sticky, widget is

    If I were you I would indeed experiment with excluding headroom and or q2w3 JS from optimization, it _could_ fix this issue (but might not ?? ).

    Thread Starter kbowson

    (@kbowson)

    Alright, but other than that… no options?

    Love this feature. Helped a ton. Would love to make it work!

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    well, the new feature is a bit of a hail-mary; it might work and if it works it can help a lot, but it won’t (and can’t) always work because it cannot take all interdependencies between scripts into account ??

    which the option is off by default B-)

    Thread Starter kbowson

    (@kbowson)

    Gotcha! Thank you!!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘New Feature Options’ is closed to new replies.