-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for WordPress 5.0 and the new editor #30
Comments
There's a third area. Fields which already produce unexpected messages when the content is displayed as part of the [bw_field] or [bw_fields] shortcode. |
There's a third area. Fields which already produce unexpected messages when the content is displayed as part of the [bw_field] or [bw_fields] shortcode. Problems detected are
Media field produces |
WordPress 5.0 was released on 6th December 2018. The latest version of oik-fields does co-exist peacefully with WordPress 5.0 and Gutenberg 4.8. There are some instances where updates to post meta fields, performed server side, are not reflected in the Block editor display. You need to reload the editor to see the changes. |
As part of the fix for bobbingwide/oik#120 I prototyped a change to the It's not caused any problems that I'm aware of so I'm happy to commit it... with oik-fields dependent upon oik v3.3.0 |
Since early 2017 a new Block 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.
Over time, more content will be created using the Block editor than the Classic editor.
The new solution needs to be backward compatible with our existing solution, so there shouldn’t be a need to change anything and it should still work. But that has not yet proven to be the case.
Also, over time, more content will be created/edited using the Block editor than the Classic editor.
We need to embrace the improvements.
So, rather than being compatible with Gutenberg we need to be Gutenberg aware.
For oik-fields there are two areas.
show_in_rest
Non functional requirements
The text was updated successfully, but these errors were encountered: