Autoptimize, Divi and IE11 not working together

I could provide you with a code snippet that disables AO when a IE11-like useragent is found in the request, but this will only work if you have no page caching off course, which you do have (Litespeed Cache).

So instead you’ll have to deep-dive in AO settings to find out which settings is breaking things. First and foremost try to identify what is breaking your site by just disabling CSS or JS or Image optimization (incl. lazyload). Once you know that, dive in and try identify what code/ files (CSS or JS) are responsible for the broken feature and try excluding that.

If the problem is with JS, chances are you’ll find useful information on your browser’s developer console.

There’s more info in the troubleshooting tips and info on exclusions in the AO FAQ.

hope this helps,
frank

Ok Frank

Going in! see you on the other side ??

brb, going to put on my swim costume

Ok, so the problem turns out to be this setting:
https://prntscr.com/pyypuk

Aggregate JS-files? – Aggregate all linked JS-files to have them loaded non-render blocking? If this option is off, the individual JS-files will remain in place but will be minified.

If I disable this setting the site works fine in IE.

So what now? What is the impact if I disable this option?

well, you could try to leave “aggregate JS-files” on and instead try if excluding wp-content/themes or wp-content/plugins helps? and if so try to be even more specific (e.g. try targetting the Divi plugins you’re using)?

Hi Frank,

Ok, I have added both exclusions in individually. and tested.

adding wp-content/themes ONLY: Solves the problem
adding wp-content/plugins ONLY: Solves the problem
adding both: Solves the problem

removing them both brings backs the problem.

So I’m confused…

This is what is shown in the developer console: https://prntscr.com/pyz9ae

• This reply was modified 5 years ago by BlueSteam.

OK, easy way out; exclude theme JS and be done with it.

but you could off course keep theme JS aggregated and now try to exclude each plugin individually to see which one helps fixing this, to keep as little as possible excluded?

the plugin exclusion fixes it AND the css exclusion fixes it individually on their own.

so which one is the problem area to focus on?

I would focus on plugins, as that will probably allow for the smallest possible exclusion (excluding your entire theme’s JS from aggregation would probably have a bigger impact).

alright! ?? diving in again….lol

you’re awesome Frank…thank you.

brb

ok!!! progress!

it is this plugin: divi-mega-pro

I am not using it at the moment but I plan to.

Is there a way to determine WHY this plugin is not playing nice?

no idea, best would be to liaise with the plugin’s developer I guess ??

hmmm…ok…but wouldn’t it be the same if that developer said to me

“Check with the developer of Autoptimize why his plugin isn’t caching my plugin properly?”

?

just saying…

Only thing I can contribute is the fact that the JS breaks when aggregated and works when not aggregated and that the impact is limited to IE11. The fact that some code might not work when aggregated is not something AO can fix I’m afraid and is not uncommon (hence the exclusion-fields) ??

I will open a ticket with them and see what they say.

Thanks.

you’re welcome, feel free to leave a review of the plugin and support here! ??