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.
This is a security release that includes two fixes. We strongly recommend updating your sites immediately. For more details, you can find the information here.
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/ 21.7?
Gutenberg 21.7 is now available. The release post provides a full overview of the changes and enhancements.
Forthcoming releases 🚀
WordPress 6.9 Timeline
WordPress 6.9 is planned for December 2, 2025, with 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 beginning October 21.
The team discussed how editorial (pre-publishing) comments should appear in the adminadmin(and super admin). Ideas included labels in the posts list, filters for unresolved feedback, or views by post type. Concerns were raised about mixing these with public comments. Naming suggestions included “Editorial Comments,” “Notes,” or “Discussions.”
CSSCSSCascading Style Sheets. Class Names
PR #10043 proposes separating the handling of CSS class names from the class attribute. This would make iteration cleaner, avoid explode() logic, and handle duplicates or unusual spacing more reliably.
Refactor of wp_kses_hair()
TicketticketCreated for both bug reports and feature development on the bug tracker.#63724 explores normalizing attribute values (for example decoding entities) to better align with browsers and the HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. spec. This could simplify edge cases but may raise backward compatibility concerns.
wp_html_split()
PR #9270 aims to improve how shortcodes are parsed when $ignore_html = true. The discussion centered on whether CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. should follow the HTML spec or keep legacy behavior.
Template Output Buffering
Ticket #43258 (PR#8412) suggests adding a standardized output buffering layer in Core. This could unify caching and optimization flows and reduce 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 conflicts. The risk is considered low, though there are concerns about potential effects on TTFB and plugin behavior. Clear documentation and testing will be needed.
Open Floor 🎙️
@coryhughart raised the nesting and inheritance issue for the experimental Terms Query 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.. The proposed change introduces a fundamental shift in how the block handles queries, aligning it more closely with 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_Loop. while remaining extensibleExtensibleThis is the ability to add additional functionality to the code. Plugins extend the WordPress core software.. Feedback on the linked PR is encouraged.
