Siteground Optimzer Issue

[vividground]

Hi,

When I use siteground optimzer and combine javascript files corenerstone stops loading.

Which path/files can I exclude from this combination for it to function:

Looking for some path like this for eg: /wp-content/plugins/forminator/assets/forminator-ui/css/src/form/forminator-form-default.base.min.css

[marc_a]

Hey @vividground,

Thanks for reaching out!

• In X, Pro, and Cornerstone we follow all the WordPress best practices for managing front end assets (CSS/JS)
• We also minify those assets ourselves with each release. You shouldn’t need to use another system to minify them again.
• By “minified” I mean that we run post processing to convert our human readable source files into much smaller files. Variable and function names are shortened, whitespace is removed, and other techniques are applied to produce valid javascript that takes up the least amount of space possible.
• When it comes to optimization systems, the burden of responsibility lies primarily with that system. Our files are valid javascript, and should be a valid input, but there is a possibility of failure if the system doesn’t properly parse and handle those files.
• What happens periodically, is that optimization systems like SiteGround’s minifier will not properly parse code that is already minified, resulting in broken output. There is nothing we can do about this on our end.

A good analogy would be imagining a set of physical parts that need to be shipped in a box. We take care to use space efficiently and package our parts neatly in the smallest box possible. SiteGrounds optimizer unpackages everything and sorts the parts again, then tries to repackage them in a new box. We don’t have control over that process, and there isn’t a way to ensure they don’t break things during that repackaging stage.

Our recommendation is to disable the minifier entirely. Unfortunately if you want to use it, there is the possibility of it failing.

Hope that helps.