Thanks for reporting that – I just noticed it myself around the same time! We’ve recently made some backend changes to this system and clearly missed a CORS setting somewhere. We’ll get cracking on it now. Cheers!
Hi again, we’ve done some research into this issue and it’s possible that it’s an unintended consequence of how we migrated from the old site to this new one. We have been able to reproduce it here, but in all cases either a refresh or signing out and signing back in cleared up the issue.
@twisted1919 could you a hard refresh, and if that doesn’t work sign out and sign back in, and let us know how that works? Thanks!
@rosssimpson - works now, thanks for fixing
Great! Thanks for confirming, and sorry for the inconvenience.