Hello @adaptablewebsites ,
The last several updates of the Speed Optimizer include no changes to the overall functionality of the Combine JavaScript Files feature. However, it seems that one or more JS scripts on your sites are not fully compatible with that feature.
In this case, you can try finding and excluding the problematic JS scripts from being combined. More information on the various filters you can use for this purpose can be found here:
https://www.siteground.com/tutorials/wordpress/speed-optimizer/custom-filters/#plugin-compatibility
In case you run into any troubles, you’re more than welcome to contact our Help Desk for further assistance on the matter.
Best Regards,
Svetoslav Vasev
Hi Svetoslav,
Thanks for the reply. I’ve done some further debugging in the browser console while the “Combine JavaScript Files” setting is active, and I’ve found the specific cause of the breakage.
When the files are combined, the resulting script throws a fatal syntax error:
Uncaught SyntaxError: Octal escape sequences are not allowed in template strings Source: siteground-optimizer-[hash].js
This is followed by a secondary load-order error: Uncaught ReferenceError: jqueryParams is not defined
It appears the optimizer is pulling a script—likely a Divi module or a third-party library—into the combined file that contains a backslash followed by a number (e.g., \033) within a backtick template string. Modern JavaScript engines treat this as a fatal error, which causes the entire combined file to stop executing. This is why the header and modules are failing to load across all my sites.
Since this is happening on multiple sites, could you check if there is a known conflict with a specific Divi script handle, or let me know which scripts I should specifically exclude to prevent this syntax crash?
Many thanks, Mark
Thank you for the provided information.
There are currently no known conflicts between specific Divi JS scripts and the Speed Optimizer’s Combine JS Files feature that we’re aware of.
I’m afraid we don’t have a suitable environment to investigate this further, however, we’ll be more than happy to review the issue on one of your sites. For this purpose, please get in touch with us via the Help Desk in your SiteGround account.
Best Regards,
Svetoslav Vasev
Many Thanks for your quick response. I haven’t the time.
I’ll just turn off the setting in the optimiser on all 20 sites
Many Thanks, Regards Mark
Hello @adaptablewebsites,
We have attempted to replicate the reported behaviour on a default WordPress website that is using Divi, however, we weren’t able to replicate it after numerous different attempts.
Taking this into consideration, it would appear that the issue is most likely coming from a specific Divi module, or a different plugin that the websites share.
In this case, the best course of action would be for you to contact us via the Help Desk in your SiteGround account, as this would allow us to replicate the issue and provide us with the required access to investigate, troubleshoot, and resolve the issue.
Best regards,
Ivaylo Stoyanov
Hi Ivaylo,
That is strange. To assist your team in replicating this, I have set up a test environment where the issue is currently active:
https://marka320.sg-host.com/
You will notice the header fails to appear on scroll. If it doesn’t happen immediately, please check via Incognito mode.
The browser console explicitly identifies a fatal syntax error in the file generated by the Speed Optimizer:
Error: Uncaught SyntaxError: Octal escape sequences are not allowed in template strings.
Source: siteground-optimizer-…js
Since this error causes the entire combined script to fail, the dynamic Divi elements cannot initialize. Hopefully, this live environment allows your team to see exactly how the “Combine JavaScript Files” feature is mishandling the script strings during the minification/combination process.
Many Thanks,
Mark
PS this:
Error: Uncaught SyntaxError: Octal escape sequences are not allowed in template strings. Source: siteground-optimizer…e1aead79e37.js:2275
Plugin Support
kamenk
(@kamenk)
Hello Mark,
Due to security and privacy regulations (GDPR), we are unfortunately unable to directly debug or access the website from the publicly shared information alone, even if the website was created by you.
To assist further, I have already opened a support ticket on your behalf in your Client Area. To begin the investigation on our end, please open the ticket (Client Area -> (?) -> View Help Center -> Support History -> Post a reply ) and confirm that we may proceed with the debugging process. This confirmation will provide us with the required authorization, access, and internal tools needed to properly investigate the issue in depth.
Once we receive your confirmation through the ticket, we will continue with the troubleshooting.
Kind regards,
Kamen Kumanov
-
This reply was modified 1 day, 19 hours ago by
kamenk.
-
This reply was modified 1 day, 19 hours ago by kamenk.
