FSE: Fix template resolution to give precedence to child theme PHP templates over parent theme block templates with equal specificity #37074
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Back-backport of WordPress/wordpress-develop#1985. See there for more background and details.
Merge only once WordPress/wordpress-develop#1985 has been approved and committed!
How has this been tested?
Ideally, have a parent theme with a block template of a certain specificity (e.g.
page-home.html
), and a child theme with a PHP template for the same specificity (e.g.page-home.php
). Then, verify that Gutenberg gives precedence to the PHP theme (e.g. when rendering a page that matches that specificity).Types of changes
Bug fix.