• Hey, fantastic plugin! I just have one quick question. Selecting ‘aggregating inline JavaScript’ seems to prevent the Jetpack Facebook widget from loading. It loads about 30% of the time (very slowly), otherwise it shows a blank space where the widget is supposed to be. I’ve tested with this option unchecked, and the widget loads 100% of the time.

    I have already excluded ‘jetpack/_inc/facebook-embed.js’ and ‘js/jquery/jquery.js’ from Autoptimize, is there anything else I can do? Or should I just refrain from aggregating Javascript?

    Thanks in advance!

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

    (@futtta)

    hiya koolkatfelix;
    AO is very much like a car; although car manufacturers don(t know where and how you will drive the car, they try to make sure it works in all normal conditions (so no, don’t try to take the car for a swim 😉 ). Indeed I (and those who work with me) don’t know where our little project ends up (given the possible combination of a theme and X plugins, almost every site is unique), but we try to make sure it works in all normal conditions. But the driving (configuration) is up to the driver (plugin user) 😉

    Enough of the shaky analogy; I’m afraid I’ve never used JP-FB, so I can’t say for sure how best to configure AO for it. But what I can say is that in general aggregating inline JS is not best practice, as it can cause severe cache issues.

    Hope this helps, somehow 😉

    frank

Viewing 1 replies (of 1 total)

The topic ‘Aggregating inline JavaScript breaking Jetpack Facebook widget?’ is closed to new replies.