Removing js/jquery/jquery.js from the exclude field breaks home page slider

Any ideas?

change slider for one that doesn’t need jquery? B-)

Nah, that doesn’t work. You can’t make that assumption that everyone will change to sliders that don’t use jQuery.

Not only did it break the slider, it also broke the hamburger menu in one of the themes I am using.

I guess I’m SOOL (redacted) then?

I’ll just add this that your response is not very helpful. I know you all answer a lot of questions here and you’re not paid to support other people’s projects, but I’ll change my 5-star review if I keep getting snarky responses. You could be more helpful or you could find someone else that wants to be more helpful in reply, instead of just shrugging it off and saying don’t use jQuery, when it’s one of the most popular options that millions of sites use. If you don’t, won’t, or can’t resolve issues where jquery in the includes folder can’t be made non-render blocking, then state what the problem is, educate me on what I could do other than just eliminating jQuery altogether.

I’ve contacted Make by The Theme Foundry, which gets a 95% in theme check, to see what they can do on their side. But it stands to reason that this is an issue to be resolved for all and simply saying don’t use jQuery is just not a good enough answer.

• This reply was modified 7 years, 4 months ago by Tony Zeoli.
• This reply was modified 7 years, 4 months ago by bdbrown. Reason: Profanity removed

Looks like ASYNC Javascript plugin helps alleviate this issue. They seem to have support for AO in the plugin. It would have been helpful if you mentioned that plugin instead of saying I should just use a theme that doesn’t need jQuery for a slider, which is ridiculous from where I sit.

sorry if my answers seem snarky @tonyzeoli, but you are indeed out of luck; if plugins (or a theme) require jquery to be available early, then (almost) the only thing to do is to exclude jquery form optimization.

(almost) because there is one alternative that _can_ work; ticking the “also aggregate inline JS” option and excluding nothing. you do risk, in that configuration, your cache size growing (very) rapidly, which actually is a sign of other problems so that’s something you’d want to avoid.

and _can_ because AO by default excludes inline JS that has document.write or nonce in it and it possible that that inline JS also depends on jquery.js in which case “also aggregate inline JS” would not work.

so this is not an easy subject ??

It would have been helpful if you mentioned that

If I would have known, I would have mentioned that ??

Okay, thank you for being so kind as to hear me and respond with an answer that is helpful. I truly appreciate you acknowledging your snarky reply and going to the next level to help me.

As far as the other plugin, interesting they have AO support, but did not notify you of that support. It seems to work fine and both sites are now using ASYNC to deal with the jQuery issue and nothing else has broken…yet.

May I suggest that plugin as an option for those who might need it.