After a bit of investigation I have found that the page in question was opened in classic edit mode and then saved. Is it possible that an edit made in classic mode could have changed the Kadence block codes? I suppose it is…
I’ve inherited this site and the default editor is classic mode for all users rather than Gutenberg which I find strange. Is there any way to overwrite the default?
Hi Nick,
This message can appear if you are using a multisite or if you are not an admin user.
As for the default editor, do you have the classic editor plugin running? Are you able to deactivate it if so?
Hannah
Hi again,
I need to clarify that the reason you were seeing this message was because you were saving the page in the classic editor. The reasons I listed above can also push out the same message, but in your case it’s being output from the classic editor. Sorry for the confusion!
Hannah
Hi Hannah
Thanks you for replying to me on this.
I am an admin on the site.
Turns out the page was edited by another user using the classic editor which I suspect disrupted the underlying block code for Kadence. I have moved onto creating the page using the theme’s page builder (Fusion) just so I could provide a similar design for them.
Is there a way of making pages created by Gutenberg Editor open in Gutenberg editor by default to stop them being edited by the classic editor in error? At the moment when users hover over the page title in the pages menu they see a choice of options to open it:
Edit (which is the classic editor) – Fusion Builder Live – Gutenberg Editor.
I am used to just seeing ‘Edit’ and that opening up the page in Gutenberg.
I did install the WordPress Classic Editor plugin to allow users to switch between editors but it failed to switch to Gutenberg (possibly due to javascript errors caused from the Avada theme). Perhaps that is why ‘Edit’ doesn’t open Gutenberg?
Thanks
Hey,
When the classic editor is installed your pages and posts will automatically default to that. I don’t know a workaround for this, unfortunately. You could reach out to WordPress support and see if they know of anything!
Hannah