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.
WordPress 6.9 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. 4 is ready for download and testing!
This version of the WordPress software is still under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended to test Beta 4 on a test server and site.
WordPress 6.9 Beta 4 can be tested using any of the following methods:
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
Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edgebleeding edgeThe latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/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). Only” stream.)
The scheduled final release date for WordPress 6.9 is still December 2, 2025. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Thank you to everyone who helps with testing!
The 6.9 Release Candidaterelease 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). is still scheduled for Tuesday, November 11th, and the final release on December 2nd is still on track. As always, a successful release depends on your confirmation during testing. So please download and test!
How to test this release
Your help testing the WordPress 6.9 Beta 4 version is key to ensuring that the final release is the best it can be. While testing the upgrade process is essential, trying out new features is equally as important. This detailed guide will walk you through testing features in WordPress 6.9.
If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible 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. report. You can also check your issue against a list of known bugs.
After last year’s update, this post seeks to summarize what’s been completed, what’s in progress, and how to follow along or contribute. This post also seeks to set expectations going forward and answer reoccurring questions at a high level. As a reminder Phase 3 is centered around fostering seamless collaboration, tying together the user experience, and streamlining the content management flows to improve the way creators and teams work together within WordPress. As work progresses, feedback is needed and welcomed to ensure broader adoption.
A design concept for real time collaboration with notes.
Real-time collaboration
Work is underway to expand the collaborative editing experiment, with the latest update highlighting key areas in progress:
Performant and stable synchronization.
Protections to make sure that the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.-data package retains control over which entity records are synced and how changes are merged.
A 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. to give plugins the ability to extend a SyncProvider class. This allows plugins to provide their own sync transports and to implement user-facing sync behaviors such as awareness / presence indicators.
Stubs (lightweight placeholder records) that allow CRDT docs to be persisted 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., avoiding the “initialization problem” as described by Kevin Jahns.
A Yjs-powered UndoManager that works across multiple synced entities.
WordPress VIP has developed a working implementation demonstrating these capabilitiescapabilityA 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)., and various contributors are working to bring functionality into Core via 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/. All of this work is being done to pave the way for possible inclusion in WordPress 7.0. For now, if you want to help test and give feedback, you can do so by using the latest 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 and enabling the “Collaboration: add real-time editing” experiment in Gutenberg > Experiments. Keep in mind that a PR is not yet merged to remove the post lock modal but, until it is, you can still test having two sessions and see changes behind the modal itself.
Formerly known as 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. Comments, the Notes feature is set to debut in WordPress 6.9, bringing block-level Notes to Core after first appearing in the Gutenberg plugin as an experimental feature in October of last year. With this initial release, you’ll be able to add/resolve/delete/thread notes on entire blocks but not yet on specific elements within a block. The name Notes was chosen to clearly distinguish it from WordPress’s existing comment functionality, making it easier to discuss and document the feature moving forward. It also provides flexibility for future expansions beyond block-level notes, without needing another rename. This was truly a collaborative effort to land this feature with various folks from across the community coming together from Fueled, Multidots, Automattic, GoDaddy, and Human Made contributing as well as individuals like Adam Silverstein and Aki Hamano.
Feedback as the feature lands in Core will help shape what’s next here so please help test and open issues. For now, initial future plans include compatibility with real time collaboration, the ability to leave notes on individual items within a block rather than just at the block level, and built-in notifications.
Adminadmin(and super admin) redesign: DataView & DataForm
Early exploration centers on defining foundational primitives with DataView and DataForm components, building blocks that separate structure from presentation to support broad reusability across admin surfaces. Work has continued on both of these components to make them strong foundations that can handle more use cases with 154 commits done by ~37 different authors just for this latest release. For WordPress 6.9, this includes access to new field types, expanded filtering options, grouping support, views persistence, and improved configuration for custom dashboards and workflows. As a reminder, both of these components have been created with extensibility at the heart of everything being built. You can view each in their respective Storybook views: DataViews and DataForm. You can also read a more granular overview of what’s landed in this iteration issue for 6.9.
For now, if you want to help test and give feedback, you can do so by using the existing Pages, Templates, and Patterns screens in the Site Editor. For some of the more experimental aspects, you can help test by using the latest Gutenberg plugin and enabling from the Gutenberg > Experiments page the following different experiments:
Data Views: add Quick Edit – this adds a Quick Edit panel in the Site Editor Pages experience.
Data Views: enable for Posts – this adds a redesigned Posts dashboard accessible through a submenu item in the Gutenberg plugin so you can still have access to your current Posts experience.
Below is a demo of this last experiment that enables Data Views for Posts. It also showcases a feature of WordPress 6.9 with data views options now persisting across sessions, until you hit reset view.
WordPress 6.9 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. 3 is now available!
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/ 22.0 has been released!
WordPress 6.9 is planned for December 2, 2025. Release Candidaterelease 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 is planned for November 11.
The Test Team invites testing and feedback on the following upcoming 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 features:
“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.
Typically, the Gutenberg release following a WordPress point 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. focuses on coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. quality 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. fixes over new enhancements. As such, this will be a relatively quiet release.
Real-time Collaboration: 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. Synchronization
This release introduces real-time synchronization for post meta, enhancing the collaborative editing experience with your custom post-meta or footnotes!
An example of synced footnotes.
A new theme package
A new package of design tokens, which will be the new foundation for Gutenberg’s design system, is now available. This package is also a prerequisite for the new UIUIUser interface components package.
Template activation: Update 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. icons. (72772)
Try using DataViewsPicker in an updated media modal. (71944)
Update: Label of “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.” action to “Trash”. (72596)
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. Library
Math Block: Use monospaced font for LaTeX input. (72557)
Add snackbar notices for page creation in Navigation block. (72627)
Core Data: Avoid extraneous when creating a new record. (72666)
Fix build command for tokens package on Windows. (72605)
Global Styles: Fix the save panel changes. (72701)
Packages: Do not limit the exports of the template packages. (72694)
PluginSidebar: Fix auto more menu item props. (72630)
Template activation: Fix isActive and isCustom values. (72641)
Template activation: Fix undefined array key PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher warning. (72729)
Use default popover placement for image format popover. (72550)
Collaboration
Block Notes: Fix issue where box shadow is cut off when active note is the last one. (72606)
Ensure “Add Note” component floats next to block in unpinned mode. (72494)
Notes: Always open histroy sidebar if note is resolved. (72708)
Notes: Disable floating notes for ‘template-locked’ mode. (72646)
Notes: Fix ‘View notes’ on mobile screens. (72546)
Notes: Prevent 403 error for low capabilitycapabilityA 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). users. (72767)
Fix empty URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org value from unbinding entity from inspector sidebar. (72447)
Fix: Force LTR direction in Math block textarea for RTL languages. (72684)
Image block: Add guard for null refs in setButtonStyles callback. (72715)
Post Date: Fix variations for 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.. (72617)
Terms Query: Show nested terms toggle when inheriting. (72510)
Update: Disable font size when fit text is enabled and the opposite. (72533)
Templates 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.
Template activation: Allow duplicates of ‘custom’ 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 templates to be activated. (72713)
Template activation: Remove the ability to deactivate registered templates. (72636)
Templates: Adds ‘type’ property to activeField as boolean in page templates. (72648)
Command Palette
Disable site editor navigation commands on Networknetwork(versus site, blog)Adminadmin(and super admin) – Take 2. (72698)
Disable site editor navigation commands on Network Admin. (72572)
Interactivity API
iAPI: Fix derived state closures processing on client-side navigation. (72725)
Write mode
Accordion: Dont’ show Add button in contentOnly mode. (72704)
Add bindableAttributes in preview context. (72625)
Typography
Fit text: Remove sizing limitation when the block is selected. (72570)
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/.
Notes: Fix ‘children’ embedding via REST API. (72561)
Style Book
Fix error with display of Heading block style variations in style book. (72551)
Fix contentOnly insertion, removal, and moving. (72416)
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)
Notes: Don’t collapse note on Escape if the event has been prevented. (72657)
Block Library
Fix focus loss from unsync and edit button in navigation link inspector sidebar. (72436)
Move 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. to 7.0 because it was punted to future release. (72472)
add: Missing 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. Schema for blocks. (72590)
Post Date: Update logic when to show the edit control. (72631)
Remove broken content only settings menu items feature. (72470)
Templates API
Template activation: Initialise old autosave and revisionsRevisionsThe WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. endpoints. (72680)
Build: Fix script_debug modules and scripts. (72485)
Build: Generate plugin version and make the build script plugin agnostic. (72707)
Build: Move the build tool to a dedicated package. (72743)
Build: Support third-party plugin scripts properly. (72760)
Build: Update output folders for scripts and modules. (72482)
Enqueue non-minified JSJSJavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. files when SCRIPT_DEBUG is enabled. (72480)
FIX PHPUnit failure in previous WordPress version. (72705)
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/ Actions: Allow writing PRs when auto-cherry-picking. (72573)
Persist credentials when cherry-picking commits to a release 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".. (72556)
Change bin script type-checking from inclusion to exclusion. (72675)
Improve output buffer for sending server-timing 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.. (72536)
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
The various curated agenda sections below refer to additional items. If you have ticketticketCreated for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.
Announcements 📢
WordPress 6.9 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. 3 is now available!
WordPress 6.9 is planned for December 2, 2025. Release Candidaterelease 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 is planned for November 11.
Call for Testing
The Test Team invites testing and feedback on the following upcoming 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 features:
The discussion section of the agenda is for discussing 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. 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.
Upload error handling for themes and plugins
@nimeshatxecurify requested feedback on #29798 and #44042. The PR adds clearer messages when a 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 ZIP is uploaded via the theme uploader (and vice versa). Feedback on the approach is welcome.
No further topics have been submitted for this discussion round yet. If you have something in mind, feel free to leave a comment below this post.
Open floor 🎙️
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 indicate whether you intend to be available during the meeting for discussion or will be async.
WordPress 6.9 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 now available!
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/ 21.9 has been released!
Gutenberg 21.9 has been released and is available for download! This release brings new blocks and polishes existing ones, plus new DataViews enhancements and many bugfixes. Thanks to @priethor for writing this wonderful overview.
Forthcoming releases 🚀
WordPress 6.9 Timeline
WordPress 6.9 is planned for December 2, 2025. Beta 3 is planned for November 4.
The Test Team invites testing and feedback on the following upcoming 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 features:
Notes UIUIUser interface: Long threads in floating mode
@adamsilverstein asked for feedback on handling long note threads in floating mode (#72507). Two approaches have been tested so far: making threads scrollable and ensuring the active note is not cut off. The goal is to find a solution without full-document scrolling. Feedback is welcome.
Ensures bottom of active floating note is never cut off at bottom (PR#72454)
Call for Testing – Notes
@jeffpaul noted that a Call-for-Testing post for the Notes feature is planned. Contributors interested in assisting with drafting or reviewing are invited to reach out to him directly.
“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-newtagtagA 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 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.
This release brings new blocks and polishes existing ones, plus new DataViews enhancements and many bugfixes.
All the blocks!
Gutenberg 21.9 ships with a handful of new tricks and treats in the form of blocks 🎃 . For starters, the Math 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. will allow you to add complex LaTeX formulas natively in the editor.
Whether math is your cup of tea or not, the new Breadcrumbs block has your back and will for sure become very handy in sites with nested pages.
Similarly convenient for sites rich in content, this release also introduces the new Term Count and Term Name blocks – simple yet effective for helping navigate your tagged content!
Finally, the accordion block now supports anchors and is ready to ship with WordPress 6.9, too.
Direct drag and drop
Rearranging blocks is a common action when organizing your site, and drag & drop is a very comfortable way to do so. This release improves this interaction by directly moving the block around when you drag, instead of showing a drag chip.
DataViews customization persistence
A long-standing user request, views powered by DataViews now support persistence. This means that when you customize the view settings on the patterns, templates, and pages screens within the site editor, your preferences will persist when you leave the screens and return, reverting only to defaults when you hit the “Reset view” button.
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
The various curated agenda sections below refer to additional items. If you have ticketticketCreated for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.
Forthcoming releases 🚀
Call for Testing
The Test Team invites testing and feedback on the following upcoming 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 features:
The discussion section of the agenda is for discussing 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. 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.
Coding Standard Proposal: Make it explicit that PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher files must use the .php extension
The current WordPress coding standardsWordPress Coding StandardsThe Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook.
May also refer to The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the PHP coding standards. do not define which file extension should be used for PHP files. This proposal recommends standardizing on the .php extension exclusively. @rodrigosprimo has published a detailed post outlining the rationale.
No further topics have been submitted for this discussion round yet. If you have something in mind, feel free to leave a comment below this post.
Open floor 🎙️
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 indicate whether you intend to be available during the meeting for discussion or will be async.
You must be logged in to post a comment.