Last Updated on September 8, 2023 by Christopher G Mendla
With the evolution of WordPress, Gutenberg blocks have emerged as a revolutionary tool, transforming the way we edit content. But what happens when you transition from the classic editor and face unsupported blocks? Here’s how to handle them effectively.
The Transition from TinyMCE to Gutenberg Blocks
Before Gutenberg blocks took center stage, many of us, including me, relied on the tinyMCE editor – particularly the classic editor. It provided a way to format content seamlessly.
While I utilized the TinyMCE plugin for advanced editing, Gutenberg’s concept grew on me. The benefits of using blocks quickly became evident, and as a result, I decided to make the shift, parting ways with the TinyMCE plugin.
However, this transition wasn’t without its challenges. When revisiting and editing older posts, I encountered unsupported blocks. Why? The editor was searching for the now-removed TinyMCE plugin, leading to errors.
Migrating Classic Paragraph Blocks to Gutenberg
During my editing ventures, I stumbled upon an error message indicating that tadv/classic-paragraph was unsupported. After some experimentation, I established a method to migrate classic paragraph blocks to Gutenberg effortlessly:
Open Both Views:
First, launch the post in both ‘view’ and ‘edit’ modes. Keeping both versions accessible allows for an easy comparison between the edited content and the original post.
Opt for HTML:
Click on the “Keep as HTML” option.
Access More Options:
To the right of the block menu, click on the three dots.
Migration:
From the dropdown menu, select ‘Convert to Blocks’.
Adjust to Preference:
Once converted, you’ll witness your content in block form. If paragraphs aren’t your desired format, simply hit the paragraph icon and alter it as needed.
Always Double-Check:
Before hitting the “UPDATE” button, compare the content in your editor with the present view of the page.
Words of Wisdom: Plugin Caution
Plugins, though helpful, require careful consideration. Excessive reliance on block-related plugins can backfire. If they become unsupported or are deleted, your future edits might become challenging.
The Power of Evergreen Posts
Editing ‘Evergreen’ posts, or content that retains its relevance and value over time, can significantly enhance your website’s appeal and usefulness. Keep them updated, and they’ll continue to serve your audience for years to come.
Dealing with <div> tags
If the above is not working, check the html for tags such as <div> . If they are present, remove them
Summary
This workflow has been reliable, easy and fast for me. I can update my posts and remove traces of legacy plugins.