Sure. They are not fixes though, unless the first one works obviously and our member hasn't got back to me yet as to whether it helped (we had tried emptying the cache but not with him logged out) anyway, here goes:
1. Have the user log out, close the browser, empty the browser cache, and then log in again.
2. If it continues use Safari's developer tools and get the JSON string for vBulletin to look at.
To do this open developer tools, how to explained here: https://support.apple.com/guide/safa...-sfri20948/mac and select the network tab. When the error happens, click on the entry for that page and select the response tab. This should show what the server is sending to the computer.
3. If they are using any sort of Ad or Javascript Blocking extension, they should whitelist your site for testing purposes.
1. Have the user log out, close the browser, empty the browser cache, and then log in again.
2. If it continues use Safari's developer tools and get the JSON string for vBulletin to look at.
To do this open developer tools, how to explained here: https://support.apple.com/guide/safa...-sfri20948/mac and select the network tab. When the error happens, click on the entry for that page and select the response tab. This should show what the server is sending to the computer.
3. If they are using any sort of Ad or Javascript Blocking extension, they should whitelist your site for testing purposes.
Comment