Update block-patterns.md

[emmahughescodes]

In the new WordPress 5.6, it is required to have a 'categories' property in the register_block_pattern function.

Description

How has this been tested?

Screenshots

Types of changes

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR.

[gziolo]

@youknowriad, can you review this changes proposed? I couldn't find the place in the code where categories for block patterns would be enforced.

[youknowriad]

I think we should investigate where categories became required. If it wasn't the case in previous versions, this might be a bug we need to fix.

[skorasaurus]

Thanks again for the Pull Request!

The value(s) inside the categories array needs to be an existing block pattern category.

Although 'my-plugin' could be its own block category, a custom block pattern needs to be registered first and for the sake of simplicity for this documentation; we should use one of the default categories, which would be buttons.

And then wrap it in a translation function, because buttons can mean some different context, so it would look like:

'categories' => array( _x( 'buttons', 'Block pattern category', 'my-plugin' )),

[skorasaurus]

I think we should investigate where categories became required. If it wasn't the case in previous versions, this might be a bug we need to fix.

The block editor would crash if the categories was not included - #27249;

From testing, requiring the categories value was introduced sometime between 9.0.0 and 9.1.0 .

[skorasaurus]

Hi @emmahughescodes

Thank you for reporting this! This was a bug in Gutenberg (categories are not required for a block pattern) and has been fixed in #27970 and will be added to WordPress 5.7 so the documentation does not need to be updated.