Topic: Fonts in Backend Problem after GenerateBlocks Update

Sonja
April 26, 2024 at 7:40 am
Hello,

after updating GenerateBlocks and GenerateBlocks Pro, the Font changes in my Backend.

Before the update, I had the same Font as on Frontage. Now it looks weird like in the Screenshot:
https://prnt.sc/iseLkQfOu2CX

On the Frontend, it looks like this, like it should
https://prnt.sc/SuatJhG_JGp2

The Font is local.

And this despite the fact that I have the following snippet active, to Show local fonts in WP block editor:
```
add_filter( 'block_editor_settings_all', function( $editor_settings ) {
    $css = wp_get_custom_css_post()->post_content;
    $editor_settings['styles'][] = array( 'css' => $css );

    return $editor_settings;
} );
```
Ying
April 26, 2024 at 11:53 am

If you open the editor, and Right Click > Inspect the editor window to open the Browser developers tools.
In the Console tab are there any Errors or Warnings ?
Sonja
April 26, 2024 at 12:28 pm

No, there are no errors.

There are these 3 Warnings:

block-editor.min.js?ver=f192218ec9fd5b103f38:26 wp.blockEditor.transformStyles Failed to transform CSS. <css input>:109:15: Missed semicolon
107 | /* placeholder focus text style */
108 | .fluentform .frm-fluent-form .ff-el-form-control:focus::placeholder {
> 109 | color: color: var(–contrast-3);
| ^
110 | }
111 |
(anonym) @ block-editor.min.js?ver=f192218ec9fd5b103f38:26
deprecated.min.js?ver=e1f84915c5e8ae38964c:2 select( ‘core/edit-site’ ).__experimentalGetPreviewDeviceType is deprecated since version 6.5 and will be removed in version 6.7. Please use select( ‘core/editor’ ).getDeviceType instead.
i @ deprecated.min.js?ver=e1f84915c5e8ae38964c:2
Knoten kann auf der aktuellen Seite nicht gefunden werden.
David
April 27, 2024 at 2:31 am

Hi there,

you have an error in your CSS.
Under the /* placeholder focus text style */
Look for the line: color: color: var(–contrast-3);
And replace that with: color: var(–contrast-3);

That will fix the error and the WP will happily load it in the editor.
Sonja
April 27, 2024 at 4:26 am

Hi David,

that did the trick. Now it is like before, Thanks.
David
April 27, 2024 at 4:38 am

Just to cover:
The issue comes from the WordPress 6.5 update
It changes the way it handles CSS being injected in to the editor.
And its really intolerant of any CSS mistakes and simply rejects all the CSS if there is a mistake.

Glad to be of help!

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.

Are you a GenerateCustomer?

Just browsing?

Fonts in Backend Problem after GenerateBlocks Update