• Resolved jotaf

    (@jotaf)


    Hi Frank!

    We’ve just started using Continual.ly on one of our sites by adding in the head section the script they’ve passed to us.

    Might be totally lost but I was under the impression that Autoptimize could not affect external files.

    The situation we are seeing is that when the option to combine JS files in Autoptimize, the bot stops working and we get a “Uncaught ReferenceError: continuallySettings is not defined” on Chrome’s console.

    What I’ve tried with no luck:

    – Adding the path to the external JS to autoptimize exclusion list
    – Deactivated the “minify excluded CSS/JS” option

    What else could we try so we are able to have JS files combined but with that external JS excluded?

    Am I doing something wrong here? (quite probably tbh)

    Thanks so much for your help

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

    (@optimizingmatters)

    OK … So do you have “aggregate inline JS” on?

    Thread Starter jotaf

    (@jotaf)

    Yes! It is activated

    Is that alright?

    Thread Starter jotaf

    (@jotaf)

    The bot started working after disabling “Aggregate inline JS” ??

    What an awesome support this plugin has, for real <3

    Kudos!

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    The bot started working after disabling “Aggregate inline JS” ??

    OK, you could also exclude the inline JS e.g. by adding continuallySettings to the commas-separeted JS optimization exclusion list.

    What an awesome support this plugin has, for real <3

    you’re welcome ?? have a nice weekend!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Conflict with Continual.ly’ is closed to new replies.