Transforms classic editor content to blocks on-the-fly.
Convert to Blocks is a WordPress plugin that transforms classic editor content to blocks on-the-fly. After installing Gutenberg or upgrading to WordPress 5.0+, your content will be displayed in "Classic Editor Blocks". While these blocks are completely functional and will display fine on the frontend of your website, they do not empower editors to fully make use of the block editing experience. In order to do so, your classic editor posts need to be converted to blocks. This plugin does that for you "on the fly". When an editor goes to edit a classic post, the content will be parsed into blocks. When the editor saves the post, the new structure will be saved into the database. This strategy reduces risk as you are only altering database values for content that needs to be changed.
When combined with the Block Catalog Plugin, Convert to Blocks can be used to bulk convert only classic editor content to blocks. This is especially useful for sites with a combination of classic and block editor content.
The wp convert-to-blocks start WP-CLI command that converts posts iteratively in the browser without requiring any manual input. One caveat worth mentioning is that Gutenberg is a CPU intensive application. You will want to keep your computer plugged in before doing this!
- Inner Blocks Transforms is only supported with the Gutenberg Plugin 10.9.0+
- Clone the repository into your
/pluginsdirectory. - Inside the repository directory, run
npm installand thennpm run build. - Inside the repository directory, run
composer install.
NAME
wp convert-to-blocks start
DESCRIPTION
Starts a new Migration. The command prints the URL that must be opened in a browser to connect it to the WP CLI.
SYNOPSIS
wp convert-to-blocks start [--post_type=<post_type>] [--per_page=<per_page>] [--page=<page>] [--only=<only>] [--catalog] [--reset]
OPTIONS
[--post_type=<post_type>]
Optional comma delimited list of post types to migrate. Defaults to post,page
[--per_page=<per_page>]
Optional number of posts to migrate per batch. Defaults to no limit. Combine with --page to paginate.
[--page=<page>]
Optional page number to start migration from. Defaults to 1.
[--only=<only>]
Optional comma delimited list of post ids to migrate.
[--catalog]
Optional flag to only migrate classic editor tagged posts. Requires that Block
Catalog plugin is present and has been indexed.
[--reset]
Stops any currently running migration and resets the migration state.
NAME
wp convert-to-blocks stop
DESCRIPTION
Stops the currently running migration if active.
NAME
wp convert-to-blocks status
DESCRIPTION
Prints the status of the currently running migration.
Find a classic editor in the post, try to navigate away from the page. You will get an error saying your changes will be discarded. This is because Convert to Blocks converted your content to blocks on the fly and those changes will be saved when you update the post.
By default it will not.
Nested / Inner Block support does not work with Gutenberg bundled with WordPress Core <=5.7.2. This feature needs the Gutenberg Plugin >=10.9.0.
Stable: 10up is not planning to develop any new features for this, but will still respond to bug reports and security concerns. We welcome PRs, but any that include new features should be small and easy to integrate and should not include breaking changes. We otherwise intend to keep this tested up to the most recent version of WordPress.
A complete listing of all notable changes to Convert to Blocks are documented in CHANGELOG.md.
Please read CODE_OF_CONDUCT.md for details on our code of conduct, CONTRIBUTING.md for details on the process for submitting pull requests to us, and CREDITS.md for a listing of maintainers of, contributors to, and libraries used by Convert to Blocks.
