Hi,
You can disable merging by disabling the js processing, however it disables minification also.
This is because most of the time, incompatibility problems are more common with minification than simple merging. By the way, does it work when you disable minification only?
There are a few cases where some plugin is poorly coded and it conflicts with other files when merged (minified or not), therefore the option to disable js processing exists.
However, the true solution lies with the ignore list as I referred earlier, especially if you now know there’s a problem with merging the files.
You can try to add the relevant js file to the ignore list. I usually start by adding them all and then removing one by one until I find which one causes trouble.
If you do this, you can keep merging and minification working.
If I add the minification only but no merging, there wouldn’t be any benefit in speed if your content is already gziped (few bytes worth).
Even with http2, there’s much more benefit in reducing requests by merging than to minify.
I also said there’s an option to disable merging but didn’t necessarily said that you could minify or do anything else if you disable merging. I understand some people might take it differently, but my intention with “disable merging” was to say, that you could disable the processing (merging + minification).
I have that featured planed, since it seems to be a popular request but not right now.
If you need me to help you check which file needs to be on the ignore list, let me know.
A usual file is the select2 library… they have a utf-8 encoding error for years and don’t seem to want to fix it… this however, breaks merging.