cleared cache, reloaded, and I see the same result. (btw, this is not urgent for me, just hoping to be helpful in debugging)
It might be a CDN caching issue, with the change that was added, it would be impossible for that error to occur.
Please Login to reply.
No replies yet.
