Plugin: Backport PHP changes for WordPress 6.1 release

[ockham]

Description

Related Trac ticket 56467.

This is the tracking issue to coordinate the process of backporting all PHP changes added in the Gutenberg plugin that needs to be backported for the WordPress 6.1 release.

Files listed for WP 6.1

lib/block-supports

• border.php Backporting block supports [border, color, elements, spacing] from Gutenberg to WP 6.1 wordpress-develop#3204 🟢
• colors.php Backporting block supports [border, color, elements, spacing] from Gutenberg to WP 6.1 wordpress-develop#3204 🟢
• dimensions.php No changes since WP 6.0.
• duotone.php Backport duotone block supports for WP 6.1 wordpress-develop#3210 🟢
• elements.php Backporting block supports [border, color, elements, spacing] from Gutenberg to WP 6.1 wordpress-develop#3204 🟢
• layout.php @andrewserong (ref). Blocked by safecss_filter_attr: Add exceptions for min(), max(), etc. functions wordpress-develop#3212 and Add layout-related CSS properties to safe_style_css_filter in kses.php wordpress-develop#2928. Style engine: migrate functions, classes and tests wordpress-develop#3199 Backport Layout block support refactor part 2 wordpress-develop#3254 🟢
• spacing.php Backporting block supports [border, color, elements, spacing] from Gutenberg to WP 6.1 wordpress-develop#3204 🟢
• typography.php Backport typography block supports for WP 6.1 wordpress-develop#3203 🟢
• utils.php No changes since WP 6.0.

lib/compat/wordpress-6.1

