Most probably it’s an isolated case, but my global styles in the backend, somehow got damaged on an install.
How it manifests:
In the editor, the page is loading without global styles; (on the frontend they are loading normally)
when going to Global Typography, the page breaks (The editor has encountered an unexpected error.)
Error in the console: TypeError: Cannot read properties of undefined (reading ‘themeFonts’)
react-dom.min.js / at /build/index.js
In the template editor on top of the above also:
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading ‘colors’)
In Cwicly → Settings → regenerate “Global Styles CSS” → when clicked spins without finishing;
I can pinpoint to what actually caused this. But some things that have been done on this install:
tested WP 6.1 RC. (but reverted to 6.0)
tested other block plugins; (but they were deleted after)
It would be good to have some sort of “auto healing” option when those situations occurs.
The global styles got applied in the backend as soon as I change the font on any given block!
Now, I think I know more precisely in which context the problem happened.
I was building the post using reusable blocks that I created in the Theme editor context.
After importing them to the post editor, I would convert them to regular blocks in order to edit the text. In that context, the texts inculded in these blocks, all using global styels, would not reflect the font choice in the back-end but would in the front-end.
Until… I just click on the Font Familly drop down menu, I don’t even need to change the font with the font selector, and then every text element would appear with the right font in the back-end.
Are you experiencing the problem in the same context @alex ? Did you try to just play with the font selector in any of your text element to see if that fix the issue?