Allow remote pattern registration in theme.json when core patterns are disabled #43634
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ndiego
added
[Type] Enhancement
Mamaduka
added
the
Backport from WordPress Core
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This issue has already been fixed in Core, and will be released in 6.0.2. This PR is just to ensure parity between Core and the 6.0 compat file.
WordPress PR: WordPress/wordpress-develop#2925
Trac ticket: https://core.trac.wordpress.org/ticket/56112
Fixes: #41282
What?
Allow remote pattern registration in theme.json when core patterns are disabled in the 6.0.
Why?
Theme developers want the ability to disable core patterns yet include specific patterns from the Patterns Directory.
How?
Remove the core pattern support check.
Testing Instructions