Title: 2021 – Page 15 – Make WordPress Core --- # Yearly Archives: 2021 [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 11:09 pm _on_ September 29, 2021 Tags: [5.8.x ( 13 )](https://make.wordpress.org/core/tag/5-8-x/), [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [dev chat ( 920 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 975 )](https://make.wordpress.org/core/tag/summary/), WPTranslationDay # 󠀁[Dev chat summary – September 29, 2021](https://make.wordpress.org/core/2021/09/29/dev-chat-summary-september-29-2021/)󠁿 [@audrasjb](https://profiles.wordpress.org/audrasjb/) led the chat on this [agenda](https://make.wordpress.org/core/2021/09/29/dev-chat-agenda-for-sept-29-2021/). You can also read the [Slack logs](https://wordpress.slack.com/archives/C02RQBWTW/p1632945614174400). ## Highlighted blogblog (versus network, site) posts Bringing to your attention some interesting reads and some call for feedback and/ or volunteers: * [Core Editor Improvement: Introducing the Widget Group Block](https://make.wordpress.org/core/2021/09/22/core-editor-improvement-introducing-the-widget-group-block/) * [WordPress 5.8.2+ Release Schedule](https://make.wordpress.org/core/2021/09/23/wordpress-5-8-2-release-schedule/) * [Changes to the WordPress Core PHP Test Suite](https://make.wordpress.org/core/2021/09/27/changes-to-the-wordpress-core-php-test-suite/) * [A Week in Core – September 27, 2021](https://make.wordpress.org/core/2021/09/27/a-week-in-core-september-27-2021/) * [Implementing a Webfonts API in WordPress Core](https://make.wordpress.org/core/2021/09/28/implementing-a-webfonts-api-in-wordpress-core/) * [Editor chat summary: Wednesday, 22 September 2021](https://make.wordpress.org/core/2021/09/28/editor-chat-summary-wednesday-22-september-2021/) Worth mentioning: > **Thanks to the 23 contributors of the past week, including 4 new contributors! > Kudos to the 5 coreCore Core is the set of software required to run WordPress. > The Core Development Team builds WordPress. committers of the week, too.** > [**A Week in Core – September 27, 2021**](https://make.wordpress.org/core/2021/09/27/a-week-in-core-september-27-2021/) ## Upcoming releases updates ### Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.(s) [@desrosj](https://profiles.wordpress.org/desrosj/) and [@circlecube](https://profiles.wordpress.org/circlecube/) are still leading the 5.8.x releases. They published [a schedule for 5.8.2 and –if needed– 5.8.3](https://make.wordpress.org/core/2021/09/23/wordpress-5-8-2-release-schedule/). The 5.8.x point releases are coordinated in the [#5-8-release-leads](https://wordpress.slack.com/archives/C01VACX5E2W) SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) channel. This channel is public and will be archived once 5.9 is released. [@costdev](https://profiles.wordpress.org/costdev/) pointed out that a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a **diff**. A patch can be _applied_ to a codebase for testing. for ticketticket Created for both bug reports and feature development on the bug tracker. #53801 leads to a change in both `Core` and in the `@wordpress/widgets` package and asked for advices for how to ensure that any changes are committed at the same time to minimise issues on either end. [@audrasjb](https://profiles.wordpress.org/audrasjb/) answered that [there is already an issue](https://github.com/WordPress/gutenberg/issues/33580) for this ticket in the [5.8.2 Gutenberg project board](https://github.com/WordPress/gutenberg/milestone/159). ### Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. Concerning the next major release —**WordPress 5.9**— a [planning roundup](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/) was published a couple weeks ago. Worth noting that [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) proposed a review of the upcoming 5.9 key features [in the last issue of the WordPress.org podcast](https://wordpress.org/news/2021/09/episode-16-a-sneak-peek-at-wordpress-5-9/). [@audrasjb](https://profiles.wordpress.org/audrasjb/) ran a first bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub last week to review the tickets marked `early`. He will run another one on [Thursday September 30, 2019 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191003T2000). Reminder: **everyone is welcome to run a bug scrub** on the `#core` Slack channel. If you are interested, please read this handbook post: [Leading bug scrubs](https://make.wordpress.org/core/handbook/tutorials/leading-bug-scrubs/) and get in touch with [@audrasjb](https://profiles.wordpress.org/audrasjb/) or [@francina](https://profiles.wordpress.org/francina/) for details. Also, [@audrasjb](https://profiles.wordpress.org/audrasjb/) silently scrubbed the` Future Release` queue and moved a dozen of tickets (in various components) to 5.9, with refreshed patches when needed. Most of them are ready and waiting for review/ commit. ## Component maintainers updates ### Build/Test Tools – 󠀁[@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)󠁿 PHPUnit 9.5.10 and 8.5.21 were released with a breaking change: PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher deprecations are no longer converted to exceptions by default (`convertDeprecationsToExceptions ="true"` can be configured to enable this). See changeset [[51871]](https://core.trac.wordpress.org/changeset/51871) and ticket [#54183](https://core.trac.wordpress.org/ticket/54183) for more details. This is also included in the [Changes to the WordPress Core PHP Test Suite](https://make.wordpress.org/core/2021/09/27/changes-to-the-wordpress-core-php-test-suite/) dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase., which is highly recommended to read as it includes other important changes for pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. and theme authors using the WordPress Core test framework as a basis for their integration tests. ### Upgrade/Install – 󠀁[@afragen](https://profiles.wordpress.org/afragen/)󠁿 [@afragen](https://profiles.wordpress.org/afragen/) shared that there is currently a lot of activity on a 9 years old ticket: [#22316](https://core.trac.wordpress.org/ticket/22316). He added [a new PR](https://github.com/WordPress/wordpress-develop/pull/1724) which is ready for review. [@audrasjb](https://profiles.wordpress.org/audrasjb/) added that the design of the feature was discussed [during the last #core-auto-updates weekly meeting](https://wordpress.slack.com/archives/CULBN711P/p1632849101235500). [@joyously](https://profiles.wordpress.org/joyously/) asked if it is supposed to handle initial installation or deactivation and uninstall also? [@audrasjb](https://profiles.wordpress.org/audrasjb/) answered that it only handles initial installation, because a dependency could exists without the “base” plugin. [@joyously](https://profiles.wordpress.org/joyously/) asked what value does this enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. add to the existing implementation. [@clorith](https://profiles.wordpress.org/clorith/) answered that It surfaces which plugins would enhance (or enable) functionality, so yes it has value. [@audrasjb](https://profiles.wordpress.org/audrasjb/) added that it standardizes a process which currently has many different implementations. [@afragen](https://profiles.wordpress.org/afragen/) encouraged testers to install the PR, add a test plugin with a couple of dot org plugin slugs in a comma separated list in the `Required Plugins` headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.. Removing or changing the header name will deactivate those dependencies from being displayed. ### Toolbar – 󠀁[@sabernhardt](https://profiles.wordpress.org/sabernhardt/)󠁿 [@sabernhardt](https://profiles.wordpress.org/sabernhardt/) shared a draft of a Toolbar component update post. He also pointed out that a docs update ([#54191](https://core.trac.wordpress.org/ticket/54191)) was just committed today. ## Open Floor From [@marybaum](https://profiles.wordpress.org/marybaum/) and [@annezazu](https://profiles.wordpress.org/annezazu/): there is a new testing call in the Full Site Editing Outreach Program. > [FSE Program Testing Call #10: Pattern Party](https://make.wordpress.org/test/2021/09/29/fse-program-testing-call-10-pattern-party/) [@costdev](https://profiles.wordpress.org/costdev/) noted that the `Administration` component doesn’t have a maintainer currently listed. He asked for a review of [#53152](https://core.trac.wordpress.org/ticket/53152). [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) moved it to milestone 5.9. [@pbearne](https://profiles.wordpress.org/pbearne/) asked for a review of [#54020](https://core.trac.wordpress.org/ticket/54020). He’s available to make a simpler patch if needed. [@webcommsat](https://profiles.wordpress.org/webcommsat/) shared that tomorrow ( 30 September) is the last day of [#WPTranslationDay](https://make.wordpress.org/core/tag/wptranslationday/) 2021. Everyone is welcome to come and join the polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. [https://make.wordpress.org/polyglots/teams/](https://make.wordpress.org/polyglots/teams/) [for the final event and the celebrations from 16:00 UTC](https://wptranslationday.org/blog/join-us-for-the-global-translation-day-finale-event-on-september-30/). [#5-8-x](https://make.wordpress.org/core/tag/5-8-x/), [#5-9](https://make.wordpress.org/core/tag/5-9/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 8:42 am _on_ September 29, 2021 Tags: [5.8.2 ( 16 )](https://make.wordpress.org/core/tag/5-8-2/), [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/), [core ( 743 )](https://make.wordpress.org/core/tag/core/), [dev chat ( 920 )](https://make.wordpress.org/core/tag/dev-chat/) # 󠀁[Dev Chat Agenda for Sept 29, 2021](https://make.wordpress.org/core/2021/09/29/dev-chat-agenda-for-sept-29-2021/)󠁿 Here is the agenda for this week’s developer meeting to occur at [September 29, 2021, at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210929T2000). ## Blogblog (versus network, site) Post Highlights and announcements Bringing to your attention some interesting reads and some call for feedback and/ or volunteers: * [Core Editor Improvement: Introducing the Widget Group Block](https://make.wordpress.org/core/2021/09/22/core-editor-improvement-introducing-the-widget-group-block/) * [WordPress 5.8.2+ Release Schedule](https://make.wordpress.org/core/2021/09/23/wordpress-5-8-2-release-schedule/) * [Changes to the WordPress Core PHP Test Suite](https://make.wordpress.org/core/2021/09/27/changes-to-the-wordpress-core-php-test-suite/) * [A Week in Core – September 27, 2021](https://make.wordpress.org/core/2021/09/27/a-week-in-core-september-27-2021/) * [Implementing a Webfonts API in WordPress Core](https://make.wordpress.org/core/2021/09/28/implementing-a-webfonts-api-in-wordpress-core/) * [Editor chat summary: Wednesday, 22 September 2021](https://make.wordpress.org/core/2021/09/28/editor-chat-summary-wednesday-22-september-2021/) ## Next releases status update * Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2( five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: WP 5.8.2 👉 [WordPress 5.8.2+ Release Schedule](https://make.wordpress.org/core/2021/09/23/wordpress-5-8-2-release-schedule/) * Next major releasemajor release A release, identified by the first two numbers( 3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: WP 5.9 👉 [WordPress 5.9 Planning Roundup](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/) ## Components check-in and status updates * Check-in with each component for status updates. * Poll for components that need assistance. ## Open Floor Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above? Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly. This meeting happens in the [#core](https://wordpress.slack.com/messages/C02RQBWTW) channel. To join the meeting, you’ll need an account on the [Making WordPress Slack](https://make.wordpress.org/chat/). [#5-8-2](https://make.wordpress.org/core/tag/5-8-2/), [#5-9](https://make.wordpress.org/core/tag/5-9/), [#agenda](https://make.wordpress.org/core/tag/agenda/), [#core](https://make.wordpress.org/core/tag/core/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) [ ](https://profiles.wordpress.org/jorgefilipecosta/) [Jorge Costa](https://profiles.wordpress.org/jorgefilipecosta/) 3:49 pm _on_ September 28, 2021 Tags: [block-editor ( 139 )](https://make.wordpress.org/core/tag/block-editor/), [chats ( 25 )](https://make.wordpress.org/core/tag/chats/), [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-summary ( 185 )](https://make.wordpress.org/core/tag/core-editor-summary/), [gutenberg ( 546 )](https://make.wordpress.org/core/tag/gutenberg/), [meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/) # 󠀁[Editor chat summary: Wednesday, 22 September 2021](https://make.wordpress.org/core/2021/09/28/editor-chat-summary-wednesday-22-september-2021/)󠁿 This post summarizes the weekly _editor chat _meeting on [Wednesday, 22 September 2021, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210922T1400) held in [Slack](https://wordpress.slack.com/archives/C02QB2JS7/p1632319263165400). ## What’s next in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. 󠀁[https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)󠁿? (Mid-September 2021) [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) said the post with the [goals for the Gutenberg project in September](https://make.wordpress.org/core/2021/09/17/whats-next-in-gutenberg-mid-september-2021/) is published and referred that the priorities are the template Editor, Patterns, Global Styles theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML., the design tools., and the Navigation blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience./ navigation editor work. As a follow-up [@ntsekouras](https://profiles.wordpress.org/ntsekouras/) brought attention to an experiment to trigger some discussions –[ a Patterns explorer](https://github.com/WordPress/gutenberg/pull/35006), asking people to share their thoughts. ## Project Updates ### Mobile Application #### Shipped * Improve error handling for embed block * Improve Reusable Blocks inserter UIUI User interface #### Fixes * Fix image block height and border regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or [blockers](https://make.wordpress.org/core/2021/page/15/?output_format=md#blocker). Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. * Fix back icon color in dark mode #### In Progress * Additional Embed block improvements * GSS Font size, line height, colors ### Components package #### Shipping * Completed a migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. away from the createComponent function. This simplifies the process of adding new components to the library, using the more straightforward View component. * Following up on the recently expanded contributor guidelines, we simplified the structure of the guidelines and added a table of contents. #### In Progress * [@youknowriad](https://profiles.wordpress.org/youknowriad/) merged a PR that introduces a navigation component to the Global Styles sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme., which moves us closer to the updated designs. We’re experimenting now with a revised Navigator component that may provide greater flexibility for the design. ### Navigation Editor Lots of work happening on priority items. Thanks to everyone who is contributing so much work. • REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/) interactions have been improved and more issues identified. • Started looking at ways to add links in Bulk.• [Using Theme JSON to control the block in the editor has been ruled out](https://github.com/WordPress/gutenberg/pull/34784#issuecomment-924063034).• Another Hallway Hangout is on the cards – dates/times to be confirmed. ## Task Coordination ### 󠀁[@annezazu](https://profiles.wordpress.org/annezazu/)󠁿 [Hallway hangout for adoption pathways for FSE with Marcus & Dave](https://make.wordpress.org/test/2021/09/17/hallway-hangout-discussion-on-adoption-pathways-for-full-site-editing-16-september/), continue amplifying the [current block theme switching exploration](https://make.wordpress.org/test/2021/09/08/fse-program-exploration-help-with-the-future-of-block-theme-switching/)( please check it out!), did some light triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., and shared a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor improvement post[ on the new Widgets Group block!](https://make.wordpress.org/core/2021/09/22/core-editor-improvement-introducing-the-widget-group-block/) ### 󠀁[@ntsekouras](https://profiles.wordpress.org/ntsekouras/)󠁿 * Query Pagination with `flex` layout([#34876](https://github.com/WordPress/gutenberg/pull/34876), [#34897](https://github.com/WordPress/-%20gutenberg/pull/34897)). * Pass the search value to inserter, when clicking Browse All([#34912](https://github.com/WordPress/gutenberg/pull/34912)). * Delayed loading state of SSR component([#35033](https://github.com/WordPress/gutenberg/pull/35033)). * Pattern Explorer experiment([#35006](https://github.com/WordPress/gutenberg/pull/35006)). ### 󠀁[@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)󠁿 For the next week, the plan is to continue iterating on the design and address the remaining follow-ups we have thinks like changing the border of the input field from a gray to slightly different gray changing the dimension of inputs from 30px to 40px, changing the focus look on the range control. ### 󠀁[@mciampini](https://profiles.wordpress.org/mciampini/)󠁿 Will keep supporting [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) and other folks working on the `@wordpress/components` package, including most of the work that is being done on the new Global Styles sidebar. ## Open floor ### **Responsiveness** Roman Axelrod asked the following: > It was mentioned earlier, but… At time moment, core editor doesn’t provide options > of setting different styling rules for each device / breakpoint (Preview modes: > Desktop, Tablet, Mobile). > Right now, the rules are global. For example if I set padding: 60px to Group block > from the right sidebar of the editor, this rule is going to appear on Desktop > and Mobile.I curious if we are going to have the same functionality that all popular > page builders have? Usually they provide a list of breakpoints and ability to “ > overwrite” styling rules of previous breakpoint. It gives ability of adapting > the design by requirements.Is this something that we can expect soon? Are we going > to have something like this in 2021? [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) said he thinks that is not something on the roadmap for 5.9, but allowing to control how things look depending on the dimensions of the place where they are rendered is something that will end up existing. ### **Custom Fields** Roman Axelrod asked the following: > Are there any plans or ideas of using Custom Fields in core blocks? > For example, > imagine the situation where I have 20 pages. All pages have a “Hero” section that > contains `title`, `text`, `button` on the left and image on the right.The design > is the same but the content is different and unique for each page (kind of a template). > Now let’s say, after I built these 20 pages, we realized that the Heading block > should be 5px bigger.How should I fix that? It might be annoying to go page by > page and update the font-size of each heading.As a reference, Elementor page builder > provides this kind of option – they call it “Dynamic Content”.I thought that the > block-template-parts of FSE will solve this case. But this is still not there. > Are there any thoughts/discussions about similar cases? [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) answered the following: > Hi Roman, maybe the solution to your issue is to define a CSSCSS Cascading Style > Sheets. variable that represents the size. Theme.json provides a mechanism for > declaring the css variables, and then instead of using 5px as value you use the > css variable as the value. Changing the variable will then change the size in > every place. Roman followed up asking about how non-developers would be able to change those values. [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) said that If one wants to allow a user to change a CSS variable, one could do it by registering a custom sidebar to change the variable. Maybe one day core offers something that automatically renders a UI where users could change variables registered using theme. json, but it is not part of the road map for now. ## **Developer Hours online** [@bph](https://profiles.wordpress.org/bph/) made a big announcement during the core editor chat: > There will be a make core post with more info, this is just** a heads-up,** about > a trial initiative to hold “**Developer Hours online**” every other week, with > a group of Gutenberg developers, a short topic and then answering attendee’s Block > and Theme building questions, with screen sharing of code and follow-up post. > Depending how the trial goes, we might expand it. If you want to be part of that > initiative let me know or comment on the post. [#block-editor](https://make.wordpress.org/core/tag/block-editor/), [#chats](https://make.wordpress.org/core/tag/chats/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-summary](https://make.wordpress.org/core/tag/core-editor-summary/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#meeting-notes](https://make.wordpress.org/core/tag/meeting-notes/) [ ](https://profiles.wordpress.org/aristath/) [Ari Stathopoulos](https://profiles.wordpress.org/aristath/) 9:10 am _on_ September 28, 2021   # 󠀁[Implementing a Webfonts API in WordPress Core](https://make.wordpress.org/core/2021/09/28/implementing-a-webfonts-api-in-wordpress-core/)󠁿 PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress. org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. and theme developers have been able to enqueue scripts and styles for years, but fonts have always been more complicated to enqueue. Following ticketticket Created for both bug reports and feature development on the bug tracker. [#46370](https://core.trac.wordpress.org/ticket/46370) and last September’s [proposal to add a fonts enqueue API in WordPress Core](https://make.wordpress.org/core/2020/09/26/proposal-a-font-enqueue-api-for-wp-core/), we now have a [patch](https://github.com/WordPress/wordpress-develop/pull/1573) ready. With the recent advancements in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/), global-styles, and an effort to consolidate options and UIs in the site-editor, a Webfonts APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. is becoming a necessity as it will allow theme developers to define fonts in their `theme.json` files. In this first iteration, we are mirroring the scripts & styles enqueueing functions for consistency. Since enqueueing a webfont entails enqueuing a stylesheet (or adding inline styles) to enqueue the font files themselves, the webfonts API functions act as wrappers for the stylesheets API (with the appropriate modifications where needed). The intention for this initial iteration is to provide a basis we can build upon and improve in the future – which is why it was kept minimal. More improvements and functionality will be added in the future, but in order to improve it, it has to be there. The patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a **diff**. A patch can be _applied_ to a codebase for testing. adds the following functions: * `wp_register_webfont` * `wp_deregister_webfont` * `wp_enqueue_webfont` * `wp_dequeue_webfont` * `wp_webfont_is` * `wp_webfont_add_data` The syntax of all these functions is identical to their `style` counterparts, so` wp_register_webfont` is the same as `wp_register_style` and so on. The only difference is the use of `$params` in lieu of `$deps` for practical reasons. Notes: * The styles registered for webfonts automatically get a `webfont-` prefix to avoid conflicts with any similarly named stylesheets. This provides a clear distinction between normal styles and webfonts styles, while keeping the implementation simple. * Since webfonts don’t have dependencies, the `$deps` argument was replaced with` $params`. These params can be used to register a webfont from local files, and auto-generate the CSSCSS Cascading Style Sheets. for `@font-face`. ## Enqueuing a webfont from a remote URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org To use a webfonts API (Google Fonts, Adobe fonts, etc), we can use the URL provided by the API directly: ```notranslate add_action( 'wp_enqueue_scripts', function() { wp_enqueue_webfont( // The handle 'dancing-script', // URL to the webfont CSS - can use any public API. 'https://fonts.googleapis.com/css2?family=Dancing+Script:wght@500;600&display=swap', ); } ); ``` This is identical to what we would previously do using the `wp_enqueue_style` function, but now using a more appropriately named `wp_enqueue_webfont` function. With the example code above, the webfont will be enqueued and the stylesheet’s handle will be `webfont-dancing-script`. ## Generating CSS for a webfont It is possible to generate the CSS for a webfont using the `provider` parameter and the `wp_webfont_generate_styles` function. A `provider` is an object with details about the provider’s implementation and a method to get (or generate) the CSS from that API. ### Generating styles for bundled font files To generate styles for bundled font-files, set the `provider` to `new WP_Fonts_Provider_Local()`. ```notranslate $my_font_styles = wp_webfont_generate_styles( array( 'provider' => new WP_Fonts_Provider_Local(), 'font-family' => 'My Font', 'font-display' => 'swap', 'font-style' => 'normal', 'font-weight' => '400', 'src' => array( get_template_directory_uri() . '/fonts/font.woff2', get_template_directory_uri() . '/fonts/font.woff', ), ) ); ``` ### Generating styles for Google fonts To generate styles for a Google font, set the `provider` to `new WP_Fonts_Provider_Google`. ```notranslate $roboto_styles = wp_webfont_generate_styles( array( 'provider' => new WP_Fonts_Provider_Google(), 'font-family' => 'Roboto', 'font-weight' => '400', ) ); ``` ## Using the generated styles You can attach the styles to an existing stylesheet using `wp_add_inline_style`: ```notranslate add_action( 'wp_enqueue_scripts', function() { // Enqueue theme stylesheet. wp_enqueue_style( 'my-theme-styles', get_theme_file_uri( 'style.css' ) ); // Get webfont styles. $roboto_styles = wp_webfont_generate_styles( array( 'provider' => new WP_Fonts_Provider_Local(), 'font-family' => 'Roboto', 'font-weight' => '400', ) ); // Add webfont styles. wp_add_inline_style( 'my-theme-styles', $roboto_styles ); } ); ``` Alternatively, you can use the `wp_enqueue_webfont` function: ```notranslate add_action( 'wp_enqueue_scripts', function() { wp_enqueue_webfont( 'roboto-400', '', array( 'provider' => new WP_Fonts_Provider_Local(), 'font-family' => 'Roboto', 'font-weight' => '400', ) ); } ); ``` This will internally call `wp_enqueue_style` with a blank `$src`, and attach the webfoot styles to the defined `$handle`. ## Adding implementations for more 3rd-party APIs At the moment of this writing, Google-Fonts is the most popular API for web fonts, and the only one publicly available, free, with OpenSource-compatible fonts. Adding implementations for more APIs in the future can be done by extending the ` WP_Fonts_Provider` class. ## The `$params` argument The `$params` argument is formatted as an array and accepts all valid CSS props of `@font-face` as its array keys. Any extra args are ignored. The list of valid descriptors was taken from [MDN](https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face). Defining a `font-family` is mandatory, and skipping that results in no CSS getting generated. ### The `src` If we’re enqueueing a webfoot from bundled files, then we can use the `src` to define the files. If we only want to define a single file for the webfont, then we can add it as a string (`'src' => $url`). If we have multiple files for the webfont ( different formats to support older browsers), then we can use an array (`'src' = > [ $url1, $url2 ]`). In this case, the URLs get internally reordered for browser support (`woff2`, `woff`, `ttf`, `eot`, `otf`). SVG for webfonts is not supported because they have been deprecated (see [caniuse.com/svg-fonts](https://caniuse.com/svg-fonts)), so if provided it gets removed (like any other invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also _notabug_) that indicates the ticket is not a bug, is a support request, or is generally invalid. type). Note: The src can also accept data-urls. ### Variable fonts The `font-variation-settings` property accepts either a string (`normal`), or an array of key/value pairs (e.g. `["wght" => 637, "wdth" => 100]`) and returns a string of these values (e.g., `wght 637, wdth 100`). _Props [@jonoaldersonwp](https://profiles.wordpress.org/jonoaldersonwp/), [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) for reviewing_ [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 10:11 pm _on_ September 27, 2021 Tags: [5.8.2 ( 16 )](https://make.wordpress.org/core/tag/5-8-2/), [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [core ( 743 )](https://make.wordpress.org/core/tag/core/), [week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/)    # 󠀁[A Week in Core – September 27, 2021](https://make.wordpress.org/core/2021/09/27/a-week-in-core-september-27-2021/)󠁿 Welcome back to a new issue of _Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress._. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between September 20 and September 27, 2021. * 22 commits * 23 contributors * 49 tickets created * 6 tickets reopened * 57 tickets closed The Core team is currently working on the next point (5.8.2) and major (5.9) releases 🛠 Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the [Trac timeline for the period above](https://core.trac.wordpress.org/timeline?from=09%2F27%2F2021&daysback=7&authors=&ticket=on&changeset=on&repo-=on&repo-design=on&repo-tests=on&sfp_email=&sfph_mail=&update=Update). The following is a summary of commits, organized by component and/or focus. ## Code changes ### Build/Test Tools * Remove the PHPUnit container from local Docker environment – [#54112](https://core.trac.wordpress.org/ticket/54112) * Splits and improves `compat` tests – [#39265](https://core.trac.wordpress.org/ticket/39265), [#53363](https://core.trac.wordpress.org/ticket/53363) * Update PHPUnit configuration for PHPUnit 9.5.10/8.5.21+ – [#54183](https://core.trac.wordpress.org/ticket/54183) * Upgrades `Tests_Multisite_MS_Permalink_Collision` fixture methods and strict assertion – [#51147](https://core.trac.wordpress.org/ticket/51147) ### Code Modernization * Fix “passing null to non-nullable” deprecation in `_mb_substr()` – [#53635](https://core.trac.wordpress.org/ticket/53635) ### Coding Standards * Fix the alignment of the array – [[51855]](https://core.trac.wordpress.org/changeset/51855) * Remove duplicate assignment from a ternary operator in `WP_MS_Sites_List_Table:: site_states()` – [#38296](https://core.trac.wordpress.org/ticket/38296) ### Docs * Add `@since` notes to `register_setting()` for the deprecated `misc` and `privacy` option groups – [#53399](https://core.trac.wordpress.org/ticket/53399) * Document some more common names for dynamic hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. and standardise the phrasing used – [#53581](https://core.trac.wordpress.org/ticket/53581) * Fix typo in the `$clear_working` parameter description in `WP_Upgrader` methods– [#54163](https://core.trac.wordpress.org/ticket/54163) * Miscellaneous docblockdocblock (phpdoc, xref, inline docs) corrections and improvements– [#52217](https://core.trac.wordpress.org/ticket/52217), [#53399](https://core.trac.wordpress.org/ticket/53399) * Update description for `retrieve_widgets()` per the documentation standards – [#53811](https://core.trac.wordpress.org/ticket/53811) * Update and enhance the docs for `retrieve_widgets()` – [#53811](https://core.trac.wordpress.org/ticket/53811) ### Formatting * Pass the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. instance as a parameter to the `render_block` filters – [#53596](https://core.trac.wordpress.org/ticket/53596) ### General * Fix code quality issues which were identified by static analysis – [#52217](https://core.trac.wordpress.org/ticket/52217) ### Posts, Post Types * Don’t add a trailing number when there is a unique post parent – [#51147](https://core.trac.wordpress.org/ticket/51147) ### Tests * Correct the `@ticket` reference in `wp_terms_checklist()` tests – [#53363](https://core.trac.wordpress.org/ticket/53363), [#51137](https://core.trac.wordpress.org/ticket/51137) * Don’t skip some Ajax tests on multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog( wp_posts becomes wp_0_posts). See also **network**, **blog**, **site**, add them to the `ms-excluded` group instead – [#53363](https://core.trac.wordpress.org/ticket/53363) * Further improve the tests for `avoid_blog_page_permalink_collision()`: – [#51147](https://core.trac.wordpress.org/ticket/51147) * Remove unnecessary `setUp()` and `tearDown()` methods in multisite tests – [#53363](https://core.trac.wordpress.org/ticket/53363) * Rename classes in `phpunit/tests/multisite/` per the naming conventions – [#53363](https://core.trac.wordpress.org/ticket/53363) * Update the `Services_JSON` test for PHPUnit 9.5.10/8.5.21+ – [#54183](https://core.trac.wordpress.org/ticket/54183), [#54029](https://core.trac.wordpress.org/ticket/54029), [#53363](https://core.trac.wordpress.org/ticket/53363) ## Props **Thanks to the 23 people who contributed to WordPress Core on Trac last week:** [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/) (5), [@jrf](https://profiles.wordpress.org/jrf/)( 5), [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/) (3), [@netweb](https://profiles.wordpress.org/netweb/)( 2), [@joelcj91](https://profiles.wordpress.org/joelcj91/) (1), [@MaximeCulea](https://profiles.wordpress.org/maximeculea/)( 1), [@zieladam](https://profiles.wordpress.org/zieladam/) (1), [@mukesh27](https://profiles.wordpress.org/mukesh27/)( 1), [@pbiron](https://profiles.wordpress.org/pbiron/) (1), [@aezazshekh](https://profiles.wordpress.org/aezazshekh/)( 1), [@zenithcity](https://profiles.wordpress.org/zenithcity/) (1), [@whyisjake](https://profiles.wordpress.org/whyisjake/)( 1), [@knutsp](https://profiles.wordpress.org/knutsp/) (1), [@tubys](https://profiles.wordpress.org/tubys/)( 1), [@Daschmi](https://profiles.wordpress.org/daschmi/) (1), [@jeremyfelt](https://profiles.wordpress.org/jeremyfelt/)( 1), [@audrasjb](https://profiles.wordpress.org/audrasjb/) (1), [@terriann](https://profiles.wordpress.org/terriann/)( 1), [@stormrockwell](https://profiles.wordpress.org/stormrockwell/) (1), [@johnbillion](https://profiles.wordpress.org/johnbillion/)( 1), [@costdev](https://profiles.wordpress.org/costdev/) (1), [@desrosj](https://profiles.wordpress.org/desrosj/)( 1), and [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) (1). **Congrats and welcome to our 4 new contributors of the week: **[@aezazshekh](https://profiles.wordpress.org/aezazshekh/), [@zenithcity](https://profiles.wordpress.org/zenithcity/), [@tubys](https://profiles.wordpress.org/tubys/), and [@Daschmi](https://profiles.wordpress.org/daschmi/) ♥️ **Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 11), [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) (4), [@johnbillion](https://profiles.wordpress.org/johnbillion/)( 4), [@whyisjake](https://profiles.wordpress.org/whyisjake/) (2), and [@azaozz](https://profiles.wordpress.org/azaozz/)( 1). [#5-8-2](https://make.wordpress.org/core/tag/5-8-2/), [#5-9](https://make.wordpress.org/core/tag/5-9/), [#core](https://make.wordpress.org/core/tag/core/), [#week-in-core](https://make.wordpress.org/core/tag/week-in-core/) [ ](https://profiles.wordpress.org/get_dave/) [David Smith](https://profiles.wordpress.org/get_dave/) 8:43 am _on_ September 27, 2021 Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/), [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-agenda ( 189 )](https://make.wordpress.org/core/tag/core-editor-agenda/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/)    # 󠀁[Editor Chat Agenda: 29 September 2021](https://make.wordpress.org/core/2021/09/27/editor-chat-agenda-29-september-2021/)󠁿 Facilitator and notetaker: [@get_dave](https://profiles.wordpress.org/get_dave/). This is the agenda for the weekly _editor chat_ scheduled for [Wednesday, September ](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210929T14&ah=1) [29](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210721T16&p1=187&ah=1) [, 2021, 03:00 PM GMT+1](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210929T16&p1=187&ah=1). _This meeting is held in the [#core-editor](https://wordpress.slack.com/messages/C02QB2JS7) channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)._ * GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) 11.6.0 ([RC available](https://github.com/WordPress/gutenberg/releases/tag/v11.6.0-rc.1)). * [WordPress 5.9](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/)“ Go, no go” date and [priorities](https://make.wordpress.org/core/2021/08/13/preliminary-road-to-5-9/). * Updates based on [updated scope for site editing projects](https://github.com/WordPress/gutenberg/issues/33094): - Template editor. - Patterns. - Styling. - Navigation BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. & Navigation Editor. - Block based WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget- ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Editor. - Mobile Team. * Task Coordination. * Open Floor. If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion: * If you have anything to share for the Task Coordination section, please leave it as a comment on this post. * If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below. [#agenda](https://make.wordpress.org/core/tag/agenda/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-agenda](https://make.wordpress.org/core/tag/core-editor-agenda/), [#meeting](https://make.wordpress.org/core/tag/meeting/) [ ](https://profiles.wordpress.org/jrf/) [Juliette Reinders Folmer](https://profiles.wordpress.org/jrf/) 5:48 am _on_ September 27, 2021 Tags: [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [build-test-tools ( 4 )](https://make.wordpress.org/core/tag/build-test-tools/), [dev-notes ( 647 )](https://make.wordpress.org/core/tag/dev-notes/), phpunit, [unit tests ( 4 )](https://make.wordpress.org/core/tag/unit-tests/) # 󠀁[Changes to the WordPress Core PHP Test Suite](https://make.wordpress.org/core/2021/09/27/changes-to-the-wordpress-core-php-test-suite/)󠁿 ## Why were changes needed? [[ Dev Wapuu Image credits: [@marktimemedia](https://profiles.wordpress.org/marktimemedia/) The WordPress test suite uses the industry standard [PHPUnit](https://phpunit.de/) tool to run the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher unit tests. Over the years, PHPUnit has seen a number of changes, new assertions being introduced, different annotations and more, but most notably, as of PHPUnit 8.0, a `void` return type was added to the typical fixture `setUp()` and `tearDown()` methods. This `void` return type is problematic in the context of WordPress, as return types in general were only introduced in PHP 7.0 and the `void` return type wasn’t introduced until PHP 7.1. While WordPress still has a minimum PHP version of PHP 5.6, the ` void` return type can not be introduced in the test suite as it would inhibit the tests from being run on PHP 5.6 and 7.0. At the same time, having to run the tests on older PHPUnit versions (PHPUnit < 8.0) made it increasingly difficult to get the test suite to run on new PHP versions, like PHP 8.0 and the upcoming PHP 8.1 (expected end of November) as these older PHPUnit versions are no longer supported and are not being made compatible with newer PHP versions anymore. Over the past few years, a number of different solution directions were explored and rejected, largely due to the large maintenance burden these would add to the small team of WordPress contributors maintaining the test framework. With the upcoming release of PHP 8.1 as a driver, [we took another look at this problem and the available tooling in the wider PHP field](https://www.youtube.com/watch?v=SAtiKaUwLU4) and a solution has now been implemented which should future-proof the test suite for, at least, a number of years. ## The solution The implemented solution is based on the external [PHPUnit Polyfills](https://github.com/Yoast/PHPUnit-Polyfills) library, which _“allows for creating PHPUnit cross-version compatible tests by offering a number of polyfills for functionality which was introduced, split up or renamed in PHPUnit”_. The PHPUnit Polyfills also solves the `void` conundrum via a tailored `TestCase` using `snake_case` methods. In effect, this means that the WP CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. test suite can now run on all PHPUnit versions between PHPUnit 5.7.21 up to the latest release (at the time of writing: PHPUnit 9.5.10), which allows for running the test suite against all supported PHP versions [using the most appropriate PHPUnit version for that PHP version](https://phpunit.de/supported-versions.html). It also means that, as of mid August, the tests are being run against PHP 8.1 and fixes for PHP 8.1 compatibility are [currently being made](https://core.trac.wordpress.org/ticket/53635). **_With the PHPUnit Polyfills in place, tests can now be written using the feature set of the _highest _supported version of PHPUnit._** The Polyfills library will fill in the gaps and ensure the tests can still run on lower versions of PHPUnit without problems. ## What has changed? 1. The [Composer `lock` file has been removed](https://core.trac.wordpress.org/ticket/47381). The version constraints in the `composer.json` file have been made stricter to ensure the developer experience is not negatively impacted by this with regards to coding standards checks. 2. The [PHPUnit Polyfills](https://github.com/Yoast/PHPUnit-Polyfills) library at version `^1.0.1` has been added as a Composer `dev` dependency. 3. All WordPress Core tests now use PHPUnit 9.x assertions and expectations. 4. All WordPress Core tests now use `snake_case` fixture methods, i.e. `set_up()` instead of `setUp()` and `tear_down()` instead of `tearDown()`. 5. The minimum supported PHPUnit version has been raised to PHPUnit 5.7.21 (was 5.4.0). 6. The WordPress Core test bootstrap file will no longer throw an error when the tests are being run with PHPUnit 8.x or 9.x. 7. The WordPress Core test bootstrap file **_will_** throw an error when the PHPUnit Polyfills are not available or do not comply with the minimum version requirements. 8. All [WP Core native assertions](https://make.wordpress.org/core/handbook/testing/automated-testing/writing-phpunit-tests/#using-assertions) now have an extra, optional `$message` parameter, just like all PHPUnit native assertions. Please use this parameter in all tests which contain more than one assertion to make debugging tests easier. 9. The `WP_UnitTestCase_Base::setExpectedException()` method is deprecated and should no longer be used. 10. The `WP_UnitTestCase_Base::checkRequirements()` method is deprecated and no longer functional, and in reality hasn’t been for a long time for anyone using it in combination with PHPUnit 7.0+. 11. The copies of the PHPUnit SpeedTrapListener classes have been removed as they were never actively used in Core. Anyone who still wants to use the SpeedTrapListener can [install it separately](https://github.com/johnkary/phpunit-speedtrap). 12. The copies of the PHPUnit 9.x MockObject classes which were introduced in the WP Core test suite in WP 5.6 have been removed, as they are no longer needed when the tests are run on the appropriate PHPUnit version for the PHP version used. #### While the above changes have been made in WordPress 5.9, a minimal selection of these changes 󠀁[has been backported to WordPress 5.2 – 5.8](https://core.trac.wordpress.org/ticket/53911)󠁿: 1. The PHPUnit Polyfills at version `^1.0.1` is now a requirement for the test suites in WP 5.2 – 5.8 and this requirement will be enforced via the test bootstrap. 2. … which makes all the polyfills for PHPUnit 9.x assertions and expectations available when running tests against WP 5.2 – 5.8. 3. Additionally, `snake_case` wrapper methods have been added for the `camelCase` fixture method names, meaning that for WP 5.2 – 5.8, the `snake_case` fixture method names will work without needing further work-arounds, both for fixture declarations as well as for calling the `parent::set_up()` and the likes. _There is one caveat to this: the backported implementation presumes a fixed order for calling the parent( camelCase) methods versus the child (snake\_case) methods: for `set\_up*()` methods: parent first, child second; for `tear\_down*()` methods: child first, parent second. __This is the standard order, but if you have a fixture method which diverges from this or doesn’t call the parent, you may get unexpected results._ These backports allow for backporting future (security) fixes for WordPress itself without having to make the accompanying tests compatible with older PHPUnit versions. These backports will also make it more straightforward for extenders to continue to test their pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party./theme against multiple WordPress versions. For full details about all the changes, please have a read through [Trac ticket 46149](https://core.trac.wordpress.org/ticket/46149). ### Changes under the hood which should not be noticeable: A new `PHPUnit_Adapter_TestCase` class has been added. This class is nested in-between the `WP_UnitTestCase_Base` class and the PHPUnit `TestCase` class and provides the PHPUnit cross-version adapter layer. All PHPUnit assertion polyfill methods which previously existed in WP Core have been removed as they are no longer necessary now this functionality is provided via the PHPUnit Polyfills library. All polyfills for assertions/expectations which were previously in WP are still available, they are now just provided via the Polyfills package. As for the Docker set up: the PHPUnit container is no longer needed and [has been removed](https://core.trac.wordpress.org/ticket/54112) from the docker-compose config. ### What hasn’t changed: * The PHPUnit class aliases (for support of PHPUnit 5), which WP provided are still available, though shouldn’t be needed anymore. * You can still extend the `WP_UnitTestCase` class for your tests and will receive access to everything which was available before + more (i.e. a complete set of polyfills). ### Future changes There is a [ticket open to rename some of the WordPress native test helper methods](https://core.trac.wordpress.org/ticket/54029) to handle the “doing it wrong” and WP native deprecation notices, as the current method names (too) closely resemble a PHPUnit native method name, which can easily lead to confusion and use of the wrong methods in tests. When that ticketticket Created for both bug reports and feature development on the bug tracker. is actioned, this dev-note will be updated with the relevant information. ## What does this mean for contributors to WordPress Core? ### In general: If you use [Composer](http://getcomposer.org/) locally, please run `composer update-- with-all-dependencies` (or `composer update -W` for short) from the root of your WordPress clone **_now_** to make sure your install is updated and to get the most appropriate versions of the dependencies for the PHP version you are running on. ▶ **_Go on, do that now. This dev-note will wait patiently for you to come back._** You will need to run this command semi-regularly in the future (whenever the `composer. json` file has been updated). For WP 5.9 and higher, please don’t use `composer install` anymore. If, for example for backports, you need to install the dependencies for WP 5.8 or lower, in that case, you still need to run `composer install`. 🎓 **Why?** The first time you run `composer install` locally, it creates a `composer.lock` file and when you run Composer again, it will look at your `composer.lock` file to install the “locked” versions again. Previously, with the committed `composer.lock` file, the `lock` file was managed and updated centrally. However, that also meant that you often would be running the dev tools at a version which wasn’t the most appropriate one for the PHP version you are working under. This was getting more and more problematic for running the tests, which is why the file was removed. Now the `composer.lock` file is no longer committed, you have to update it yourself to make sure you receive the latest version of the `dev` dependencies appropriate for your PHP version and within the version constraints set in the `composer.json` file. ### For running the Core tests: If you usually run the Core tests via **Docker** using the `npm run test:php` command, you can continue to do so and all should still work as expected. If you usually run the Core tests via a **Composer** installed version of PHPUnit, again, you can continue to do so and all should still work as expected as long as you followed the [above instructions](https://make.wordpress.org/core/2021/page/15/?output_format=md#core-contributors-general) to run `composer update -W` first. If you usually run the Core tests via a **PHAR** file, you either have to run `composer update -W` once in a while or you have to set up a clone of the PHPUnit Polyfills repo. For more information about this last option, please see the [set up information in the handbook](https://make.wordpress.org/core/handbook/testing/automated-testing/phpunit/#workflow-4-setting-up-to-run-with-the-phpunit-phar-file-without-composer). If you are running locally on PHP 7.2 or higher, you may want to download a more recent PHPUnit PHAR file (PHPUnit 8 or 9) to benefit from the advances which have been made in PHPUnit. If you are running the tests locally on PHP 7.2 or higher, you may notice the test runs being faster and the output being enhanced as the tests will now run on a more recent PHPUnit version. 💡 **Pro-tip:** Now might also be a good time to verify that your local `wp-tests-config.php` file is still in sync with the `wp-tests-config-sample.php` file. Similarly, if you use a local `phpunit.xml` overload configuration file, it is strongly recommended to verify that any changes made in the `phpunit.xml.dist` (and `multisite. xml`) file are synced into your local configuration. ### For writing tests for Core: You can now use the [full range of assertions as available in PHPUnit 9.5](https://phpunit.readthedocs.io/en/9.5/assertions.html) in your tests. **Please use the most appropriate assertion available.** [Test fixture methods](https://phpunit.readthedocs.io/en/9.5/fixtures.html) **MUST** use `snake_case` method names from now on as per the below table. | Old name | New name | | `setUpBeforeClass()` | `set_up_before_class()` | | `setUp()` | `set_up()` | | `assertPreConditions()` | `assert_pre_conditions()` | | `assertPostConditions()` | `assert_post_conditions()` | | `tearDown()` | `tear_down()` | | `tearDownAfterClass()` | `tear_down_after_class()` | The [Make Core handbook page about writing tests](https://make.wordpress.org/core/handbook/testing/automated-testing/writing-phpunit-tests/) has been updated with this information. The page has also been enhanced with more handy tips and tricks, so please have a read through! ## What does this mean for plugins/themes running integration tests based on the WP Core test suite? It is a known fact that there are a lot of plugins/themes which use the WordPress Core test framework as a basis for their integration tests. If your plugin/theme is one of them, these changes will impact you as well. ### Step-by-step: how to make your test setup compatible with these changes and with higher PHPUnit versions: 1. Run your tests against PHP 7.4 with PHPUnit 7.x and WP 5.8.1 and make sure there are no pre-existing errors/failures. 2. Add [PHPUnit Polyfills](https://github.com/Yoast/PHPUnit-Polyfills) as a Composer` require-dev` dependency (or inherit it from WP). 3. If you add the Polyfills as a requirement and only support WP 5.9 and higher, remove the requirement for PHPUnit in favour of letting the Polyfills handle it. This will prevent potential future version constraint conflicts. 4. * If you still need/want to run your tests against older WP versions, keep the PHPUnit requirement and make sure it is set to `^5.7.21 || ^6.5 || ^7.5` and let CI (continuous integration script) handle removing that requirement for WP 5.9. * Or do it in reverse and remove the requirement for `dev` and add it back in CI for older WP versions. 5. Make sure the Polyfills autoloader is wired in to your test bootstrap. 6. * If you’ve chosen to “inherit the Polyfills from WP”, in this context that means that you use a full clone of WordPress and will install the Composer dependencies for WordPress before running the tests. In that case, you should be all set. * If you use only a partial clone of WordPress, like when your tests have been set up using the WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/)` scaffold` command, or if you don’t run WordPress’ Composer setup, please make sure you load the Polyfills autoloader in your test bootstrap before running the WP native test bootstrap. - If you include your Composer `vendor/autoload.php` file as your test bootstrap before you run the WP native test bootstrap, you’re all set already, the Polyfills autoloader will be included automatically. - Alternatively, you can add a `require_once 'path/to/vendor/yoast/phpunit- polyfills/phpunitpolyfills-autoload.php';` in your test bootstrap **_before_** including the WP native test bootstrap. - As a last alternative, you can declare a `WP_TESTS_PHPUNIT_POLYFILLS_PATH` constant containing the absolute path to the root directory of the PHPUnit Polyfills installation in your plugin/theme’s own test bootstrap file. Again, this constant must be declared prior to running the WP native test bootstrap file. 7. Search your codebase for declarations of the [fixture methods](https://make.wordpress.org/core/2021/page/15/?output_format=md#core-contributors-writing-tests), as well as calls to (parent) fixture methods, and replace `camelCase` with `snake_case` in the method names. Example: 8. ``` // Old: public function setUp() { parent::setUp(); // Do something. } // New: public function set_up() { parent::set_up(); // Do something. } ``` 9. Verify your tests run without errors after the changes by running them against PHP 7.4 on PHPUnit 7.x with **WP `5.8`** . 10. Verify your tests run without errors after the changes by running them against PHP 7.4 on PHPUnit 7.x with **WP `trunk`** (= WP 5.9). 11. While using WP `trunk`/`5.9`, switch to PHPUnit 8.x – look out for deprecation notices PHPUnit throws and just literally do what they tell you to do. 12. While still using WP `trunk`/`5.9`, switch to PHPUnit 9.x – look out for deprecation notices PHPUnit throws and just literally do what they tell you to do. Once you’ve run through these steps, your tests should be cross-version compatible with PHPUnit 5.7.21 – 9.5, able to run against the WordPress 5.2 to 5.9 branches and able to run on PHP 5.6 – 8.1. Next, you may want to run your tests against PHP 8.0 and 8.1 using PHPUnit 9.x with WP 5.9 to see if your plugin/theme is compatible with these more recent PHP versions. 🚨 **Pro-tip:** If you want your CI build to fail when PHPUnit encounters PHP native deprecation notices, make sure to add `convertDeprecationsToExceptions="true"` to your PHPUnit configuration file as the default value for this setting has been changed to `false` in PHPUnit 9.5.10/8.5.21. Enabling this setting is strongly recommended for testing your plugin/theme against PHP 8.1, as PHP 8.1 introduces a **_lot_** of new deprecations. ### What to do when running tests in CI against multiple WP/PHP combinations? If you are running your plugin/theme integration tests against multiple WordPress and PHP combinations, you will most likely need to make some adjustments to your Continuous Integration (CI) script(s). Which exact changes you need to make depends entirely on your specific setup. There is no “one size fits all” solution. As a general rule of thumb: * **WP 5.2 – 5.5** is able to run tests against **PHP 5.6 – 7.4** with **PHPUnit 5.x** (PHP 5.6 and 7.0) **– 7.x** (PHP 7.1 and higher). * **WP 5.6 – 5.8** is able to run tests against **PHP 5.6 – 8.0** with **PHPUnit 5.x** (PHP 5.6 and 7.0) **– 7.x** (PHP 7.1 and higher). * **WP 5.9 and higher** is able to run tests against **PHP 5.6 – 8.1** with **PHPUnit 5.x – 9.x** (use the [most appropriate PHPUnit version](https://phpunit.de/supported-versions.html) for each PHP version). Also see the [PHP Compatibility and WordPress Versions](https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/) and [PHPUnit Compatibility and WordPress Versions](https://make.wordpress.org/core/handbook/references/phpunit-compatibility-and-wordpress-versions/) pages in the Make Core handbook. Other typical things to take into account and to work around when needed: * Is there a `config - platform - php` setting in your `composer.json` which fixes the PHP version to a specific version – typically PHP 5.6 – for installing dependencies? If so, you may need to either selectively remove this setting or run Composer with `--ignore-platform-reqs` for certain WP/PHP combinations in your test matrix. * Has the `composer.lock` file been committed ? In that case, you may need to either selectively remove that file in CI before running `composer install`; or run ` composer update -W` for certain WP/PHP combinations in your test matrix. * Do you use a complete clone of WP ? For WP 5.2 – 5.8, you’ll need to install the WP dependencies by using `composer install`.For WP 5.9 and higher, you’ll need to install the WP dependencies by using `composer update -W`. To make sure you run the test against the right PHPUnit version, you may need to run (a variation on): ```notranslate composer remove --dev phpunit/phpunit composer update --dev yoast/phpunit-polyfills --with-dependencies --ignore-platform-reqs ``` 💡 **Did you know ?** If you use GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/) Actions to run your tests for continuous integration and PHPUnit and the PHPUnit Polyfills are your only external test dependencies, as of Setup-PHP 2.15.0 (expected soon), you can use the `tools` key in the [`shivammathur/setup-php` action](https://github.com/marketplace/actions/setup-php-action) to install these: ```notranslate - name: Setup PHP with tools uses: shivammathur/setup-php@v2 with: php-version: '8.0' tools: phpunit-polyfills ``` For more information about the `tools` key for `setup-php`, see the [action documentation](https://github.com/shivammathur/setup-php#wrench-tools-support). For more information on how to wire in the PHPUnit Polyfills when installed via ` setup-php`, see the [FAQ section of the Polyfills documentation](https://github.com/Yoast/PHPUnit-Polyfills#q-how-do-i-run-my-tests-when-the-library-is-installed-via-the-github-actions-setup-php-action-). ## Anticipating some frequently asked questions ### I’m a plugin/theme maintainer, but don’t use Composer, can I still run my integration tests? Yes, but you do need to make sure that either the Polyfills are available via a [Composer](https://getcomposer.org/) global or local installLocal Install A local install of WordPress is a way to create a staging environment by installing a LAMP or LEMP stack on your local computer. or via some other manner, like a clone of the repo. If you haven’t looked at [Composer](https://getcomposer.org/) before, now might be a good time to take a look at it. ### I’m running my tests via another tool stack (like BrainMonkey, WP Mock, PHP Mock, WP Browser, PestPHP), how do the changes made to the WordPress test suite affect me? Short answer: They don’t. Long answer: if you want to run your tests against multiple PHP and PHPUnit combinations, you may still find the [PHPUnit Polyfills](https://github.com/Yoast/PHPUnit-Polyfills) library helpful to you. If you’ve not heard of the above mentioned tools before and want to read up on them, here are some links: * [BrainMonkey](https://giuseppe-mazzapica.gitbook.io/brain-monkey/) * [WP Mock](https://github.com/10up/wp_mock) * [PHP Mock](https://github.com/php-mock/php-mock) * [WP Browser](https://wpbrowser.wptestkit.dev/) * [PestPHP](https://pestphp.com/) ### I used the WP-CLI `scaffold` command to set up my integration tests. How do the changes made to the WordPress test suite affect me? There is no automated way right now to adapt existing tests for which the initial was created via the [WP-CLI `scaffold` command](https://github.com/wp-cli/scaffold-command/), to make use of the new setup. The current recommendation is to go through the steps in “[What does this mean for plugins/themes running integration tests based on the WP Core test suite?](http://impact-plugin-theme-integration-tests)“, which might be more or less involved depending on what version of the scaffolded test setup you are currently using. A future version of the WP-CLI `scaffold plugin-tests` command will provide an upgrade mechanism to automatically upgrade an existing test setup to the new requirements. This will include adding a fully Composer-based testing setup as a replacement for the current bootstrap logic, making a `composer update` possible in the future to keep up with further test setup changes. If you’re interested in learning more about these plans for the future, please subscribe to the [issue on GitHub](https://github.com/wp-cli/scaffold-command/issues/299) to stay informed. ### I’m using WP Test Utils for my unit and integration tests. How do the changes made to the WordPress test suite affect me? [WP Test Utils](https://github.com/Yoast/wp-test-utils) is a library offering utilities for both unit testing and integration testing for WordPress plugins and themes. WP Test Utils already includes the PHPUnit Polyfills. For the unit testing part, which is based on BrainMonkey, you are not affected by the changes. If you use the integration testing utilities, you will need to make the change from` camelCase` to `snake_case` for the fixture methods in your test suite and you can now potentially widen the PHPUnit version requirements for your integration tests( also see the information about this in step 3 of the [“Step by step” guide](https://make.wordpress.org/core/2021/page/15/?output_format=md#integration-tests-step-by-step) and the information about [adjusting CI scripts](https://make.wordpress.org/core/2021/page/15/?output_format=md#integration-tests-ci-changes)). Presuming you were already using the PHPUnit Polyfills provided by the Test Utils to use modern assertions, that’s it. You’re done. WP Test Utils will continue to handle the integration test bootstrapping, which allows for running the tests against multiple WordPress and PHP versions. The first version of WP Test Utils which has full support for the test framework changes made in WP 5.9, is WP Test Utils 1.0.0. WP Test Utils 1.0.0 also includes improved support for integration tests which were created using the WP-CLI `scaffold` command and support for running tests against WP versions which don’t include the backports, like WP 5.2 – 5.8 point releases released before today, as well as WP < 5.2. --- Props to [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/), [@johnbillion](https://profiles.wordpress.org/johnbillion/), [@dingo_d](https://profiles.wordpress.org/dingo_d/), [@netweb](https://profiles.wordpress.org/netweb/), [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/), [@swissspidy](https://profiles.wordpress.org/swissspidy/), [@schlessera](https://profiles.wordpress.org/schlessera/) for reviewing ahead of publication. [#5-9](https://make.wordpress.org/core/tag/5-9/), [#build-test-tools](https://make.wordpress.org/core/tag/build-test-tools/), [#dev-notes](https://make.wordpress.org/core/tag/dev-notes/), [#phpunit](https://make.wordpress.org/core/tag/phpunit/), [#unit-tests](https://make.wordpress.org/core/tag/unit-tests/) [ ](https://profiles.wordpress.org/circlecube/) [Evan Mullins](https://profiles.wordpress.org/circlecube/) 9:03 pm _on_ September 23, 2021 Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [5.8.1 ( 8 )](https://make.wordpress.org/core/tag/5-8-1/), [5.8.2 ( 16 )](https://make.wordpress.org/core/tag/5-8-2/), [5.8.3 ( 2 )](https://make.wordpress.org/core/tag/5-8-3/), [5.8.x ( 13 )](https://make.wordpress.org/core/tag/5-8-x/) # 󠀁[WordPress 5.8.2+ Release Schedule](https://make.wordpress.org/core/2021/09/23/wordpress-5-8-2-release-schedule/)󠁿 Thanks to everyone that helped release [5.8.1](https://wordpress.org/news/2021/09/wordpress-5-8-1-security-and-maintenance-release/) on September 9th! It’s time to look ahead to 5.8.2, and other 5.8.x releases (if necessary). Like the [5.8.1 release](https://make.wordpress.org/core/2021/08/24/wordpress-5-8-x-release-team-and-5-8-1-schedule/), these releases are following the strategy of having a [consistent minor release squad](https://make.wordpress.org/core/2021/07/28/consistent-minor-release-squad-leaders-for-each-major-branch-trial-run-retrospective-and-5-8-x-releases/) for all 5.8.x releases. ## 5.8.2 The following schedule is proposed for a 5.8.2 release: * RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/2021/page/15/?output_format=md#alpha-beta).: Tuesday, October 5, 2021 * Final release: Tuesday, October 12, 2021 As of the publish date of this post, [19 open tickets](https://core.trac.wordpress.org/tickets/minor/workflow) are currently in the [5.8.2 milestone](https://core.trac.wordpress.org/milestone/5.8.2) for consideration. Please head over and check out that list to help contribute to the release. ## 5.8.3 (if necessary) For the 5.8.x release cycle, a 5.8.3 release will be pursued only if necessary. Below is the proposed schedule for 5.8.3: * RC: Tuesday November 2, 2021 * Final release: Wednesday, November 10, 2021 These dates also take into account the [5.9 release cycle](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/), which will be approaching the first betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. release at this time. ## Release coordination Because the 5.8.x releases are part of 5.8 by extension, all coordination and conversation related to the 5.8.x releases are held in the [#5-8-release-leads](https://wordpress.slack.com/archives/C01VACX5E2W) SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) channel. This channel will be archived when WordPress 5.9 is released. _Props _[@desrosj](https://profiles.wordpress.org/desrosj/) & [@audrasjb](https://profiles.wordpress.org/audrasjb/)_ for peer review. _ [#5-8](https://make.wordpress.org/core/tag/5-8/), [#5-8-1](https://make.wordpress.org/core/tag/5-8-1/), [#5-8-2](https://make.wordpress.org/core/tag/5-8-2/), [#5-8-3](https://make.wordpress.org/core/tag/5-8-3/), [#5-8-x](https://make.wordpress.org/core/tag/5-8-x/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 9:42 pm _on_ September 22, 2021 Tags: [5.8.x ( 13 )](https://make.wordpress.org/core/tag/5-8-x/), [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [dev chat ( 920 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 975 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Dev chat summary – September 22, 2021](https://make.wordpress.org/core/2021/09/22/dev-chat-summary-september-22-2021/)󠁿 [@audrasjb](https://profiles.wordpress.org/audrasjb/) led the chat on this [agenda](https://make.wordpress.org/core/2021/09/21/dev-chat-agenda-for-sept-22-2021/). You can also read the [Slack logs](https://wordpress.slack.com/archives/C02RQBWTW/p1632340821008300). ## Highlighted blogblog (versus network, site) posts Bringing to your attention some interesting reads and some call for feedback and/ or volunteers: * [What’s next in Gutenberg? (Mid-September 2021)](https://make.wordpress.org/core/2021/09/17/whats-next-in-gutenberg-mid-september-2021/) * [What’s new in Gutenberg 11.5? (16 September)](https://make.wordpress.org/core/2021/09/17/whats-new-in-gutenberg-11-5-16-september/) * [Editor chat summary: Wednesday, 15 September 2021](https://make.wordpress.org/core/2021/09/20/editor-chat-summary-wednesday-15-september-2021/) * [CSS Chat Summary: 16 September 2021](https://make.wordpress.org/core/2021/09/21/css-chat-summary-16-september-2021/) * [Core Editor Improvement: Introducing the Widget Group Block](https://make.wordpress.org/core/2021/09/22/core-editor-improvement-introducing-the-widget-group-block/) * [A Week in Core – September 20, 2021](https://make.wordpress.org/core/2021/09/21/a-week-in-core-september-20-2021/) * Feedback needed: [WordPress JavaScript Standards Change Proposal](https://make.wordpress.org/core/2021/09/21/wordpress-javascript-standards-change-proposal/) Worth mentioning: > **Thanks to the 42 contributors of the past week, including 7 new contributors! > Kudos to the 4 coreCore Core is the set of software required to run WordPress. > The Core Development Team builds WordPress. committers of the week, too.** > [**A Week in Core – September 20, 2021**](https://make.wordpress.org/core/2021/09/21/a-week-in-core-september-20-2021/) ## Upcoming releases updates ### Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.(s) [@desrosj](https://profiles.wordpress.org/desrosj/) and [@circlecube](https://profiles.wordpress.org/circlecube/) are still leading the 5.8.x releases. They will publish a schedule for 5.8.2 and –if needed– 5.8.3 on September 23. ### Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. Concerning the next major release —**WordPress 5.9**— a [planning roundup](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/) was published a couple weeks ago. Worth noting that [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) proposed a review of the upcoming 5.9 key features [in the last issue of the WordPress.org podcast](https://wordpress.org/news/2021/09/episode-16-a-sneak-peek-at-wordpress-5-9/). [@audrasjb](https://profiles.wordpress.org/audrasjb/) proposed to start to schedule bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs for the milestone. He will run the first scrub of 5.9 on [Thursday September 23, 2019 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190926T2000). Reminder: **everyone is welcome to run a bug scrub** on the `#core` SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) channel. If you are interested, please read this handbook post: [Leading bug scrubs](https://make.wordpress.org/core/handbook/tutorials/leading-bug-scrubs/). And yes, that’s a call for volunteers 🙂 Please add a comment below if you want to help. For 5.9, [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) pointed out that it would be nice to try to also plan some APAC-friendly bug scrubs when possible. ## Component maintainers updates **Help/About** – [@marybaum](https://profiles.wordpress.org/marybaum/) * [@marybaum](https://profiles.wordpress.org/marybaum/) and [@webcommsat](https://profiles.wordpress.org/webcommsat/) will schedule a scrub of the ten tickets currently in the milestone. **Build/Test Tools** – [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) * Some changes were implemented to make the PHPUnit Polyfills loading more flexible and improve the related messaging. See changesets [51810-51813](https://core.trac.wordpress.org/log/?revs=51810-51813) and ticketticket Created for both bug reports and feature development on the bug tracker. [#46149](https://core.trac.wordpress.org/ticket/46149) for more details. * The PHPUnit Polyfills package and related test infrastructure changes are now backported to a few older branches (WP 5.8 to 5.2). This makes it easier for developers to continue testing on multiple versions of WordPress while adding tests for newer versions of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher, which require more modern PHPUnit practices. See changesets [51838-51840, 51843-51846](https://core.trac.wordpress.org/log/?revs=51838-51840,51843-51846) and ticket [#53911](https://core.trac.wordpress.org/ticket/53911) for more details. * Work is now complete on Modernizing to the Latest PHPUnit version. Dev notedev note Each important change in WordPress Core is documented in a developers note,( usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. is being reviewed and plan is to publish on Monday. * PHP 8.1: work is nearly complete, i.e. identified through tests. Will be shifting shortly into community feedback and open call for contributions to identify and help fix compatibility issues. **General** – [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) and [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) * Various compatibility fixes for PHP 8.1. Thanks [@jrf](https://wordpress.slack.com/team/U04GMEHEL), [@hellofromtonya](https://wordpress.slack.com/team/U04NQ8LM3), and others helping with that effort. See changesets [51816-51818, 51829-51831](https://core.trac.wordpress.org/log/?revs=51816-51818,51829-51831) and ticket [#53635](https://core.trac.wordpress.org/ticket/53635) for more details. * Various PHP coding standards fixes. See changesets [51822-51826](https://core.trac.wordpress.org/log/?revs=51822-51826) and ticket [#53359](https://core.trac.wordpress.org/ticket/53359) for more details. **Internationalization** – [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) * A translator comment was added to clarify the “BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.” string in the Block widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. settings form. This should reduce confusion for Polyglots translating the string. **Toolbar** – [@sabernhardt](https://profiles.wordpress.org/sabernhardt/) * [@sabernhardt](https://profiles.wordpress.org/sabernhardt/) shared a draft of a Toolbar component update post (it’s also available in a [Google doc](https://docs.google.com/document/d/1Px3cAw1q8JqMpfZDNNF6FTwRaKk89v3CljfxuiXDZ1I/edit?usp=sharing) if you want to add comments that way) ## Open Floor From [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/): If you want to contribute to the Testing Team, [here’s this week’s edition of Week in Test](https://make.wordpress.org/test/2021/09/21/week-in-test-20-sep-2021/) which is a curated list of where testers (of any skillset) are needed this week. [#5-8-x](https://make.wordpress.org/core/tag/5-8-x/), [#5-9](https://make.wordpress.org/core/tag/5-9/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 12:33 am _on_ September 22, 2021 Tags: [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-improvement ( 35 )](https://make.wordpress.org/core/tag/core-editor-improvement/), [feature-widgets-block-editor ( 8 )](https://make.wordpress.org/core/tag/feature-widgets-block-editor/) # 󠀁[Core Editor Improvement: Introducing the Widget Group Block](https://make.wordpress.org/core/2021/09/22/core-editor-improvement-introducing-the-widget-group-block/)󠁿 While the [Block Widgets Editor was released with WordPress 5.8](https://wordpress.org/support/article/block-based-widgets-editor/), the work to improve the experience hasn’t stopped to help even more folks use blocks to build out widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. areas in an endless number of ways. The latest in a series of improvements comes with the [launch of Gutenberg 11.5 that introduces a Widget Group block](https://github.com/WordPress/gutenberg/pull/34484). This new blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. replicates the familiar experience of being able to add a title to a group of blocks and allows you to group any block, making it easier to move and layout content however you’d like. This both helps with compatibility for older themes when migrating over to the new editor and enables a more cohesive experience for building out widget areas. For example, before this update, it was tricky to get the spacing right for adding a headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. above another set of blocks. Now, you can do that with ease: _Video showing how to use the Widget Group Block_. This also makes it a breeze to move collections of blocks into new widget areas: _Video showing how you can drag and drop a collection of blocks within the Widget Group Block_. As always, you can also make these changes in the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.! For more general information about the Block Widgets Editor, [check out the Dev note](https://make.wordpress.org/core/2021/06/29/block-based-widgets-editor-in-wordpress-5-8/) and [the user documentation](https://wordpress.org/support/article/block-based-widgets-editor/). To get involved in this work, head to [#feature-widgets-block-editor](https://wordpress.slack.com/archives/C01D71823PB) and [explore the GitHub tracking project](https://github.com/WordPress/gutenberg/projects/27) to see what’s next.  Props to [@critterverse](https://profiles.wordpress.org/critterverse/) for the lovely videos! [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-improvement](https://make.wordpress.org/core/tag/core-editor-improvement/), [#feature-widgets-block-editor](https://make.wordpress.org/core/tag/feature-widgets-block-editor/) # Post navigation [← Older posts](https://make.wordpress.org/core/2021/page/16/?output_format=md) [Newer posts →](https://make.wordpress.org/core/2021/page/14/?output_format=md)