You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 21, 2019. It is now read-only.
We have a plugin that adds a media button to the classic editor for inserting a shortcode, in a very similar fashion to Shortcake/Shortcode UI (in fact, Shortcake is also supported).
Considering that a user can still add a shortcode using the Gutenberg block, would not having this UI for "building" the shortcode be considered an incompatibility?
The text was updated successfully, but these errors were encountered:
Considering that a user can still add a shortcode using the Gutenberg block, would not having this UI for "building" the shortcode be considered an incompatibility?
For the purposes of our research, yes. Compatibility is defined as:
A WordPress user can perform the same functional task with Gutenberg active. For instance, if the plugin includes an "Add Media" button, it's considered Gutenberg-compatible when it has a block registered for the Gutenberg inserter. Feature-parity, essentially.
Also, for what it's worth, the missing "Add Media" button seems like a very common incompatibility and may be something we can accommodate in Gutenberg.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have a plugin that adds a media button to the classic editor for inserting a shortcode, in a very similar fashion to Shortcake/Shortcode UI (in fact, Shortcake is also supported).
Considering that a user can still add a shortcode using the Gutenberg block, would not having this UI for "building" the shortcode be considered an incompatibility?
The text was updated successfully, but these errors were encountered: