Moderator
James Huff
(@macmanx)
Volunteer Moderator
I’m not seeing this problem myself under WordPress 5.6 and Twenty Twenty-One 1.1.
This may be a plugin conflict, or a conflict with your child theme. Please attempt to disable all plugins, and switch to the default Twenty Twenty-One parent theme. If the problem goes away, enable them one by one to identify the source of the problem.
If you can install plugins, install Health Check. On the troubleshooting tab, you can click the button to disable all plugins and change the theme for you, while you’re still logged in, without affecting normal visitors to your site.
Hi @macmanx ,
Thank you for your immediate reaction.
I use WP 5.6 and 2021 version 1.1.
I now have Akismet, Hello Dolly, Healthcheck and Gutenberg as plugins.
Healthcheck tells me the imagick PHP component is not active, this is the only minor performance point it mentions (except unactivated plugins NexGen and NexGenPlus).
I used the Twentytwentyone theme (without child theme). I added a paragraph in the widget area saying ‘Hello World’ and when saving there is a message on the bottom left side saying : there was an error [object Object] and the saving process doesn’t complete, I have to leave the page unsaved. Same thing on Twentytwenty without child-theme.
Thanks for your help.
Etienne R
I’m also can’t replicate the same issue on my setup with WordPress 5.6
@mukesh27 @macmanx ,
Thank you for your time and efforts.
Apparently, this is not a 2021 issue, I have the same problem with 2020. I believe it is a compatibility issue with Gutenberg as everything works without the Gutenberg plugin.
Therefore I consider this point as resolved
Regards
Etienne R
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Since Gutenberg is now built into WordPress as of a few major releases back, the Gutenberg plugin itself is now just a testing ground for upcoming features and as such can’t be guaranteed to be stable.
You should only ever use the Gutenberg plugin if you want to use or test upcoming features.
Hi @macmanx ,
I’ll live without it.
Sorry for the burden and thanks again.
By the way, this bug was already reported in the Gutenberg Support.