ISSUE: Why is the Classic Editor plugin required with Boutiques?

We're often asked why our Boutiques plugin requires the Classic Editor plugin, when this feels out of sync and even regressive with WordPress' new block editor environment. There's a simple answer for this: it's because it's not yet possible to register custom block templates on static pages in the WordPress block editor system! 

How it works

The Boutiques plugin adds new page templates allowing you to simply fill out your options in a page editor, with the plugin handling the rest. While the new Gutenberg block editor introduced in WordPress v5.0+ came with the ability for developers to create block templates, these templates do not yet work with specific page templates. This is a feature that WordPress will (hopefully!) roll out to developers in future releases of the platform.

In order to make the Boutiques plugin compatible with the WordPress Gutenberg block editor, it would have required our customers to lay out the Boutiques page themselves with custom blocks we created. Definitely not user-friendly, and far more time consuming for you!

We're keeping an eye on it!

So for now, we’ve opted to require the Classic Editor plugin, giving our customers a more user-friendly experience. As WordPress and the new block editor environment evolve, we are committed to updating this plugin with block editor compatibility. In the future, this will provide a similar experience as the existing page editor, within the new WordPress interface. While this feature does appear to be planned for future WordPress updates, no date has been announced at this time. We will continue to monitor WordPress for updates to make this plugin compatible with the block editor system.


In the meantime, if you have installed the Classic Editor plugin but wish to use Block Editor everywhere else, please read this Help Desk article on how to set a default editor view, as well as turn on the ability to toggle between both Classic and Block Editor modes.