Updating Gutenberg 22.6.0
-
Hi everybody,
Question to @bernhard-reiter
As a new version of Gut was released yesterday, I uploaded (I got WP 6.9.1 and PHP 8.3).
It didn’t work well, displaying a somewhat chaotic pages layout in draft mode and making it impossible to work with, even though everything else was working fine. I had to downgrade.
What’s the problem with it? thanks
-
Wow ok.
Good news for Gut.
What a pity, Neve is my favorite and I work on it… ^-^
Thank you so much for you reactivity!
I will inform Neve asap.On another website it works:
WP 6.9.1, Gutenberg 22.6.0, with theme TwentyTwentyOne
but the plugin “Editor Gutenberg Full Width” not.
Works with several mesage’s in the console:
Block with API version 2 or lower is deprecated since version 6.9. See: https://developer.wordpress.org/block-editor/reference-guides/block-api/block-api-versions/block-migration-for-iframe-editor-compatibility/ Note: The block “uagb/post-grid” is registered with API version 1. This means that the post editor may work as a non-iframe editor. Since all editors are planned to work as iframes in the future, set theapiVersionfield to 3 and test the block inside the iframe editor.
WP 6.9.1, Gutenberg 22.5.3, with theme TwentyTwentyOne
Works with several mesage’s in the console:
Block with API version 2 or lower is deprecated since version 6.9. See: https://developer.wordpress.org/block-editor/reference-guides/block-api/block-api-versions/block-migration-for-iframe-editor-compatibility/ Note: The block “uagb/post-grid” is registered with API version 1. This means that the post editor may work as a non-iframe editor. Since all editors are planned to work as iframes in the future, set theapiVersionfield to 3 and test the block inside the iframe editor.
The screenshots I’ve made are from another website with also the warnings as mentioned above.-
This reply was modified 2 months, 3 weeks ago by
fvbussel.
@fvbussel Could you share all the errors in the console? It’s hard to tell if there’s errors preceding. The errors you shared are related to images and shouldn’t block the editor canvas iframe from loading as far as I know.
On another website it works:
WP 6.9.1, Gutenberg 22.6.0, with theme TwentyTwentyOne
but the plugin “Editor Gutenberg Full Width” not.@fvbussel Could you clarify what you meant? Are you saying that you’re experiencing the issue when that plugin (“Editor Gutenberg Full Width”) is activated? Is the issue gone when deactivating that plugin?
I can’t seem to find that plugin in the repository. Could you provide a link to it?
@bernhard-reiter
No, I’m not saying that, I just notice that.
On the first website (screenshots) I can’t see it because I have a ligt gray area without anything on it.
See Console.txt
Plugin
Also the plugin Spectra is not complete working, I can see the blocks on the left but I cannot change for example color or text px.
Plugin SpectraI’ve identified the cause. We can’t be certain that this is a theme issue. It may need to be fixed on the Gutenberg side. See https://github.com/WordPress/gutenberg/pull/75398#issuecomment-3967610213 for more details.
Update: The cause I discovered is related to the Neve theme. The problem @fvbussel is experiencing is probably due to a different cause.
-
This reply was modified 2 months, 3 weeks ago by
Aki Hamano.
@fvbussel I don’t see anything suspicious except maybe:
Client-side media processing unavailable: Browser does not support credentialless iframes. Cross-origin isolation would break third-party embeds. Using server-side processing.
It could be that it’s a fatal error, but it doesn’t sound like it should be. I’ve seen an issue mentioned somewhere with Playground that prevents the iframe from loading, caused by the Client-side media processing. So maybe it’s related. Maybe the client-side fallback needs to be tested.
Could you try disabling client-side media processing?
add_filter('wp_client_side_media_processing_enabled', '__return_false');@ellatrix
Where do I have put the code? …I’m not that familiar with PHP.
In .htaccess I’ve blocked the Header set Content-Security-Policy with a #
The editor is now visible with the latest version of Gutenberg, so I think its working.
But not full width, so the plugin “Editor Gutenberg Full Width” is not working.
In the console I see no red messages.
The other website has no Header set Content-Security-Policy thats why I thought of it.
On both website’s the plugin “Editor Gutenberg Full Width” is not working.
I’ve have to clean up and update the CSP, I think but that will not explaind why the other plugin is not working and why I have to do this with this update of Gutenberg.Sorry to make that assumption. There are some code snippet plugins available to add PHP code to your site (but I don’t recommend doing it on a live site).
Glad to hear it’s working now. Maybe it’s worth contacting the author of that plugin.
@ellatrix
I know that there are plugins but I thought I have to place the code in one of the files of the plugin.
I’m still wondering why this happened with this update. So far the updates causes no problems.I did a rollback to version 22.5.3. So the plugin I use for the width is working.
The narrow width of the Gutenberg editor is is not easy to work with.
Why this narrow width in the editor? -
This reply was modified 2 months, 3 weeks ago by
You must be logged in to reply to this topic.
