mirror of
https://github.com/gosticks/wordpress-develop.git
synced 2025-10-16 12:05:38 +00:00
Themes: Allow remote pattern registration in theme.json when core patterns are disabled.
In 6.0 there is now a functionality that allows to register selected remote patterns (from the Pattern Directory) via `theme.json`. However, it requires to fully enable all core and remote patterns. This can be a blocker for user adoption. Many theme authors want to have all core and remote patterns disabled by default using `remove_theme_support( 'core-block-patterns' )`. This changeset ensures they are serving only patterns relevant to their theme. This changeset removes theme support check from the function that registers remote patterns specified in `theme.json`. This allows theme authors to disable core patterns but then selectively register the ones they want from the Pattern Directory. If a theme author intentionally specifies patterns in `theme.json`, they probably intend for them to be present in the pattern inserter and the check is not required. This change will make the Pattern Directory more appealing/usable from the theme author's perspective. Props ndiego, ryelle. Fixes #56112. git-svn-id: https://develop.svn.wordpress.org/trunk@53793 602fd350-edb4-49c9-b593-d223f7449a82
This commit is contained in:
parent
00a2b65eee
commit
6d5d482c72
@ -133,10 +133,6 @@ function _load_remote_featured_patterns() {
|
||||
* @access private
|
||||
*/
|
||||
function _register_remote_theme_patterns() {
|
||||
if ( ! get_theme_support( 'core-block-patterns' ) ) {
|
||||
return;
|
||||
}
|
||||
|
||||
/** This filter is documented in wp-includes/block-patterns.php */
|
||||
if ( ! apply_filters( 'should_load_remote_block_patterns', true ) ) {
|
||||
return;
|
||||
|
||||
Loading…
Reference in New Issue
Block a user