PublishPress Blocks adds the missing blocks and configuration you need to build professional websites. Take the control of the new Gutenberg editor with user edition profile configuration and 20+ new blocks and options.
15
stars
8
forks
source link
Blocks using metadata.name on their registration trigger error on PublishPress-Blocks #1366
If a block is created using npx @wordpress/create-block or manually using the metadata.name registration, PublishPress-Blocks throws an error on the console, doesn't display the block for permission management, making the custom block unavailable.
If PublishPress-Blocks plugin is not enabled, the custom block created is available on the editor screen and no errors are thrown on the console.
If metadata registration is used instead of metadata.name, PublishPress-Block doesn't throw an error and the block displays on the permision list.
Review the index.js and make sure the registerBlockType is using metadata.name or the block name directly.
Open PublishPress-Blocks Block Permissions on the WP site.
Open the console and check for errors. The error "The block {namespace/block-name} must have a title." appears on the console and the block doesn't appear on the list to be enabled or disabled.
Context
This issue blocks administrators from managing certain blocks depending on their registration method.
Your Environment
Multisite using WPVIP enterprise host.
Version used: PHP 8.1 and WordPress 6.3.3 or WordPress 6.4.3
Browser Name and version: Chrome
Operating System and version (desktop or mobile): MacOS
Expected Behavior
PublishPress-Blocks plugin should display blocks independently of their registration method as long as the registration method is available on the WordPress documentation for the used WordPress version. Docs reference: https://developer.wordpress.org/block-editor/reference-guides/block-api/block-metadata/
Current Behavior
npx @wordpress/create-blockor manually using themetadata.nameregistration, PublishPress-Blocks throws an error on the console, doesn't display the block for permission management, making the custom block unavailable.metadataregistration is used instead ofmetadata.name, PublishPress-Block doesn't throw an error and the block displays on the permision list.Steps to Reproduce (for bugs)
npx @wordpress/create-blockhttps://developer.wordpress.org/block-editor/reference-guides/packages/packages-create-block/Context
This issue blocks administrators from managing certain blocks depending on their registration method.
Your Environment
Multisite using WPVIP enterprise host.