Pattern resolver: run filters

[ellatrix]

What?

Render the pattern block through the render_block API, which will call the necessary filters.

Why?

Fixes #61454.

How?

Testing Instructions

Testing Instructions for Keyboard

Screenshots or screencast

[github-actions]

This pull request has changed or added PHP files. Please confirm whether these changes need to be synced to WordPress Core, and therefore featured in the next release of WordPress.

If so, it is recommended to create a new Trac ticket and submit a pull request to the WordPress Core Github repository soon after this pull request is merged.

If you're unsure, you can always ask for help in the #core-editor channel in WordPress Slack.

Thank you! ❤️

View changed files

❔ lib/compat/wordpress-6.6/resolve-patterns.php

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: ellatrix <[email protected]>
Co-authored-by: joemcgill <[email protected]>
Co-authored-by: westonruter <[email protected]>
Co-authored-by: justintadlock <[email protected]>
Co-authored-by: ryelle <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[ellatrix]

Ok, this will break because we now rely on the pattern block's server side render function, which is really a front-end render function, because it in turn calls do_blocks and strips paragraphs from its comment delimiters.

[ellatrix]

We also can't really run the render_block filters because we're not rendering blocks, we're just fetching them and resolving them, and they might be displayed in the editor (in which case these front-end filters shouldn't be running).