Skip to content
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

New createBlockEditFilter removed the core/editor/custom-class-name/with-inspector-control and causes issues with plugin #61689

Open
coreyworrell opened this issue May 15, 2024 · 2 comments
Labels
[Type] Bug An existing feature does not function as intended [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes.

Comments

@coreyworrell
Copy link
Contributor

coreyworrell commented May 15, 2024

Description

In older version of Gutenberg we could replace the "Additional CSS Class(es)" field with our own (with autocomplete for example) by simply using something like:

removeFilter(
    'editor.BlockEdit',
    'core/editor/custom-class-name/with-inspector-control',
)

addFilter(
    'editor.BlockEdit',
    'site/custom-class-name/withInspectorControls',
    withInspectorControls,
)

Now core does not add the core/editor/custom-class-name/with-inspector-control filter, so the removeFilter code above does not remove the custom class name field, so we end up with a duplicate field. This seems to be the commit that changes it: a9cbc06

This affects our Block Class Autocomplete plugin (source) and the more popular EditorsKit plugin (source).

Step-by-step reproduction instructions

  1. Install either plugin referenced above
  2. Edit page
  3. Select a block
  4. Open Advanced Inspector panel
  5. See duplicate Custom CSS Class(es) field

Screenshots, screen recording, code snippet

image

Environment info

  • WordPress 6.5.2 (bundled Gutenberg version)

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

@coreyworrell coreyworrell added the [Type] Bug An existing feature does not function as intended label May 15, 2024
@Mamaduka Mamaduka added the [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes. label May 15, 2024
@Mamaduka
Copy link
Member

cc @ellatrix

@mkkeck
Copy link

mkkeck commented May 18, 2024

How can we get a working alternative of the removed hook
core/editor/custom-class-name/with-inspector-control?
Or how can we replace / hook into any control of Inspektor Control?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Bug An existing feature does not function as intended [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes.
Projects
None yet
Development

No branches or pull requests

3 participants