What You Need to Know About PublishPress and Gutenberg
WordPress 5 is now available.
Version 5 brings the new Gutenberg editor to WordPress. If you’re unfamiliar with the new editor, the official launch post is a good place to start.
The Gutenberg editor is really cool and it is the future of WordPress. But, Gutenberg is a big change from the old editor and it does remove some features that WordPress users have relied on.
Version 1.18 of PublishPress is available today to provide some support for Gutenberg. However, we do not recommend that you update to Gutenberg yet, if you want to use all the features of PublishPress.
Gutenberg doesn’t support custom statuses
For PublishPress users, the big missing feature in Gutenberg is custom statuses. At least for now, WordPress has dropped support for them. That may possibly be fixed in WordPress 5.1, but there are no guarantees.
This problem impacts PublishPress, and all the other plugins and SaaS platforms that create custom workflows.
In the next couple of weeks, we hope to release a temporary workaround. In the long-term, we’d love to work with the WordPress team on a fix.
Smaller issues with Gutenberg
Gutenberg also causes some problems with metaboxes. This impacts the Content Checklist and Multiple Authors add-ons in small ways. These are similar to problems faced by the Advanced Custom Fields plugin.
Update to WordPress 5, but use the Classic Editor plugin for now.
This is probably the biggest update in the history of WordPress. Gutenberg is breaking plugins that have far more users than PublishPress.
I know a lot of WordPress professionals and hosting companies are waiting until at least January to start moving their content over to Gutenberg. By that point, we hope to have a clearer idea on whether Gutenberg will restore support for custom statuses.