Fixed a bug that blocked Framer connections in production
A WebSocket authentication bug that silently rejected Framer CMS connections is fixed, and connection errors now show their real reason.
Framer connections were failing every time in production, without a clear reason why. The cause was a mismatch deep in how the Framer library sends authentication: it expected credentials passed a specific way that only one WebSocket implementation supports, and the one running on our servers wasn't it. So every connection attempt looked unauthenticated and got rejected, silently.
That's fixed now. Framer CMS connections authenticate correctly, and if a Framer connection, sync, or collection lookup does fail for some other reason, the admin screen shows the actual error instead of a generic message.