The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in the bug tracker.
GutenbergGutenbergThe 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/ version 20.4 was released!
Gutenberg version 20.4 was officially released today! This update brings a variety of enhancements and improvements to the blockBlockBlock 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. editor. This version is the final release to be merged into WordPress 6.8.
A detailed changelog article will follow shortly, providing an in-depth look at the features and changes in this version.
Forthcoming releases 🚀
Next major releasemajor releaseA 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.: 6.8 – BetaBetaA 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. 2
The Beta 2 release of WordPress 6.8 will be available on Tuesday, March 11th. Join the Release Party to test new features and provide feedback!
Stay tuned for weekly updates to keep you informed about the latest in WordPress editor development. Whether you’re a developer, designer, or content creator, these updates will keep you in the loopLoopThe Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop on all the key changes.
Don’t miss out — check out the weekly update and get ready for more!
Discussion 🤔
To avoid listing the topics here twice, all the necessary links and information can be found in the agenda. This section now includes a few additions.
6.8 – Beta 1 | Current update issue with versions older than 5.1 ⚠️
A bugbugA 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. was found preventing updates for versions older than 5.1 in Beta 1, with ticketticketCreated for both bug reports and feature development on the bug tracker.#63052 created. @joemcgill mentioned that @johnbillion will handle it when he’s back this week, and it shouldn’t affect Beta 2. 🥳
6.8 | Preparing Documentation for the 6.8 Release
@jeffpaul mentioned that the document is intended for the Helphub page, similar to the 6.7 release. Additionally, @milana_cap shared details on docs-related topics here.
Call for the Security Role for the upcoming 6.8 release parties
@desrosj mentioned that he can take on the security role, as it involves running the security test suite. He is open to involving more team members if anyone is interested, but he’s fine handling it on his own.
Open Floor 💬
6.8 Beta 1 | Feedback
After the Beta 1 release, a ticket was created for an issue (#63055) regarding missing template parts, related to #62574. @jeffpaul confirmed that changes from #62574won’t be included in 6.8 as is, but updates will resolve the gaps.
Thanks to @francinafor helping review this summary.
Last week, there were some exciting developments in the GutenbergGutenbergThe 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/ Editor. Below, you’ll find an overview of the key changes and improvements.
A special thanks goes to @krupaly2k for his excellent compilation of all the topics from the Gutenberg development team.
EnhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. ✨
Search Block: Background wrapper for ‘Button Inside’ option – This issue is a follow up of #69318 Currently, the ‘Button Inside’ option in the Search BlockBlockBlock 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. is missing a background wrapper with a common color as of the input, making the input and button appear separate instead of part of a single container.
Advanced Margin and Padding Editing for Block – Currently, the management of internal (padding) and external (margin) spacing for blocks in Gutenberg is limited and not very intuitive. Adding an advanced interface similar to Elementor would allow users to have precise control over block spacing without needing custom CSSCSSCascading Style Sheets..
Enhanced Block Management – Enhance Block Swapping – Intuitive Drag-and-Drop for Left/Right Reordering – The current block movement system in Gutenberg relies on up and down arrows or a basic drag-and-drop mechanism, which can be restrictive and unintuitive. A more visual and flexible approach, similar to how Elementor or Beaver Builder handles block positioning, would greatly enhance the user experience.
PR – Button Block: Add draft page creation capability – This PR adds the ability to create draft pages directly from the button block in the navigation editor, similar to how it already works in the navigation link block.
PR – Navigation in Site View: Automatically expand all options – This PR changes the default state of navigation submenus in Site View from collapsed to expanded, making all navigation options immediately visible to users without requiring manual expansion.
Bug 🐛
Block Directory: Issues in installing blocks from Inserter – When debugging the the issue #69315 found that when installing a block from inserter and then saving the post the block pluginPluginA 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/ or can be cost-based plugin from a third-party. doesn’t install and block disappears.
As with most releases since 20.0 this release has also primarily been focused on fixing bugs. But of course there are still always some features that join the mix.
Highlights
Ignore sticky posts in query loopLoopThe Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop
The query loop blockBlockBlock 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. now has a new option to ignore sticky posts. When selected, the query block ignores whether or not a post has the sticky option enabled. So, all posts show based on the sorting preferences selected without taking the sticky status into account.
Add social icon block variation for discord
The social icons block now ships with the option to add a Discord icon.
Changelog
Enhancements
Block Library
Query block: Add option to ignore sticky posts behavior. (69057)
Featured ImageFeatured imageA featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. block: Use resolution tool component. (68471)
Display root appender when default block is disabled. (68951)
Fix regressionregressionA software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. 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. for root appender logic. (68994)
Inserter: Remove block default icon from no results message. (68693)
Rename aspect property to ratio to carry the defaultAspect in AspectRatioDropdown. (69085)
Writing Flow: Restore early return for no block selection in tab nav hook. (69079)
Social Links: Fix appender size in non-iframeiframeiFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. editor. (68215)
REST APIREST APIThe 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/
Add support for the ‘ignore_sticky_posts’ argument. (68970)
Fix: Prevent Errors in HeaderHeaderThe 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. Processing and Encode URLs Properly. (67780)
Icons
Fix the background, arrowUpLeft, keyboardReturn and square icons. (69076)
Font Library
Refactor font variant components to use useId for checkbox IDs. (69050)
Block Directory
Remove block icon from InstalledBlocksPrePublishPanel. (69046)
DataViews
Fixed: Empty Pattern Overlap in Pattern Title in Dataviews Table Layout. (68997)
Media
Add optional chain to sizes indexing of media details in edit-site. (68995)
Block hooksHooksIn 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.
Interactivity APIAPIAn 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.
iAPI Router: Fix CSS rule order in some constructed style sheets. (68923)
iAPI Router: Revert “Handle styles assets on region-based navigation” (69222)
AccessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)
Components
Font Size Picker: Remove Custom option from FontSizePickerSelect dropdown. (69038)
Global Styles
Add missing list role to the list of blocks in the global Styles. (69027)
Block API
Block support: Preserve aria-label value in comment delimiter. (69002)
Block Editor
[Block Editor]: A11yAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) – Add and Update missing reduce-motion mixing. (68417)
Performance
Post Editor
Editor: Don’t use selector shortcuts for the taxonomyTaxonomyA taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. queries. (68998)
Editor: Optimize ‘PostAuthorCheck’ component data selection. (69105)
Style Book
Improve StyleBook resize responsiveness for Classic Theme. (68980)
Remove reactReactReact is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces.
https://reactjs.org-native dependabot group – Take 2. (69122)
PluginPluginA 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/ or can be cost-based plugin from a third-party.
Code Quality: Delete unused function from PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher Sync Issue generation script. (68947)
[Editor’s note: This survey was only answered by 3 people, only 2 of which were on the release squad. It’s useful as seeing three people’s distinct opinion, but not extrapolation.]
This post summarizes the feedback received from the WordPress 6.7 retrospective. Thank you to those who contributed their feedback via the retrospective survey and comments on the post. For ease of reading, feedback has been synthesized. Full feedback is available for review in the anonymized form responses and comments to the original post.
Please remember that the following feedback are suggestions to bear in mind for future releases rather than action items for implementation.
What would you keep?
Aligning Dev Chats to the time where Tech Release leads could attend was useful and should be considered in the future.
Release process.
What would you add?
Future release leads should be announced earlier—prior to the end of the previous release.
More robust testing around new features in conjunction with plugins.
What would you change, reduce, or remove?
The squad was announced too late.
The climate of contributing.
How did the collaboration feel?
This section included ways for one to indicate how much they agreed or disagreed with a statement around collaboration.
Would you like to be part of future release squads?
What is your feedback on the current release squad size?
Takeaways and next steps
One lead felt they and their co-leads were not appropriately respected by a sponsored non-lead and indicated their intent to not volunteer for another lead role without assurances that lead roles are to be respect by non-leads.
Another contributor indicated a general sense that release testing throughout the cycle was less that usual.
GutenbergGutenbergThe 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/ version 20.3 was released!
Gutenberg Version 20.3 was officially released last week! This new update brings a variety of enhancements and improvements to the blockBlockBlock 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. editor.
A detailed changelog article will follow shortly, providing an in-depth look at the features and changes in this version.
Forthcoming releases 🚀
Next major releasemajor releaseA 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.: 6.8 – BetaBetaA 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. 1
The Beta 1 release of WordPress 6.8 will be available on Tuesday, March 4th. Join the Release Party to test new features and provide feedback!
Next Gutenberg version: 20.4
Gutenberg 20.4 is scheduled for release on Wednesday, March 5th. This will be the final release to be merged into WordPress 6.8.
Stay tuned for weekly updates to keep you informed about the latest in WordPress editor development. Whether you’re a developer, designer, or content creator, these updates will keep you in the loopLoopThe Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop on all the key changes.
Clarifying our PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher support for 6.8
The discussion focused on PHP compatibility for WordPress 6.8. @joemcgill mentioned that @johnbillion was exploring moving ticketticketCreated for both bug reports and feature development on the bug tracker.#58320 to the 6.8 milestone, as the PHP compatibility page needs an update. It was suggested to review and potentially update the criteria for removing labels.
Over 40% of WordPress sites run PHP 8.0 or newer, so labeling PHP 8.0 as “beta” is unclear. It was clarified that “beta” support now applies to PHP 8.3 and 8.4, while 8.0, 8.1, and 8.2 are “compatible with exceptions.”
REST APIREST APIThe 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/ | Template Parts
For ticket #62574, the goal is to align on where to expose data in the REST API, coming from the GB pluginPluginA 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/ or can be cost-based plugin from a third-party.. The current plan is to add it to the index for logged-in users, likely merging this for Beta 1 unless a better alternative arises. Feedback is encouraged as a decision will need to be made soon. Mamaduka is open to following up on the PR/patchpatchA 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. based on feedback before or after Beta 1. @jorbin supported the idea of adding it only for logged-in users.
Style Book for Classic themes
The discussion focused on ticket #62509, which proposes making the Style Book available to classic themes in WordPress. This feature is being carried over from Gutenberg. The current plan is to commit the feature by Beta 1, though it may need refinement before RC1. There was a PR under review that modifies how the Style Book is shown based on theme support, which would be a change to the adminadmin(and super admin) menu. It was noted that while the Style Book would be available for all classic themes, adjustments to the UIUIUser interface and an opt-out strategy still need to be worked on.
The team discussed whether the feature should be committed for Beta 1 and whether testers were available to test both the Gutenberg and coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. PRs before the deadline. The consensus was that tickets close to landing could be included before Beta 1, but anything not ready should be punted to a later stage.
Open Floor 💬
WordPress 6.8 | TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. update
@audrasjb shared updated stats for the upcoming WordPress Release 6.8 release with detailed information.
Ticket Status
On the 354 tickets in the milestone:
about 30 tickets have been moved to Future Release or 6.9 since last week
194 tickets are closed as fixed (+19 compared to previous week)
160 tickets are still open (-17 compared to previous week)
Ticket Types
On the 160 still opentickets in the milestone:
99 are bugfixes
43 are enhancements
18 are blessed tasks
2 are feature requests
Misc infos:
We have 0 ‘high’ (or higher) priority ticket (-1):
On the 160 open tickets, 7 have the ‘commit’ keyword (+1)
On the 160 open tickets, 3 have the ‘early’ keyword (-3)
WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/APIAPIAn 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. Connections to a Different Location
@clorith is requesting feedback on the implementation in ticket #62132 and its viability for WordPress 6.8. The response can be found in the first comment from @jorbin.
Thanks to @audrasjbfor helping review this summary.
Last week, there were some exciting developments in the GutenbergGutenbergThe 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/ Editor. Below, you’ll find an overview of the key changes and improvements.
A special thanks goes to @krupaly2k for his excellent compilation of all the topics from the Gutenberg development team.
Need Design Feedback 🎨
[List View]Always open List View: disable sidebar animation when preference is enabled – When the ”Always open List View:’ preferences are enabled, the sidebarSidebarA 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. animation on first page load is a very distracting and unexpected experience.
Native WordPress custom fields are added twice – Custom Fields are sometimes being duplicated. Sometimes this results in two or even three copies of the same custom fieldCustom FieldCustom Field, also referred to as post meta, is a feature in WordPress. It allows users to add additional information when writing a post, eg contributors’ names, auth. WordPress stores this information as metadata. Users can display this meta data by using template tags in their WordPress themes. and value.
Spacer: Add background color support – Add the background-color design tool to the Spacer blockBlockBlock 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.
EnhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. ✨
Add lightbox functionality to Post Featured Image block – The Image block in Gutenberg includes a native lightbox functionality that allows users to expand images in a modal view. However, this functionality is not available in the Post Featured ImageFeatured imageA featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. block, even though it would be equally useful in this context.
PR #67052 for Make BlockManager component reusable – The current BlockManager component is tightly coupled to the showBlockTypes and hideBlockTypes actions and cannot be used for other purposes.
[AccessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)] PR #69248 for Audit the new Inserter accessibility – The new Inserter introduced in WordPress 5.5 has been identified by the accessibility team as a regressionregressionA software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. 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. in the accessibility level compared to WordPress 5.4.
PR #69239 for Gradient: Add a border – When the gradient is white the field in the color palette panel is hard to see.
Thanks to @krupaly2kfor helping to create this post.
There are no major announcements from the past week.
Forthcoming releases 🚀
Next major releasemajor releaseA 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.: 6.8
Next GutenbergGutenbergThe 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/ release: 20.3
The next Gutenberg release will be 20.3. It is scheduled for today, February 19 and will include the following issues.
Discussion 🤔
Added speculative loading support
@joemcgill mentioned that Speculative Loading was implemented yesterday and encouraged people to test the feature and provide feedback to help address any bugs before the major release. Further information on this can be found here: #62503
WordPress 6.8 Feedback
@jeffpaul asked if anyone sees an enhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. or other priority topic that requires attention before BetaBetaA 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.1 on March 4th, which is less than two weeks away.
Decision Needed on REST APIREST APIThe 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/ Template Exposition
@joemcgill mentioned that a decision is needed on how to resolve the issue in #62574 regarding where to expose default template types or template part areas in the REST API.
Editor Updates 🔄
In the future, the Editor Update News will be published separately as individual posts.
Let’s take a quick look at what has been happening with the Gutenberg Editor. See here.
Thank you @krupaly2k for the detailed listing and efforts based on the current development status.
Open Floor 💬
WordPress 6.8 | TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. update
@audrasjb shared updated stats for the upcoming WordPress Release 6.8 release with detailed information.
TicketticketCreated for both bug reports and feature development on the bug tracker. Status
On the 352 tickets in the milestone:
about 25 tickets have been moved to Future Release or 6.9 last week
175 tickets are closed as fixed (+15 compared to previous week)
177 tickets are still open (-24 compared to previous week)
Ticket Types
On the 352 tickets in the milestone:
191 are bugfixes (-3)
127 are enhancements (-5)
23 are blessed tasks (-1)
11 are feature requests (=)
Please note that 6.8 tries to limit the number of new features. As we are approaching Beta 1, we’re starting to puntpuntContributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) almost all tickets marked early, feature request and enhancement.
Misc infos:
We have 0 ‘high’ priority ticket (-1):
On the 177 open tickets, 6 have the ‘commit’ keyword (-3)
On the 177 open tickets, 6 have the ‘early’ keyword (-1)
To committers working on 6.8: feel free to commit any tickets that are ready to ship! Here’s the Trac report for those tickets.
For people working on early tickets, especially committers: please note that we’ve started moving some tickets to milestone 6.9 or Future Release. Here’s a useful Trac report.
The next scheduled scrub is tomorrow, February 20th, at 20:00 UTC.
WordPress 6.8 | Feature discussion
@krupajnanda is seeking clarification on whether the Zoom out to compose with patterns feature will be included in the WordPress 6.8 release and what its current status is.
Benjamin Zekavica is joining as a Core Team RepTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. for the first time, and along with Francesca Marano and Jean-Baptiste Audras. He aims to get up to speed, gain new experiences, and strengthen the Core Team together.
Forthcoming releases 🚀
New maintenance release: 6.7.2
The maintenance release WordPress 6.7.2 was officially released on February 11 and is now available for download. Thanks to everyone who contributed to this release and helped with testing at the release party!
Next major releasemajor releaseA 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.: 6.8
Next GutenbergGutenbergThe 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/ release: 20.3
Gutenberg 20.3 is due for release on February 19, 2025. For more insights into the latest version, here is a detailed overview of all the changes and new features in the Gutenberg release.
Discussion 🤔
Improving Unit Testunit testCode written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression.TicketticketCreated for both bug reports and feature development on the bug tracker. visibility
@desrosj shared a proposal to improve the visibility of unit test-related tickets. See more here: #7907. A new tests focus has been added in MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. to highlight tickets where tests need to be added or improved. @joemcgill clarified that this focus is specifically for tickets where new tests are being added or enhanced, not for tickets that already include tests as part of feature work.
@jorbin discussed that Task (blessed) tickets should only be handled by the release squad. If this is not the case, the categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. should likely be re-evaluated.
Open Floor 💬
WordPress 6.8 | TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. update
@audrasjb shared updated stats for the upcoming WordPress Release 6.8 release with detailed information.
Ticket Status
On the 361 tickets in the milestone:
160 tickets are closed as fixed
201 tickets are still open (14 of them were reopened for further fixes)
@audrasjb encourages committers involved in version 6.8 to commit tickets that are ready. A Trac report for commit-ready tickets has been shared. Starting tomorrow, tickets with the early keyword will be moved to milestone 6.9, and a Trac report for those tickets is also available. A milestone for WordPress 6.9 was created on February 11, during the latest accessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) scrub.
Gutenberg Packages update status
@joemcgill mentioned that the initial sync of Gutenberg (GB) packages was completed last week, allowing features to be tested directly in trunktrunkA directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. Ongoing syncs will continue after upcoming Gutenberg releases and as needed for bugbugA 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. fixes. There are several pending pull requests (PRs) to port PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher functionality to trunk, which still require review and merging. These PRs are tagged with the gutenberg-merge keyword in Trac. See #62887
Recommended PHP version information
@Mdxfr raised a question about the recommended PHP version for WordPress 6.8, particularly for performance and pluginPluginA 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/ or can be cost-based plugin from a third-party. compatibility. While WordPress is compatible with PHP 8.3, full compatibility is still being assessed. This will be discussed further in the next Dev Chat, where a Core Team representative will gather additional information from the Hosting Team.
Thanks to @francinafor helping review this summary.
This time, due to the smaller sizes of the releases, this post contains information for both the 20.1 (22 January) and 20.2 (5 February) releases.
“What’s new in GutenbergGutenbergThe 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/…” posts (labeled with the #gutenberg-new tag) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Editor.
Although both releases were smaller in size, they contain many useful enhancements, bugfixes and more. Apart from the highlighted changes, work continued on updating the blockBlockBlock 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. settings to use the ToolsPanel. Both updates ship with accessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) updates as well.
20.1 (22 January)
Content preview for pages in DataViews
Menu name shown in list view
Color pickers in Navigation, Social Icons and Post Featured ImageFeatured imageA featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. get Clear control
Changelog
20.2 (5 February)
Content block: color options for headings added
Changelog
20.1 (22 January)
Content preview for pages in DataViews
The DataViews got enhanced by a new preview functionality to show the page’s content instead of the featured image, similar to patterns and templates. You can activate this feature in the settings and switch between featured image and content preview. This setting persists across all three views, table, grid and list. (67278)
Menu name shown in list view
In the list view, the name of a menu is now shown instead of the block name “Navigation”. If the menu is changed, the name is updated as well. (68446)
Color pickers in Navigation, Social Icons and Post Featured Image get Clear control
Previously, color options at the Navigation, Social Icons and Post Featured Image blocks did not have a Clear control to easily remove the color. This applies to every color option on these blocks. (68454, 68564, 68525)
Other Notable Highlights
Enhancements
ESLint: Improve regex for valid-sprintf rule to handle ‘%%’. (68270)
Simplify sprintftranslationtranslationThe process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. for percentage widths. (68587)
Block Library
Archive Title Block: Refactor settings panel to use ToolsPanel. (67915)
Author Name: Refactor settings panel to use ToolsPanel. (67953)
Block Editor: Move state logic inside ‘BlockRenameModal’. (68560)
Editor: New default rendering mode for editor via post type supports. (68549)
Document Settings
Change “Swap” to “Replace” for Template Action. (68234)
DataViews
Add: Media field changing ui to Dataviews and content preview field to posts and pages. (67278)
Bug Fixes
CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Data: Check post-type support before requesting autosaves. (68680)
Fix text direction for URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org and email fields in block editor for RTL languages. (68188)
Navigation Link UIUIUser interface: Remove onClose from onSelectBlock. (67760)
Post Featured Image: Adds control to clear the the overlay color. (68525)
Site Logo: Prevent uploading multiple images via drag and drop. (68618)
Social Links: Don’t prepend URL fragments. (68655)
i18ni18nInternationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: Make example label for Comments Pagination Next block translatable. (68373)
i18n: Make example translatable in comments-pagination-previous. (68374)
Components
Duotone: Fix scrollbars displayed on Duotone Control. (67187)
Fix SCSS Media Query Compilation Issue in Storybook. (68464)
Restore Non-Themed Text Colors for optimizeReadabilityFor. (68472)
StoryBook: Fix error that could occur when loading compiled CSSCSSCascading Style Sheets.. (68526)
Site Editor
Classic theme preview: Remove adminadmin(and super admin)-bar class name. (68519)
Fix: Site Editor Template part is missing an icon in the sidebarSidebarA 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.. (68653)
Navigation: Fix typo in history.navigation's function call. (68623)
Block Editor
Differentiate ‘Copy’ and ‘Copy styles’ snackbar confirmation messages. (68167)
Refactor: Separate input form styles to a dedicated stylesheet. (68501)
Update percentage strings to be translatable. (66323)
Interactivity APIAPIAn 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.
iAPI: Fix the logic path that merges plain objects. (68579)
Accessibility
Nux: Standardize reduced motion handling using media queries. (68423)
Block Library
Fix Inconsistent Labels for Lightbox Feature. (68261)
Site Logo: Prevent focus loss when updating media from the sidebar. (68621)
Standardize reduced motion handling with media queries. (68315)
Components
Fix usage of tooltip in the Circular option picker. (68602)
Post Editor
Edit Post: Standardize reduced motion handling using media queries. (68426)
Widgets Editor
Customize Widgets: Standardize reduced motion handling using media queries. (68425)
Block Editor
Remove unnecessary CSS order property for the contrast checker in the Color hook. (68055)
[core-data] Document and add types for dynamic actions and selectors. (67668)
docs: Fix param name in gutenberg_add_can_update_block_bindings_editor_setting(). (68390)
docs: Fix return type on gutenberg_register_block_module_id(). (68393)
Block Library
Query LoopLoopThe Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop: Remove unused styles. (68615)
Site Logo: Remove unused argument for ‘mediaUpload’ function. (68617)
Global Styles
Remove unused prop for ‘BackgroundImageControls’. (68616)
Post Editor
Document Outline: Use block client ID as unique ‘key’. (68502)
Edit Widgets and Base Styles: Standardize reduced motion handling using media queries. (68427)
Components
Standardize reduced motion handling using media queries. (68421)
Block Directory
Standardize reduced motion handling using media queries #68419. (68420)
Site Editor
Edit Site: Add tsconfig.jsonJSONJSON, 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. validation for package. (67406)
PluginPluginA 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/ or can be cost-based plugin from a third-party.: Remove ESLint rule for deprecated functions. (68590)
First-time contributors
The following PRs were merged by first-time contributors:
@AhmarZaidi: Update percentage strings to be translatable. (66323)
Previously, it was only possible to change colors for text, background and link on the content block. With this update, the color of all headings and each individual heading level can be changed. (67783)
Other Notable Highlights
Enhancements
Block Library
Details block: Add name attribute for exclusive accordion. (56971)
Search Results Title Block: Add dropdown menu props to Tools Panel component. (68763)
Spacer: Add dropdown menu props to Tools Panel component. (68761)
Term List Block: Refactor settings panel to use ToolsPanel. (67955)
Design Tools
Position: Refactor “Position” controls panel to use ToolsPanel instead of PanelBody. (67967)
Post-content block headerHeaderThe 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. color support. (67783)
Navigation Submenu Block: Add example preview. (68378)
Bug Fixes
Fix: InvalidinvalidA 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._doing_it_wrong() for experimental-link-color. (68408)
Docs: Update links to HTTPSHTTPSHTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information.. (68888)
Lint: Fix broken URL reference for stylelint user guide configuration. (68706)
Used https in main-dashboard-button.md file. (68883)
wp-env: Add phpMyAdmin and multisitemultisiteUsed 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 support to the documentation. (68125)
Code Quality
Inline Commenting: Change the PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher compat directory. (68846)
Fix: Remove invalid param from wp_register_style() in gutenberg_enqueue_stored_styles(). (68409)
Fix: setcookie() $value must be string in Gutenberg_HTTP_Signaling_Server::Handle_read_pending_messages(). (68411)
Block Library
Gallery: Remove unused inline menu styles. (68776)
Move HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. element help messages to the block library utils. (68708)
Unify block title with a strict title case. (51912)
Video: Fix reactReactReact is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces.
https://reactjs.org component warning error. (68762)
Post Editor
Editor: Children prop to accept ReactNode. (68839)
Editor: Combine selectors in the ‘Header’ component. (68697)
Editor: Standardize reduced motion handling using media queries. (68424)
Components
Box Control: Add Runtime Check & Conditional Types for presets and presetKey Props. (68385)
Remove unnecessary Tooltip component from linked button. (68498)
Block Editor
Clean up unused utils of spacing size control. (68794)
Template Editor
Editor: Update post-type support key for new default rendering mode. (68745)
Tools
Build Tooling
Fix Duplicate Entries for 19.7.0 in changelog.txt. (68836)
E2E: Fix WP Editor MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Boxes test. (68872)
Next major releasemajor releaseA 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.: 6.8
Next GutenbergGutenbergThe 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/ release: 20.2
Gutenberg 20.2.0 was released on February 5. It included the following issues. For the last several releases, the “What’s new in Gutenberg” posts have been paused due to the team’s capacity. If anyone is interested in helping with these posts, please contact @mamaduka.
The PR is ready for another review. There is an issue causing the wp-polyfill script being bundled but is not a blockerblockerA bug which is so severe that it blocks a release. for the sync.
WordPress 6.8 Roadmap
@krupaly2k was still working on this with support from @jeffpaul and feedback from release squad members.
The Roadmap to 6.8 post was published following the meeting.
REST APIREST APIThe 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/ feedback needed
There was discussion about whether this should be fixed on the server side or in the client.
@jorbin suggested trying to get some tests written that show the bugbugA 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. in the server in order to help drive a fix.
@joemcgill said that fixing server side is a good idea, but if a client side fix could resolve a user issue then we should pursue that as well.
You must be logged in to post a comment.