Provide a repro, and maybe you’ll get a ‘staff response’ that has any meaning.
We can’t install every single resource you guys use, so it’s impossible to actually reproduce this issue internally whatsoever.
Since nothing was changed that should cause an issue like this, it’s likely something to do with an obscure resource.
Also, if anyone comes along with ‘just install these 150 ESX resources and it’ll happen’, they’ll promptly be shown the door as we aren’t going to install 150 resources by hand that all have additional setup requirements just to be able to reproduce some obscure issue, so it’s up to you to provide information that can be used to fix the issue. If this happens to be an automated script to set up this ESX suite, or a server dump, or whatever, it doesn’t matter, as long as it can reproducibly show the issue within 15-30 minutes.
As a quick fix, you can remove some JS-based client resources you may happen to be using, such as some ‘custom radio’ resource that seems to be popular in servers that install 500 resources.