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.
It’s time to get WordPress 6.7 ready for release, and help is needed to ensure it’s smooth and 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.-free. Whether you’re an experienced contributor or joining in for the first time, everyone is welcome at our bug scrubs! 🎉
Schedule Overview
Regular bug scrubs are being held every week leading up to the WordPress 6.7 release, with some cases including two sessions a day to cover a broader time frame. As the release date approaches and activity ramps up, the number of scrubs may be increased if necessary. These efforts will help ensure everything is on track for a smooth launch. Participation is welcome at any of these sessions, so feel free to join. Bring questions, ideas, and let’s scrub some bugs together!
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 be 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.
WordPress 6.7BetaBetaA 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 next week, October 8
Priority Items
WordPress performance TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
Performance Lab 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 (and other performance plugins)
@joemcgill planning on punting #59600, because I don’t think we have any clear next steps to move that forward
Just want to review it an make sure there aren’t any follow-up items in that ticketticketCreated for both bug reports and feature development on the bug tracker. that need to be tended to first
I also noticed that there was an issue with the performance tests during the release party due to the inclusion of a new default theme. Curious if we already have a ticket to update this, or any next steps we need to do. @mukesh27 do you know?
@joemcgill will spin up a new ticket to conditionally test TT5 on WP versions that support that theme
@mukesh27 ran WP 6.7 Beta 1 Performance Benchmark Report – please seehttps://wordpress.slack.com/archives/C02KGN5K076/p1727785426773919 shows the 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 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. theme
Performance Lab Plugin (and other Performance Plugins)
@westonruter I submitted the initial version of Web Worker Offloading (powered by Partytown) to the plugin directory. This initial version integrates with WooCommerce’s integration with Google Analytics (integration²)
@adamsilverstein noticed a new comment in the INP opportunities doc (created in March) noting that Elementor has fixed one of the issues identified there. Their new release has the fix which loads CSSCSSCascading Style Sheets. more dynamically based on content.
Improving the calculation of image size attributes
@joemcgill For improving the calculation of image sizes attributes, we’ve been doing some experimentation with using block context to pass layout information from parent blocks to their ancestors and have noticed that #62046 is affecting our work. I’d like to see if we could get this solved for 6.7 so we don’t need to ship a workaround for this 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 our feature pluginFeature PluginA plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. implementation. @gziolo flagged this as too late for 6.7 on the ticket, but as a bug, I think it could still land during betas.
Further discussion on WP 6.7 performance benchmarks
@joemcgill regarding (Slack post) the performance metrics for classic themes looks pretty steady, which is great! For TT4, it seems like we need to investigate the cause of the additional performance regression during template rendering, because adding 10% is not great.
Can we spin up a tracking issue in our performance repo to collect each of these benchmarks during the release and have a place to discuss the potential causes/remediation efforts?
WordPress 6.7BetaBetaA 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 next week, October 8
Priority items
WordPress performance TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
Performance Lab 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 (and other performance plugins) including:
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
Additional items will be referred to in the various curated agenda sections, as below. If you have ticketticketCreated for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this agenda.
Announcements
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.
Next maintenance release
There are no maintenance releases planned at this time.
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.
Discussions
The discussion section of the agenda is to provide a place to discuss important topics affecting the upcoming release or larger initiatives that impact the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team.
If you want to nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.
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: not for 6.7 but work is underway to Open the stable editor APIs
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.:Expose “block hooks” at the section level
Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.
Please include details of tickets / PRs and the links in the comments, and if you intend to be available during the meeting for discussion or if you will be async.
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://2017.us.wordcamp.org/contributor-day/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 5.6.20 or higher to enable quick edit for custom fields. We’ll be talking more about it in the days ahead in #core-fields.
WordPress 6.7BetaBetaA 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 next week, October 1
Performance Lab release 3.4.1 was published yesterday
The WordPress Performance Team is looking for feedback to streamline the onboarding experience of the Performance Lab 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. We would appreciate it if would you took 5 minutes of your time to set up the plugin and share your feedback.
WordPress performance TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
To be discussed on tomorrow’s 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. scrub
Performance Lab Plugin (and other Performance Plugins)
Improving the calculation of image size attributes
No updates this week
Enable Client Side Modern Image Generation
@swissspidy I gave a talk about this last week at WCUS, which was a great success. Lots of positive feedback and interest in helping to contribute. Writing a blogblog(versus network, site) post now with details etc
@joemcgill Once this effort gets past the initial experiments phase, I think it would benefit from more people being able to support Pascal in implementing some of these ideas. What do you think?
@swissspidy Definitely 🙂 As soon as this is 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/, more eyes are definitely helpful. But even now it can’t hurt to at least test the existing plugin and provide feedback
Enhance Onboarding Experience of Performance Lab Plugin
“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 5.6.20 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_posts capabilities. (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.
WordPress 6.7BetaBetaA 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 next week, October 1
Performance Lab release 3.4.1 was published yesterday
Priority items
WordPress performance TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
Current release milestone report. There are currently 19 tickets unresolved
Future release
Performance Lab 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 (and other performance plugins) including:
You must be logged in to post a comment.