Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Support for WordPress 5.0 and the new editor - Gutenberg #97
Since early 2017 a new editor has been under development. Code named Gutenberg this new editor is being developed as a feature plugin. It is expected to be merged into core for WordPress 5.0.
We need to be aware of Gutenberg and to attempt to be compatible with it.
According to Gutenberg's README.
That's not the case right now.
This particular issue may act as the central repository of all our known issues associated with Gutenberg. We will need to create issues in each plugin that is affected by the changes associated with WordPress 5.0 and Gutenberg.
Some extension plugins may benefit from providing full support for the new editor. For example oik-fields may implement the Fields meta-box differently.
There will also be cases where Gutenberg appears to break a site.
referenced this issue
Jan 14, 2018
In a couple of environments I noticed messages in the Chrome console.
I discovered this was associated with issue 3215, which occurs when the site is configured with plain permalinks. The problem is due to there being two question marks in the request.
I raised an improvement request that the plugin should detect when the site uses Plain permalinks and produces a warning. See WordPress/gutenberg#4617
I also added a comment to WordPress/gutenberg#3010 (comment)
I believe the problem I saw with hyphens being stripped from HTML comments in the output from [bw_wtf]. But it could have been due to my accidentally hitting the Insert More Tag in the Classic block.
Earlier today I detected a problem when editing an oik-shortcode which had