• block-editor-settings.php - Layout: #42906 Spacing: #42173 🟢
• block-patterns.php - 🔴 Patterns registered in this file are not in Core.
• block-template-utils.php Site editor: #3214 🟢
• blocks.php 🔴 It seems that the multiple viewScripts feature has not been backported.
• class-gutenberg-rest-block-patterns-controller.php No changes since WP 6.0.
• class-gutenberg-rest-templates-controller.php No changes since WP 6.0.
• class-wp-theme-json-6-1.php Elements API updates backport wordpress-develop#3206 Backport foundation for Layout block support refactor (part 1) wordpress-develop#3205 Backport spacing presets  wordpress-develop#3255 🟢
• class-wp-theme-json-resolver-6-1.php Backport spacing presets  wordpress-develop#3255 ⚠️ Core has more 6.1 functions than the Gutenberg file.
• date-settings.php Code is already in Core 🟢
• edit-form-blocks.php Preload settings and templates permissions for post editor wordpress-develop#3156 @Mamaduka 🟢
• get-global-styles-and-settings.php 🟢
• persisted-preferences.php Backport block editor persisted preferences wordpress-develop#3219 🟢
• rest-api.php 🟢
• script-loader.php Style engine changes in WordPress/wordpress-develop#3218 🟢
• theme-i18n.json 🔴
• theme.json Backport foundation for Layout block support refactor (part 1) wordpress-develop#3205 🟢
• theme.php @andrewserong Should be covered by layout related work. Only affected by Layout: Add a disable-layout-styles theme supports flag to opt out of all layout styles #42544. 🟢
• wp-theme-get-post-templates.php (No need to backport, see Plugin: Backport PHP changes for WordPress 6.1 release #43440 (comment).)

lib/experimental

• block-editor-settings-mobile.php No need to backport: Only used for mobile editor. @geriux confirmed that the endpoint is only available from the GB plugin for now.
• blocks.php Deleted.
• class-wp-rest-block-editor-settings-controller.php
• class-wp-rest-customizer-nonces.php
• class-wp-theme-json-gutenberg.php No need to backport -- "alias" wrapper around WP_Theme_JSON_6_1.
• class-wp-theme-json-resolver-gutenberg.php
• [ ] class-wp-webfonts-provider-local.php 🔴 Webfonts API is still in development and not ready for WP 6.1.
• [ ] class-wp-webfonts-provider.php 🔴 Webfonts API is still in development and not ready for WP 6.1.
• [ ] class-wp-webfonts.php 🔴 Webfonts API is still in development and not ready for WP 6.1.
• editor-settings.php
• navigation-page.php
• navigation-theme-opt-in.php
• [ ] register-webfonts-from-theme-json.php 🔴 Webfonts API is still in development and not ready for WP 6.1.
• rest-api.php
• [ ] webfonts.php 🔴 Webfonts API is still in development and not ready for WP 6.1.

Legend:

🟢 – confirmed for WP 6.1
🟡 – needs decision
🔴 – moved to future WP release

Getting Involved

If you are interested in helping with the effort, can you comment (or edit the issue's description) with your name next to the file if you plan to help with backporting. It would also help to link to Track issues / GitHub PRs in WordPress core when they are available.

Action items when working on backports:

• Update the files to follow best practices. Mostly rename functions/classes to use wp_ prefix instead of gutenberg_ and guard with declaration checks for code that needs to be backported to WordPress core.
• Identify files and functionality that need to be backported to WordPress core.
• Ensure all files, classes, methods, properties, and functions have @since 6.1.0 documentation tag included.
• Ensure all functionality backported to WordPress core has unit tests written.

Note that @hellofromtonya has started work to smoothen the backporting process, by adjusting Gutenberg's test and lint structure to more closely resemble Core's (to avoid having to fix code in backport PRs when they don't pass wordpress-develop's tests even though they did pass Gutenberg's): #43333

---

Issue modeled after #39889.

[Mamaduka]

I'll create a patch for changes in edit-form-blocks.php file.

The gutenberg_add_site_icon_url_to_index feature backport from rest-api.php depends if we merge #43514 or not.

@ntsekouras, correct me if I'm wrong, but the wp-theme-get-post-templates.php doesn't need to be ported into the core.

[Aljullu]

Heads-up that I opened a PR in wordpress-develop: WordPress/wordpress-develop#3131 which implements the same fix as #43597 in block-template-utils.php.

Related track issue: https://core.trac.wordpress.org/ticket/55881#ticket

[ntsekouras]

@ntsekouras, correct me if I'm wrong, but the wp-theme-get-post-templates.php doesn't need to be ported into the core.

Good catch @Mamaduka ! It seems so.

[ockham]

Apologies for the mass ping -- I'd like to get the backports work off the ground 😊

tl;dr: If you've added PHP code to Gutenberg's lib/ directory since the WP 6.0 release, it will need backporting to wordpress-develop in order to be included in WP 6.1. Backporting is typically easiest for the people who originally implemented the relevant feature. Please refer to the list in the issue description and leave a comment if you're willing to backport code. If you're unfamiliar with the process of backporting, don't hesitate to ping me (@ockham) or @michalczaplinski -- we're happy to help!

PRs that are strickenthrough are already merged in WordPress Core

lib/block-supports/

• border.php

  • Style engine: rename global function #42719
  • Style engine: rename main public function to reflect functionality #42140
  • Style engine: rename 'css_var' option property to 'convert_vars_to_classnames' #42113
  • Theme.json: Add spacing size presets #41527
  • Style Engine: add border to backend #40531
  • Borders: Use new border control components in block support #37770
    @ramonjd @glendaviesnz @aaronrobertshaw

• colors.php

  • Style engine: rename global function #42719
  • Style engine: rename main public function to reflect functionality #42140
  • Style engine: rename 'css_var' option property to 'convert_vars_to_classnames' #42113
  • Style Engine: add typography and color to backend  #40332
    @ramonjd

• dimensions.php

• duotone.php

  • Remove: Unrequired regex search on duotone supports. #42020
  • Add ability to unset duotone in themes with default duotone set #39564
    @jorgefilipecosta @ajlende

• elements.php

  • Style engine: remove enqueue flag #43103
  • Style engine: add optimize flag and combine functions into wp_style_engine_get_stylesheet  #42878
  • Style engine: enqueue block support styles #42452
  • Style engine: rename global function #42719
  • Style engine: rename main public function to reflect functionality #42140
  • Style engine: rename 'css_var' option property to 'convert_vars_to_classnames' #42113
  • Style engine: elements backend support #40987
  • Element styles: prevent the WordPress filter callback from being executed #40594
  • Elements: Add styles to the footer before the block is rendered #37728
    @ramonjd @oandregal @scruffian

• layout.php

  • Style engine: remove enqueue flag #43103
  • Layout: merge CSS rule for block gap #43052
  • Combine style-engine stores for block-supports #42970
  • Layout: fix flex direction column #42939
  • Style engine: add optimize flag and combine functions into wp_style_engine_get_stylesheet  #42878
  • Style engine: enqueue block support styles #42452
  • Layout: Add a disable-layout-styles theme supports flag to opt out of all layout styles #42544
  • Style engine: rename global function #42719
  • Core CSS support for root padding and alignfull blocks #42085
  • Layout: Use semantic classnames, centralize layout definitions, reduce duplication, and fix blockGap in theme.json #40875
  • Update the minimum WP version to 5.9 #41306
  • Layout: Move generation of util classes to existing method to avoid adding global public method WP #41885
  • Add utility classnames back to blocks that have layout attributes specified #41487
  • Layout: Add default fallback gap value in block.json, and set to 2em for Columns blocks #41098
  • Layout: Remove double output of align-items in horizontal layouts #41018
    @ramonjd @aristath @matiasbenedetto @andrewserong @tellthemachines @youknowriad @glendaviesnz

• spacing.php

  • Style engine: rename global function #42719
  • Style engine: rename main public function to reflect functionality #42140
  • Style engine: rename 'css_var' option property to 'convert_vars_to_classnames' #42113
  • Theme.json: Add spacing size presets #41527
  • Style Engine: add typography and color to backend  #40332
    @ramonjd @glendaviesnz

• typography.php

  • Typography: add explicit bypass for fluid font size calculation #42757
  • Style engine: rename global function #42719
  • Fluid typography: migrate fluid typography algorithm to JS for site editor #42688
  • Block supports: add fluid typography #39529
  • Style engine: rename main public function to reflect functionality #42140
  • Style engine: rename 'css_var' option property to 'convert_vars_to_classnames' #42113
  • Style Engine: add typography and color to backend  #40332
    @ramonjd

• utils.php

lib/compat/wordpress-6.1/

• block-editor-settings.php
  • Spacing presets: add editor UI support #42173
  • Layout: Ensure defaultEditorStyles are still output in Classic themes #42906
  • Remove old WordPress 5.8 code #42818
  • Layout: Add a disable-layout-styles theme supports flag to opt out of all layout styles #42544
  • Layout: Use semantic classnames, centralize layout definitions, reduce duplication, and fix blockGap in theme.json #40875
  • Theme.json: Add spacing size presets #41527
  • Send registered patterns in HTML and combine them with REST ones #40818
  • Do not render global styles coming from the server in the site editor #40185
    @glendaviesnz @andrewserong @Soean @jsnajdr @oandregal
• block-patterns.php
  • Add: Ability to use creation patterns for other post types besides page #41791
    @jorgefilipecosta
• block-template-utils.php
  • [Site Editor]: Add fallback template content on creation #42520
  • Fix typo in default category template's description #42586
  • [FSE - Templates]: Add info to templates created from wp suggestion #41387
  • [Site Editor]: Update single default template copy #41302
    @ntsekouras
• blocks.php
  • Style Engine: Include 6.1 CSS filter, ensure style engine can output CSS functions like clamp #43004
  • Layout: Use semantic classnames, centralize layout definitions, reduce duplication, and fix blockGap in theme.json #40875
  • Allow using a custom domainpath for viewscripts #40136
  • Plugin: Post WordPress 6.0 Beta 1 cleanup #40349
    @andrewserong @aristath @gziolo
• class-gutenberg-rest-block-patterns-controller.php
  • Add: Ability to use creation patterns for other post types besides page #41791
  • Backport #2576 to Gutenberg #40902
  • Patterns API: Add 'inserter' to the schema #40416
  • Add edit context to patterns REST controllers #40259
  • Plugin: Fix REST API class redeclaration #40265
  • Block patterns REST endpoint: use snake case for field names #40254
  • Update patterns REST controllers namespace to stable #40252 (This is a "back-backport" from Core.)
    @jorgefilipecosta @anton-vlasenko @Mamaduka @ntsekouras @gziolo @jsnajdr
• class-gutenberg-rest-templates-controller.php
  • [Site Editor]: Add fallback template content on creation #42520
  • [Site Editor]: Expand the template types that can be added - single custom post type and specific posts templates #41189
  • [FSE - Templates]: Add info to templates created from wp suggestion #41387
    @ntsekouras
• class-wp-theme-json-6-1.php
  • Theme_JSON: Use existing append_to_selector for pseudo elements #43167
  • Spacing presets: Add check for 0 spacing steps #43105
  • Pseudo elements supports on button elements #43088
  • Spacing presets: Prevent % spacing size units being stripped by sanitize_title #43101
  • Theme JSON: Add a static $blocks_metadata data definition to the Gutenberg instance of WP_Theme_JSON #42776
  • Layout: Add a disable-layout-styles theme supports flag to opt out of all layout styles #42544
  • Layout: Reduce specificity of fallback blockGap styles #42665
  • Link elements: Add a :where selector to the :not to lower specificity #42669
  • Block supports: add fluid typography #39529
  • Core CSS support for root padding and alignfull blocks #42085
  • Theme.json: Add block support feature level selectors for blocks #42087
  • Layout: Use semantic classnames, centralize layout definitions, reduce duplication, and fix blockGap in theme.json #40875
  • Global Styles: Add support for heading elements #41981
  • Add visited to link element allowed pseudo selector list #42096
  • Fix link element hover bleeding into button element default styles #42072
  • Theme.json: Add spacing size presets #41527
  • Global Styles: Add support for caption elements #41140
  • Global Styles: Allow references to values in other locations in the tree #41696
  • Support pseudo selectors on elements in theme json #41786
  • Elements: Button - Fix element selectors #41822
  • Elements: Add an API make it easier to get class names #41753
  • Duotone: Fix CSS Selectors rendered by theme.json duotone/filter settings for blocks on public pages #41335
  • Global Styles: Button Element: update button element selector #41240
  • get_style_nodes should be compatible with parent method. #41217
  • Add support for button elements to theme.json #40260
  • Global Styles: Load block CSS conditionally #41160
  • Theme Json: Don't output double selectors for elements inside blocks #40889
    @Mamaduka @glendaviesnz @MaggieCabrera @scruffian @andrewserong @ramonjd @tellthemachines @aaronrobertshaw @getdave @matiasbenedetto @torounit
• class-wp-theme-json-resolver-6-1.php
  • Update the minimum WP version to 5.9 #41306
  • Theme.json: Add spacing size presets #41527
  • Elements: Button - Fix element selectors #41822
    @youknowriad @glendaviesnz @scruffian
• date-settings.php
  • Make date picker respect site's 'Week Starts On' setting #41648
    @noisysocks
• edit-form-blocks.php
  • Post Editor: Avoid 403 errors for users with low permissions #42413
  • Post Editor: Preload templates post type permissions #42209
    @Mamaduka
• get-global-styles-and-settings.php
  • Layout: Use semantic classnames, centralize layout definitions, reduce duplication, and fix blockGap in theme.json #40875
  • Global Styles: Always load block CSS from __experimentalStyle #42005
  • Block styles: Account for style block nodes that have no name #41446
  • Global Styles: Load block CSS conditionally #41160
    @andrewserong @scruffian @glendaviesnz
• persisted-preferences.php
  • Preferences persistence - mark modified property as not readonly in schema #40637
  • Add new preferences persistence API, and save editor preferences in user meta #39795
    @talldan
• rest-api.php
  • REST API: Add the missing 'site_icon_url' to the index #42957
  • Add: Ability to use creation patterns for other post types besides page #41791
  • [Site Editor]: Expand the template types that can be added - single custom post type and specific posts templates #41189
  • [FSE - Templates]: Add info to templates created from wp suggestion #41387
    @Mamaduka @jorgefilipecosta @ntsekouras
• script-loader.php
  • Style engine: enqueue block supports styles in Gutenberg #42880
  • Global styles: specify priority in remove_action #43073
  • Global styles: filter block level styles before compiling global stylesheet #42207
  • Global Styles: Always load block CSS from __experimentalStyle #42005
  • Gallery block: update the gallery gap to load styles in header for block themes #41015
  • Global Styles: Load block CSS conditionally #41160
    @ramonjd @scruffian @glendaviesnz
• theme-i18n.json
  • Theme.json: Add spacing size presets #41527
  • Tools: Improve configuration for formatting files #40994
    @glendaviesnz @gziolo
• theme.json
  • Spacing presets: add editor UI support #42173
  • Remove core/post-comments-form block styles that are overriding button element styles #42053
  • Core CSS support for root padding and alignfull blocks #42085
  • Layout: Use semantic classnames, centralize layout definitions, reduce duplication, and fix blockGap in theme.json #40875
  • Button Elements: Allow element styles in classic themes #42012
  • Theme.json: Add spacing size presets #41527
  • Global Styles: Add block CSS rules after the Global Styles rules #41934
  • Support pseudo selectors on elements in theme json #41786
  • Elements: Button - Fix element selectors #41822
    @glendaviesnz @matiasbenedetto @tellthemachines @andrewserong @scruffian @getdave
• theme.php
  • Layout: Add a disable-layout-styles theme supports flag to opt out of all layout styles #42544
    @andrewserong

lib/experimental/

• block-editor-settings-mobile.php

  • List v2: add __experimentalEnableListBlockV2 flag for mobile #42697
  • Quote: use nested blocks #25892
    @ellatrix @oandregal

• blocks.php

  • List v2: add __experimentalEnableListBlockV2 flag for mobile #42697
  • Quote: use nested blocks #25892
    @ellatrix @oandregal

• class-wp-rest-block-editor-settings-controller.php

  • Spacing presets: add editor UI support #42173
  • Layout: Add a disable-layout-styles theme supports flag to opt out of all layout styles #42544
  • List v2: add __experimentalEnableListBlockV2 flag for mobile #42697
  • Theme.json: Add spacing size presets #41527
    @glendaviesnz @andrewserong @ellatrix

• class-wp-rest-customizer-nonces.php

• class-wp-theme-json-gutenberg.php

  • Theme JSON: Add a static $blocks_metadata data definition to the Gutenberg instance of WP_Theme_JSON #42776
  • Theme Json: Don't output double selectors for elements inside blocks #40889
    @scruffian

• class-wp-theme-json-resolver-gutenberg.php

  • Theme JSON Resolver: Update cache check to also check that the object is an instance of the Gutenberg version #42756
  • Enable appearance tools via theme_support #43337

---

List modeled after #39889 (comment). Created using the script from #43360.

[glendaviesnz]

I can take care of all the spacing size preset related changes.

[Mamaduka]

@ockham, @michalczaplinski, do we have a core tracking ticket to reference in Core PRs?

[ockham]

@ockham, @michalczaplinski, do we have a core tracking ticket to reference in Core PRs?

@Mamaduka Ah, we didn't -- my apologies! I've filed one now: https://core.trac.wordpress.org/ticket/56467

[andrewserong]

I'm happy to help out with Layout backports. I'm travelling at the moment but can start looking at some of them next week when I'm back. Some of them might have a couple of challenges — layout.php currently depends on the style engine work in the style engine package (so just CCing @ramonjd there), which might need to land first?

Also, I was wondering how we deal with PHP changes that require JS changes to be shipped at the same time? I think some of the Layout work might need to happen all at once 🤔. There's definitely pieces that can be done in separate PRs first, though, so I'll give it a bit more thought to see what sort of order might work.

Just linking a couple of other pre-requisites for Layout in Gutenberg being merged to core:

• Trac ticket 55966, which adds in support for additional CSS functions to safecss_filter_attr (like clamp)
• Core PR (Add layout-related CSS properties to safe_style_css_filter in kses.php wordpress-develop#2928) to add in layout related CSS properties to safe_style_css_filter

I believe the above two tickets/PRs will need to land prior to the layout.php changes being backported.

[Mamaduka]

@ockham,

My backport PRs are ready:

• Preload settings and templates permissions for post editor wordpress-develop#3156
• REST API: Add the missing 'site_icon_url' to the index wordpress-develop#3157

The #40416 should already be in Core, cherry-picked for a minor release - WordPress/wordpress-develop#2600.

I've only done a minor code quality work for class-wp-theme-json-6-1.php, but happy to help as needed.

[ockham]

Small update: In WordPress/wordpress-develop#3154, I'm attempting a package sync to update Core to the latest package versions -- mostly as a dry-run for Beta 1. (I would like to actually merge it once its ready -- see its PR desc for context).

In order to unblock that PR, I've filed a small backport PR to add the $priority param to wp_enqueue_block_support_styles.

[gziolo]

In order to unblock that PR, I've filed a small backport PR to add the $priority param to wp_enqueue_block_support_styles.

In addition to that, we need to refactor all occurrences of WP_Theme_JSON_Gutenberg and gutenberg_enqueue_block_support_styles in core blocks in the Gutenberg plugin. That might not be trivial as the plugin still supports WordPress 6.0 and 6.1 where some functionality is missing.

[ockham]

In order to unblock that PR, I've filed a small backport PR to add the $priority param to wp_enqueue_block_support_styles.

In addition to that, we need to refactor all occurrences of WP_Theme_JSON_Gutenberg and gutenberg_enqueue_block_support_styles in core blocks in the Gutenberg plugin. That might not be trivial as the plugin still supports WordPress 6.0 and 6.1 where some functionality is missing.

Good point. Here's one approach for gutenberg_enqueue_block_support_styles: #43779.

[noisysocks]

Thanks for the nice list—that's a cool script! I've backported #41648 (in r54079) and checked it off the list in the description.

[ramonjd]

I'm working on prepping packages/style-engine for inclusion in core.

WIP here: WordPress/wordpress-develop#3199

This will unblock most of the lib/block-supports migrations given that they're using style engine methods.

It requires https://core.trac.wordpress.org/ticket/55966, otherwise I'll need to migrate gutenberg_safecss_filter_attr_allow_css_6_1 to core to make the Style Engine work. 😱

[ockham]

It requires https://core.trac.wordpress.org/ticket/55966, otherwise I'll need to migrate gutenberg_safecss_filter_attr_allow_css_6_1 to core to make the Style Engine work. 😱

I've asked in #core for someone to merge 55966's patch 🙂

[ockham]

As the Feature Freeze is only two weeks away, I'll start pinging some folks who I know have good domain knowledge of certain areas and can help backporting some files 😊

@ntsekouras -- Could you file a backport PR for the changes you made to block-template-utils.php and class-gutenberg-rest-templates-controller.php? 🙏

[ockham]

As the Feature Freeze is only two weeks away, I'll start pinging some folks who I know have good domain knowledge of certain areas and can help backporting some files 😊

@jorgefilipecosta -- Could you maybe file a backport PR for #41791 (affecting block-patterns.php, class-gutenberg-rest-block-patterns-controller.php, and rest-api.php)? 🙏

[jorgefilipecosta]

As the Feature Freeze is only two weeks away, I'll start pinging some folks who I know have good domain knowledge of certain areas and can help backporting some files 😊

@jorgefilipecosta -- Could you maybe file a backport PR for #41791 (affecting block-patterns.php, class-gutenberg-rest-block-patterns-controller.php, and rest-api.php)? 🙏

Sure 👍

[ockham]

As the Feature Freeze is only two weeks away, I'll start pinging some folks who I know have good domain knowledge of certain areas and can help backporting some files 😊

@oandregal -- Could you maybe file a backport PR for #25892 (Quote v2)? 🙏

[ironprogrammer]

Submitted #3237 as refresh of #3203, primarily to resolve failing PHP unit tests once style engine is in place.

[oandregal]

Prepared WordPress/wordpress-develop#3247 to backport some recent changes: #44015 #44109 and #44159

[andrewserong]

Thanks for all the help landing part 1 of the Layout refactor! Update on Layout and Spacing presets follow-up backports:

• Spacing Presets backport is ready for review from @glendaviesnz: Backport spacing presets  wordpress-develop#3255
• Spacing Presets is designed to work with the backport for border, color, elements, spacing, so ideally that one might land first: Backporting block supports [border, color, elements, spacing] from Gutenberg to WP 6.1 wordpress-develop#3204
• Layout backport part 2 is ready for review: Backport Layout block support refactor part 2 wordpress-develop#3254
• Layout part 2 depends on Backport script loader to land first: Backport script loader: enqueue stored block supports styles (refresh) wordpress-develop#3259

[oandregal]

Prepared WordPress/wordpress-develop#3261 to backport #44189 (which is approved but I'm waiting for the tests to pass and will backport to 14.1).

[andrewserong]

Just looking over the theme JSON file and saw that box-shadow support hadn't been backported yet. I've opened up a PR in WordPress/wordpress-develop#3274, which should pull in the final bits for that.

[ramonjd]

Block supports scripts loading

Added WordPress/wordpress-develop#3273 as an extension of WordPress/wordpress-develop#3259 cc @ockham

[oandregal]

I've prepared WordPress/wordpress-develop#3313 to backport the changes at #44363

[gziolo]

I have an update for the lib/compat/wordpress-6.1/blocks.php file:

• there is an open Trac ticket and PR for backporting gutenberg_block_type_metadata_render_template to WordPress core
• there is also an open PR (still in progress) to backport support for multiple view scripts to WordPress core (gutenberg_block_type_metadata_multiple_view_scripts)

I can confirm that all the changes are present in WordPress core.

• I'm not sure if we immediately need wp_enqueue_block_view_script in WordPress core, @aristath should know better why we need it, but it might depend on how we land support for multiple view scripts

We didn't include this new API in WP core in 6.1. PR that reflects that in the plugin is ready for review: #44414.

[scruffian]

I think this one is missing from some of the backports above: WordPress/wordpress-develop#3319

[hellofromtonya]

I removed all of the Webfonts API files from the backport list. Why? The API is being re-architected, ie still in development. It will not be ready for WP 6.1. 🔴

Please leave these files in the lib/experimental/ directory. Thanks.

[cbravobernal]

Now that the 6.1 release is out, I think we can close this issue.