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.