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.
These “CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement…” posts (labeled with the #core-editor-improvementtagtagA directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)) are a series dedicated to highlighting various new features, improvements, and more from Core Editor related projects.
Various improvements to font management, including managing font size presets and refinements to the Font Library experience, are coming to WordPress 6.7. Taken together, expect more control over your fonts and an easier time using them exactly as you want. Below is a video showcasing some of these new options and improvements:
Edit and apply font size presets
Create, edit, remove, and apply font size presets with a new addition to the Styles interface. You can now modify presets provided by a theme or create your own custom options. A key feature is the ability to toggle fluid typography, which enables responsive font scaling, with the option to set custom fluid values for finer control over responsiveness. Of note, individual font sizes may opt out of fluid typography if it is turned on globally and vice versa, ensuring more flexibility.
Alongside these overall improvements and new functionality, the Styles interface has been refined to make applying site-wide font changes more discoverable. Namely, the font presets, along with the color presets, are now available to select between from the Styles 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. under the “Browse styles” option. The Font Library is also better surfaced whether you’ve added fonts or not. The aim is to ensure high level font options are right where you want them with more advanced customization options available for anyone who wants to go a step further.
WordPress 6.7 Beta 1 was released on October 1. Thank you to everyone who contributed to this release and attended the release party! There is a helpful guide here on how to help test this release.
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.7
We are currently in the WordPress 6.7 release cycle. WordPress 6.7 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 is scheduled for Tuesday, October 8. For specific release times, review the release party schedule post.
@peterwilsoncc noted that the release is now in the phase of 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 only. No further enhancements or features can be committed to WordPress-Develop until the 6.7 branchbranchA directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". is forked in a few weeks time after RCrelease candidateOne 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). 1. Tasks can also be completed at this stage, such as the about page, etc.
@peterwilsoncc also mentioned that the Twenty Twenty-Five theme is still being worked on in the GitHubGitHubGitHub 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/ repository and he’s sure the theme team would love assistance there https://github.com/WordPress/twentytwentyfive/issues.
On the Editor side, @noisysocks suggested diving into fixing bugs that are in the 6.7 board if you’re interested in helping out.
Next maintenance release
There are no maintenance releases planned at this time. Currently, the next minor report is clear.
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: 19.4
The next Gutenberg release will be 19.4, scheduled for October 9, and will include the following issues.
Discussion
There were no discussion topics raised this week.
Open Floor
@akirk left a comment on the agenda asking whether the WordPress project wanted to be represented at FOSDEM 2025, happening in Brussels this coming Feb. To quote his comment on the agenda:
I believe bringing a dedicated WordPress room to this open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. conference could be beneficial for WordPress to connect more with other open source projects. We could select talks for the devroom (given that they’d be proposed) that can inspire and take inspiration from other open source projects, for example about WordPress Playground, or how the WordPress project does translationtranslationThe process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization..
Proposals need to be submitted by Oct 10. Alex is looking for feedback about whether it makes sense to engage in the FOSDEM environment and to gather interest in submitting talks if the room is accepted. Please reach out to @akirk directly if you’d like more information about this.
At WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US last week, CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers in attendance (including emeritus) gathered for a brief informal meeting.
There was no formal agenda, but a few goals for the meeting were mentioned at the beginning:
Allow newer committers to meet more senior ones.
Allow anyone to raise questions, concerns, or suggestions that have been on their minds.
Just spend some time together chatting and getting to know each other.
Below are some brief notes from discussions that happened following Chatham House Rule.
A group photo taken the day after the meeting. A few committers are missing that were present at the actual meeting. – Photo credit: @rzen with alternate angles form @afragen.
What is the right way to commit?
A newer committercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. mentioned that established committers have been very supportive and helpful getting them set up and comfortable. However, they often question whether they are doing things right. There is baseline documentation in the handbook around committing and some extensive documentation around commit messages, but every committer seems to have a different setup with a different tool set.
Some takeaways
There’s no wrong way to set up your environment or make commits.
To increase the amount of documentation around committing, every committer should blogblog(versus network, site) about their set up (and more about committing in general)! A new page has been created in the Core Handbook to serve as a blogroll for these posts and will be updated as new ones are published. Everyone is welcome to publish, including emeritus and committers who were not in attendance at WCUS.
Using the #core-committers channel for questions around committing process is always appropriate.
Clarity around requesting feedback
The next discussion was around how to properly seek feedback from other contributors and committers. The Make Core Blog has recently felt a bit too “official” for these more casual posts. But in the past, these types of posts were perfect for the Make Core blog. Is this no longer the place for these types of discussions?
The ideal purpose of Make Blogs was discussed a bit, and it was mentioned that there was a 2 partdiscussion at the 2023 Community Summit focused on this. It was suggested to read through the session notes to see if there were any mentions of this.
Some takeaways:
There’s value in posting on your own blog to validate your own ideas and understandings vs. speaking on behalf of WP to the community.
It’s OK to share posts on your blog seeking feedback as long as findings are summarized in the TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.ticketticketCreated for both bug reports and feature development on the bug tracker..
As long as it’s accompanied by a problem statement/theory/points needing validation, posting on the Make blog seeking feedback about that problem seems reasonable.
It’s always preferred to have a Trac ticket outlining the problem, even if it’s unclear whether it’s something that will actually be fixed (there’s always wontfix and maybelater).
Moving more “official” communication to the relatively new Developer blog makes sense. This would include the Field GuideField guideThe field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page., developer notes, etc.
No matter where these discussion points are shared, make sure to be clear about what type of feedback you are seeking.
Is this idea unrealistic?
Are there blockers that are not apparent?
Is there history behind why something is a certain way that is not immediately obvious?
There are no announcements this week. However, last week many from the community attended WordCamp US 2024 in Portland, OR. If you missed it, or just want to reminisce, several folks contributed to this PDX + WCUS 2024: A Recap post from the 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.7
We are currently in the WordPress 6.7 release cycle. WordPress 6.7 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 is one week away. The Road Map post can be found here.
@peterwilsoncc reminded that all enhancements need to be committed prior to the beta so folks wishing to get something in should do so sooner rather than later.
The final release of 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/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. for WP 6.7 has been released and the 6.7 branchbranchA directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". for the plugin created.
One of the bigger tasks is to get Twenty Twenty-Five committed, so the team working on that is pretty focused this week. It would be very valuable if people could take some time to test the theme and log any issues, create PRs (if able to), etc. To do so, visit https://github.com/WordPress/twentytwentyfive. There are instructions in the repo explaining how to set it up and get it running.
Next maintenance release
There are no maintenance releases planned at this time.
Next Gutenberg release: 19.3
The next Gutenberg release will be 19.3, scheduled for September 25, and will include the following issues.
Discussion
There were no discussion topics raised this week.
Open Floor
Cory Hughart shared that during contributor dayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ at WCUS, the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Fields table spent the day diving through bleeding-edge Gutenberg code related to the new DataViews in posts and pages areas of the site editor. @sc0ttkclark is working on a dev blogblog(versus network, site) post, but the TL;DR is that we want to add some options to register_meta functions in PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher to enable quick edit for custom fields. We’ll be talking more about it in the days ahead in #core-fields.
“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.
A total of 174 PRs were merged in Gutenberg 19.3, with 7 first-time contributors! With WordPress 6.7 rapidly approaching, many contributors are focusing on 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. However, this release still includes some great features and enhancements, including stabilizing the Zoom Out mode!
The Zoom Out Mode is officially out of the experiment and is available to all users. This new mode allows users to zoom out to edit and create at the pattern level over granular 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. editing. This effort aims to provide a new, high-level approach to building and interacting with your site. Follow the 6.7 iteration issue for more information.
Swap the position of the publish buttons
A nice user experience improvement to swap the “Cancel” and the “Publish” buttons in the pre-publish check panel. Now, users don’t have to move their cursor unnecessarily when publishing. (#65317)
Use custom block names in inspector controls
Uses the custom name for a block in the block inspector controls when available. (#65398)
Allow opting out of the “Choose a pattern” modal when adding new pages
The “Choose a pattern” modal can be distracting for power users who always want to start with a blank page. A new preference toggle disables the modal when adding new pages. (#65026)
Automatic phone number linking
The link field can now be automatically populated with tel: when the selected text is a phone number. (#64865)
Allow dropping multiple images to the image block
Multiple images can now be dropped on an image block, converting it to a gallery block. In addition, dropping multiple file types will each create an appropriate block. (#65030, #65144)
Create Block: Update the minimum required PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher version to 7.2. (65166)
Media Utils: Add TypeScript support and export more utils. (64784)
Media placeholders: Add “drag” to the text. (65149)
Restore: Move to trashTrashTrash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days. button in Document settings. (65087)
Inspector Controls: Use custom block name in inspector controls when available. (65398)
Navigator Screen: Warn if path doesn’t follow a URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org-like scheme. (65231)
Terms List block: Add Categories-specific variation. (65434)
Zoom Out
Add Zoom Out toggle to editor 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. when experiment enabled. (65183)
Add prompt for drag and drop in Patterns tab in Zoom Out mode. (65115)
Close inserter on exiting Zoom Out to edit. (65194)
Use post 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. label from register_meta in block bindings workflows. (65099)
Global Styles
Refactor site background controls and move site global styles into Background group. (65304)
Spacing control: Replace sides dropdwon with link button. (65193)
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.
Update: Rephrase “Force page reload” and move to Advanced. (65081)
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/
Global Styles: Allow read access to users with edit_postscapabilitiescapabilityA capability is permission to perform one or more types of task. Checking if a user has a capability is performed by the current_user_can function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability).. (65071)
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 / Post template: Enable post format filterFilterFilters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.. (64167)
Inserter: Fix loading indicator for reusable blocks. (64839)
Normalize spacing in Layout hook controls. (65132)
Pattern Inserter: Fix pattern list overflow. (65192)
Remove reset styles RTL from the 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.. (65150)
Revert “Block Insertion: Clear the insertion point when selecting a different block or clearing block selection (#64048)” (65208)
Components
BoxControl: Unify input filed width whether linked or not. (65348)
Remove zoom out toggle when editor is not iframed. (65452)
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)
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 script-module. (65101)
Interactivity API: Use a11y Script Module in Gutenberg. (65123)
Script Modules API: Print script module live regions HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. in page HTML. (65380)
Form Input: Don’t use flex-direction: Row-reverse for checkbox field. (64232)
Navigation Menus: Remove Warning and add notice for Navigation. (63921)
Global Styles: Fix the shadows Range control accessibility and usability. (63908)
Block Editor: Fix accessibility of the hooked blocks toggles. (63133)
Post Editor
Support keyboard resizing of meta boxes pane. (65325)
Swap position of the Pre-publish checks buttons. (65317)
Performance
CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Data: Batch remaining actions in resolvers. (65176)
Block Editor: Use static access for selector in ‘useZoomOutModeExit’. (65337)
Editor: Optimize global styles permission check. (65177)
Experiments
Block bindings REST API: Bring bindings UIUIUser interface in Site Editor. (64072)
Documentation
Add JSDoc block for getSectionRootClientId in block editor package. (65219)
ButtonGroup: Fix story to show what the component does. (65336)
Editor: Use 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. instead of HoC in BlockManager. (65349)
Data Views Fields: Migrate store and actions from editor package to fields package. (65261)
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 ‘function_exists’ checks for methods with ‘gutenberg’ prefix. (65260)
Global Styles: Update REST controller override method and backportbackportA port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. changes from Core. (65259)
Patterns: Remove unused method returned from ‘mapSelect’. (65073)
Embed: Convert EmbedPreview component to functional component. (51325)
Components
BoxControl: Fix critical error when null value is passed. (65287)
The purpose of this meeting is to discuss and collaborate on the development of the Twenty Twenty-Five theme. This meeting is held in the #core-themes channel in Making WordPress SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
Topics
Status update
Priorities
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
Open Floor
If you have anything you would like to add to the agenda, please add a comment.
Thanks to @juanfra and @joen for reviewing the agenda.
This post offers a proposal to create a private slackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ channel (#performance-hosting) where members of both the Performance Team and relevant representatives from hosting companies can come together to share information impacting the performance of sites, test relevant PRs, and have a quick feedback 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 for any performance regressions in new releases. This builds on the current private #security-hosting channel that’s already in place and has proven to be an area of collaboration.
Background
In talking to folks last week at WCUS alongside @harishanker, it became clear that in some cases hosting companies would benefit from a more curated and focused space for contribution that aligns with areas where they can make the biggest impact. In talking with folks, the following areas came to mind: performance, infrastructure, support, and security. This was a repeated topic in all conversations and, in these conversations, the #security-hosting channel came up as an already functional pathway.
Format
Create a new private slack channel for #performance-hosting that includes members from the Performance team for monitoring and engagement alongside relevant members from hosting companies. This is private in order to allow for more sharing and it’s centered around performance in order to provide a curated path for contribution, bringing in folks from the Performance team to engage directly.
What will this group work on?
Below are some of the ideas that were shared in the conversations. See these are starting ideas and not entirely encompassing:
Share anonymized data around plugins that are impacting sites the most in order to do outreach to them with performance suggestions, see what we can learn from them to improve CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., and update the plugin checker for anything that might be missing to help future contributors.
Share common user configuration to provide better tests for real world performance situations, rather than solely relying on lab metrics.
Test performance PRs early.
Create a tight feedback loop after releases for any performance degradations.
Why performance?
It’s clear there are a specific areas that hosts are best equipped to make the biggest impact and contribution, including performance. At the same time, the Performance team is a strong team with a clear roadmap, sponsored contributors, and a dedicated space already. In my time in the FSE Outreach Program, I found out how critical it is to create a space that’s managed, maintained, and specific. This checked all the boxes and I anticipate there will be more areas that will, like Support.
Why a private channel?
In talking to folks, a private channel came up as a safer space to share information. I am not personally opposed to a public channel but I want to recognize the reality that for folks in the hosting space, it felt advantageous to have private.
What do you all think? Please share by October 9th, 2024.
Please share your thoughts below. While there was an appetite for this idea when talking to folks in person, I want to know what blockers there might be and whether there are reasons not to pursue this, especially from the Performance team who will be impacted by this.
These “CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement…” posts (labeled with the #core-editor-improvementtagtagA directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)) are a series dedicated to highlighting various new features, improvements, and more from Core Editor related projects.
In the spirit of Matt’s “simple things should be easy and intuitive, and complex things possible”, the 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_LoopblockBlockBlock 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. has been refreshed with a focus on ensuring the most intuitive default state possible out of the box and increased clarity when trying to achieve anything more complex with custom queries. All of what’s shared below is slated for inclusion in the upcoming WordPress 6.7 release on November 12th, 2024.
Strong defaults
With recent updates, you no longer need to manually enable “Inherit query from template.” The Query Loop block now automatically inherits the query by default, ensuring expected posts are displayed both in the editor and on the front end. This change simplifies the process for most users, who typically just want to see their posts appear without complications. It also minimizes the likelihood of confusion, such as when a Query Loop block is added but posts don’t show up. Now, whenever you add a Query Loop block—whether starting from scratch or using a pattern—your posts will display immediately. This includes when adding a Query loop block to single post or page where the settings will automatically be configured to work in that context. Additionally, the Post List variation has been removed from the Inserter, as its default settings often caused posts to not display, leading to a confusing user experience.
To make this complex block more user-friendly and predictable, the settings have been simplified. Now, there’s a toggle to choose between using the default options or creating a custom query. If you select a custom query, another toggle lets you choose between posts or pages, with the usual filtering options. For custom post types, this section becomes a dropdown for easier selection. In response to feedback about scattered settings for the Query Loop block, options for Posts Per Page, Offset, and Max Pages to Show have been moved to the Settings panel. This change makes the settings 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. the central place to configure the Query Loop block fully.
The details matter, and these refinements are no exception: a preview now appears when selecting the Query Loop block, and the “Add a new post” prompt now reflects the specific type of content you’re querying. The help text for sticky posts has been updated to clarify that sticky posts will always appear first. Additionally, the enhanced pagination setting has been moved to the Advanced section with a new label for better clarity.
To help take steps towards post formats in Block themes, the Query Loop block has a new parameter called “format” that allows you to filterFilterFilters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. the content shown by post format, in the same way you’d filter by any other option. This additional filter can be combined with others so you can create custom queries for something as nuanced as posts by a specific author across two categories and with a certain post format.
In the Figma file you can see what is completed by looking for a green circle. Designs in progress have a yellow circle, and anything that is blocked or not planned at this time, is labeled with a red circle.
Work on the style variations. There’s an open issue to address these.
Work on items that are set to [Priority] High.
Once we finish adding the remaining 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. patterns and templates, we’ll start adding issues and instructions on how to proceed with 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. (making strings translatable, etc.), indentation, and polishing the patterns/templates.
Open floor
@erichmond brought up that it is difficult to pick issues to work on, and that even if a contributor is assigned to an issue, there may be duplicate pull requests submitted.
The intention is to follow the assignment to the person who has shown interest in the issue first. A recommendation would be to see if there are pull requests open before starting to work on a given issue.
@luminuu Asked if it would be a good idea to test the theme during the WCUS contributor dayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ on Tuesday the 17th of September, and if anyone would be available online during the start of the contributor day.
It is difficult to predict what kind of issues that may be open in the repository on the 17th and if they are suitable to work on during a contributor day. A new label in the repository can help contributor day attendees to select issues to work on.
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.7
We are currently in the WordPress 6.7 release cycle. WordPress 6.7 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 is scheduled for Tuesday, October 1. The Road Map post can be found here.
Next minor releaseMinor ReleaseA 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.: 6.6.3
Following the recent WordPress 6.6.2 release, the next maintenance release (if needed) will be WordPress 6.6.3. There were not updates shared in the meeting.
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: 19.2
The next Gutenberg release will be 19.2, scheduled for September 11 (this release occurred after the meeting).
Discussion
@peterwilsoncc requested that we discuss 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. Bindings UIUIUser interface feature, TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.ticketticketCreated for both bug reports and feature development on the bug tracker.#61945.
To summarize his concern:
My main concern here is that the approach is to hide the UI from users with low permissions. I don’t feel that this is a great approach to handling a UI that is considered too technical, as I don’t think there is anything to suggest that an administrator will understand what an author does not.
So I’m of the view the interface ought to be improved and made less technical before it’s shipped in coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress..
@noisysocks suggested waiting on an update from Mario Santos, who is working on the feature, but added:
I’d be fine with just updating this to use caps. The interface doesn’t strike me as being too technical. Can put it in the Advanced tab if we’re worried…
…The short of it is that I’m okay with fixing the cap issue (add a new cap, don’t check against a role) and shipping in 6.7 or leaving it in the 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. for more testing. Up to the team working on it. We have until beta 1 to decide.
@joemcgill highlighted two additional Slack updates this week:
I’ve addressed the feedback by adding a deprecation notice to the pattern rather than removing it. I’d appreciate any thoughts on if this feels like a better approach.
@joemcgill pointed out #62004. @jrf recently asked all committers to review in full here. Julia shared the following updates during the meeting:
Ticket #53010 is basically the first step: splitting up the huge test classes to smaller classes which each only test one thing, i.e. one global function, one method in a class etc.
This includes making sure that the new test files comply with the PHPUnit naming conventions.
There are a number of patches attached to the ticket which can be used to see how to do this (mind: not all have been reviewed yet for the latest info).
I also think it would be great if we could get a decision on yes/no namespacing the test classes. I believe we should and that now is the time.
And followed up with
The other thing which would really really help, is to make sure that any new tests go in “clean”. As in: comply with the requirements for newer PHPUnit versions. The task is large enough as it is without having to clean up after new commits.
You must be logged in to post a comment.