Hi there! It looks like you have a plugin which is optimizing/minifying our JS files by generating new versions of them which is known for causing conflicts. This is visible by the name of the file which is different from the files that we publish in the release. Unfortunately, I can’t tell exactly what it is from the error message, but there are a number of plugins that do this kind of thing.
If you’re able to exclude Site Kit from these optimizations, I would expect this should resolve the issue for you. If not, our support team will be happy to dig into this with you and get to the bottom of it!
Cheers 👍
Yes we use SG Optimizer and I can exclude the JS but need to know what JS to exclude. I don’t see any that appear to be SiteKit specific.
I have already tried flushing cache on site, server and browser.
I can confirm that if I switch off the JS minification then the error disappears
Hi David, thanks for confirming the issue and the fix. I think there may be an issue with the SG plugin, but I’ve gone ahead and created a tiny plugin you can use to safely exclude Site Kit from that plugins optimizations automatically.
https://gist.github.com/aaemnnosttv/2bc6fab481236fd920dd895ea8adcfd6
Feel free to review the code first afterwards you can download the zip right from GitHub and install it manually as you would for any other plugin that isn’t on the plugin repository.
Let us know how that goes for you!
Thank you Even
I have added your snippet and can confirm that is has stopped the errors appearing.
@wicko Glad to hear that Evan’s plugin has helped to address your issue. I will close this support topic but should you have any further questions or issues in the future then please don’t hesitate to ask!
