All Activity

WordPress 7.0 Beta 5 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 5 on a test server and site.WordPress 7.0 Beta 5 can be tested using any of the following methods: PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the Beta 5 version (zip) and install it on a WordPress website.Command LineUse this WP-CLI command: wp core update --version=7.0-beta5WordPress PlaygroundUse the WordPress Playground instance to test the software directly in your browser. No setup is required – just click and go! The scheduled final release date for WordPress 7.0 is still April 9, 2026. 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! Please continue checking the Make WordPress Core blog for 7.0-related posts in the coming weeks for more information. What’s new in WordPress 7.0? Check out the Beta 1, Beta 2, and Beta 3 announcements for details and highlights. How to test this release Your help testing the WordPress 7.0 Beta 5 version is key to ensuring everything in the release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 7.0. 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 bug report. You can also check your issue against a list of known bugs.Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack. Beta 5 updates and highlights WordPress 7.0 Beta 5 contains more than 101 updates and fixes since the Beta 3 release. Each beta cycle focuses on bug fixes, and more are on the way with your help through testing. You can browse the technical details for all issues addressed since Beta 3 using these links: GitHub commits since March 5, 2026 Closed Trac tickets since March 5, 2026 Issues addressed since Beta 4: GitHub commits since March 10, 2026 Closed Trac tickets since March 10, 2026 WordPress 7.0 Beta 5 contains a new feature! Instantly access all the tools you need with a single click using the new Command Palette shortcut in the Omnibar! In 7.0 Beta 5, logged-in editors will see a field with a ⌘K or Ctrl+K symbol in the upper admin bar that unfurls the command palette when clicked. The new command palette entry point streamlines navigation and customization, giving you full control from anywhere on your site – whether you’re editing, designing or just browsing plugins. A Beta 5 haiku A smooth melody Beta 5 plays on its strings. Seven brings good things. Props to @amykamala, @annezazu and @4thhubbard for proofreading and review. View the full article

WordPress 6.9.4 is now available! WordPress 6.9.2 and WordPress 6.9.3 were released yesterday, addressing 10 security issues and a bug that affected template file loading on a limited number of sites. The WordPress Security Team has discovered that not all of the security fixes were fully applied, therefore 6.9.4 has been released containing the necessary additional fixes. Because this is a security release, it is recommended that you update your sites immediately. You can download WordPress 6.9.4 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin automatically. For more information on WordPress 6.9.4, please visit the version page on the HelpHub site. Security updates included in this release The security team would like to thank the contributors who reported and investigated this issue, in particular Thomas Kräftner for his responsible disclosure. The security issues that are resolved in 6.9.4 are: A PclZip path traversal issue reported independently by Francesco Carlucci and kaminuma An authorization bypass on the Notes feature reported by kaminuma An XXE in the external getID3 library reported by Youssef Achtatal View the full article

For nearly two decades, WordPress has been known for a simple, powerful idea: that anyone should be able to get online and start creating with minimal friction. The famous five-minute install captured that spirit for an earlier era of the web. Today, we’re introducing my.WordPress.net, a new take on that idea designed for a new generation of creators. With my.WordPress.net, WordPress runs entirely and persistently in your browser. There’s no sign-up, no hosting plan, and no domain decision standing between you and getting started. Built on WordPress Playground, my.WordPress.net takes the same technology that powers instant WordPress demos and turns it into something permanent and personal. This isn’t a temporary environment meant to be discarded. It’s a WordPress that stays with you. New Ways to WordPress When you open my.WordPress.net, you’re placed directly into a complete WordPress environment that runs entirely in your browser. What makes this approach meaningful is not just where WordPress runs, but how it changes the relationship between people and the software itself. By removing the need to sign up or make early decisions about hosting and visibility, my.WordPress.net reframes WordPress as a space you can enter and work within, rather than a service you have to configure before you begin. “This takes WordPress from being framed as something that is democratizing publishing to democratizing digital sovereignty.” – Alex Kirk Seen through that lens, my.WordPress.net is not just about convenience. As you don’t need to choose a hosting provider, your WordPress belongs entirely to you. In a publishing environment, you’d briefly interact with WordPress as you prepare your next post. In a personal setting, it becomes a place you shape and return to. That change unlocks new ways of thinking about what WordPress can be. Permanently and Privately Yours Because sites on my.WordPress.net are private by default and not accessible from the public internet, they don’t behave like traditional websites. They aren’t optimized for traffic, discovery, or presentation, and they don’t need to be. Instead, WordPress becomes a personal environment where ideas can exist before they are ready to be shared, or where they may never be shared at all. This changes how WordPress can be used day to day. It becomes a place to think, to draft, to organize, and to experiment without pressure, whether that means writing privately, collecting research, or building small tools for personal use. Learning also fits naturally into this model, since people can explore plugins, themes, and features inside a real WordPress environment where mistakes are expected and recoverable. This turns WordPress into a personal workspace. It becomes a place for thinking, learning, prototyping, and tinkering, where exploration matters more than outcomes. In that role, WordPress shifts from being something you prepare for others to visit into something you actively work inside, adapting to how you want to create and learn over time. Sparking Creativity with Apps To make these ideas concrete, my.WordPress.net includes an App Catalog with pre-configured experiences designed specifically for personal use, built with WordPress plugins. These examples highlight how WordPress can function when it’s private, persistent, and easy to experiment with. Each app installs with a single click and configures itself automatically. Personal CRM A private relationship manager designed to help you stay in touch with people who matter to you. Contacts can be grouped, enriched with personal details, and paired with reminders to reconnect. In the demo, this extends to analyzing communication patterns using imported chat data, all stored locally inside WordPress. Personal RSS Reader Using the Friends plugin, WordPress becomes a quiet, personal feed reader. Instead of relying on external platforms, you can follow sites and creators inside your own WordPress and read at your own pace, free from algorithms or engagement pressure. AI Workspace and Knowledge Base Because my.WordPress.net is powered by WordPress Playground, an AI assistant can safely modify it, empowering you to customize beyond what you’re used to. Ask it to modify a plugin to your liking, or create an entirely new one, featuring your desired block. Ask it about the data you have stored in your WordPress. The assistant remembers what it touches and makes it easy to share your changes with others. Over time, WordPress itself can become your personal knowledge base that the AI understands and works with. Zero Barriers my.WordPress.net lowers the barrier to getting started with WordPress to almost nothing. It offers a fast, commitment-free way to explore, learn, and build, whether the result is a long-term personal project or something that eventually moves elsewhere. In that sense, it updates the spirit of the five-minute install for a browser-first web. What you should know Storage starts at roughly 100 MB The first launch takes a little longer while WordPress downloads and initializes All data stays in your browser and is not uploaded anywhere Each device has its own separate installation Backups should be downloaded regularly Create and explore WordPress has always grown through experimentation. People trying things, breaking things, and discovering new ways to use the platform have shaped what WordPress is today. my.WordPress.net continues that tradition by making experimentation easier and more personal. It’s an invitation to create without pressure, to explore ideas that may never be published, and to use WordPress in ways that fit your life. Start exploring at my.WordPress.net my.WordPress.net is built on WordPress Playground technology. Learn more at WordPress.org/playground or join the conversation in the #meta-playground channel on WordPress Slack. View the full article

WordPress 6.9.2 was released earlier today and addressed 10 security issues. A few users have subsequently reported an issue where the front end of their site was appearing blank after updating to 6.9.2. The issue has been narrowed down to some themes using an unusual approach to loading template files via “stringable objects” instead of primitive strings for file paths. Although this is is not an officially supported approach to loading template files in WordPress (the template_include filter only accepts a string), it nevertheless caused some sites to break. As a result, the Security Team has decided to address this in a fast follow 6.9.3 release. As always, it is recommended that you update your sites to the latest version of WordPress immediately. This ensures your site is protected by all available security fixes in 6.9.2 and that you will not be affected by the bug fixed in 6.9.3. Many thanks to those who reported the issue, assisted in narrowing down the problem, and helped with the fix. You can download WordPress 6.9.3 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin shortly. You don’t have to do a thing! For more information on WordPress 6.9.3, please visit the version page on the HelpHub site. WordPress 7.0 beta 4 The next major release of WordPress will be version 7.0, which is planned for April 9, 2026. The Security Team has decided to package a new beta release (7.0 beta 4) to keep everyone protected from the patched vulnerabilities, including the dedicated members of the community focusing their time and effort on testing the upcoming release. This will be an additional beta release in the 7.0 release cycle. The schedule will remain the same going forward, but with five total beta releases instead of the previously planned four. The next 7.0 beta release is still scheduled for Thursday, March 12th. This beta version of the WordPress software is still under development. Please do not install, run, or test WordPress 7.0 beta versions on production or mission-critical websites. Instead, you should evaluate Beta 4 on a test server and site. Beta 4 updates and highlights WordPress 7.0 Beta 4 contains the ten security patches shipped in WordPress 6.9.2, and more than 49 updates and fixes since the Beta 3 release, including 14 in the Editor and 35 in Core. Each beta cycle focuses on bug fixes. More are on the way, thanks to your help with testing. You can browse the technical details for all issues addressed since Beta 3 at these links: GitHub commits for 7.0 since March 5, 2026 Closed Trac tickets for 7.0 since March 5, 2026 As always, a successful release depends on your confirmation during testing. So please download and test! Props @peterwilson, @desrosj, @marybaum, @amykamala for peer reviewing. View the full article

WordPress 6.9.2 is now available! This is a security release that features several fixes. Because this is a security release, it is recommended that you update your sites immediately. You can download WordPress 6.9.2 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. If you have sites that support automatic background updates, the update process will begin automatically. The next major release will be version 7.0, which is planned for April 9th, 2026. For more information on WordPress 6.9.2, please visit the version page on the HelpHub site. Security updates included in this release The security team would like to thank the following people for responsibly reporting vulnerabilities, and allowing them to be fixed in this release: A Blind SSRF issue reported by sibwtf, and subsequently by several other researchers while the fix was being worked on A PoP-chain weakness in the HTML API and Block Registry reported by Phat RiO A regex DoS weakness in numeric character references reported by Dennis Snell of the WordPress Security Team A stored XSS in nav menus reported by Phill Savage An AJAX query-attachments authorization bypass reported by Vitaly Simonovich A stored XSS via the data-wp-bind directive reported by kaminuma An XSS that allows overridding client-side templates in the admin area reported by Asaf Mozes A PclZip path traversal issue reported independently by Francesco Carlucci and kaminuma An authorization bypass on the Notes feature reported by kaminuma An XXE in the external getID3 library reported by Youssef Achtatal The WordPress security team have worked with the maintainer of the external getID3 library, James Heinrich, to coordinate a fix to getID3. A new version of getID3 is available here. As a courtesy, these fixes are being backported, where necessary, to all branches eligible to receive security fixes (currently through 4.7). As a reminder, only the most recent version of WordPress is actively supported. The backports are in progress and will ship as they become ready. Thank you to these WordPress contributors This release was led by John Blackbourn. In addition to the security researchers mentioned above, WordPress 6.9.2 would not have been possible without the contributions of the following people: Dennis Snell, Alex Concha, Jon Surrell, Isabel Brison, Peter Wilson, Jonathan Desrosiers, Jb Audras, Luis Herranz, Aaron Jorbin, Weston Ruter, and Dominik Schilling. View the full article

WordPress 7.0 Beta 3 is available for download and testing! This beta 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, you should evaluate Beta 3 on a test server and site.WordPress 7.0 Beta 3 can be tested using any of the following methods: PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the Beta 3 version (zip) and install it on a WordPress website.Command LineUse this WP-CLI command: wp core update --version=7.0-beta3WordPress PlaygroundUse the WordPress Playground instance to test the software directly in your browser. No setup is required – just click and go! The scheduled final release date for WordPress 7.0 is April 9, 2026. 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. Please continue checking the Make WordPress Core blog for 7.0-related posts in the coming weeks for more information. Thank you to everyone who is contributing with testing! Catch up on what’s new in WordPress 7.0: Read the Beta 2 announcement for details and highlights. How to test this release Your help testing the WordPress 7.0 Beta 3 version is key to ensuring everything in the release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 7.0. 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 bug report. You can also check your issue against a list of known bugs.Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack. Beta 3 updates and highlights WordPress 7.0 Beta 3 contains more than 148 updates and fixes since the Beta 2 release, including 70 in the Editor and 78 in Core. Each beta cycle focuses on bug fixes, and more are on the way with your help through testing. You can browse the technical details for all issues addressed since Beta 2 using these links: GitHub commits for 7.0 since February 26, 2026 Closed Trac tickets for 7.0 since February 26, 2026 Tapping into the power of AI is even easier in Beta 3! The WP AI Client Connectors screen now dynamically registers providers from the WP AI Client registry, in addition to the 3 default providers, giving users more flexibility and command over AI integrations. A Beta 3 haiku Through sun set and rise, Beta 3 takes off and flies. Seven soon arrives. Props to @annezazu, @jeffpaul, @chaion07, @audrasjb and @valentingrenier for proofreading and review. View the full article

WordPress 7.0 Beta 2 is now ready for testing! This beta version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, you should evaluate Beta 2 on a test server and site. You can test WordPress 7.0 Beta 2 in any of the following ways: PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the Beta 2 version (zip) and install it on a WordPress website.Command LineUse this WP-CLI command: wp core update --version=7.0-beta2WordPress PlaygroundUse the WordPress Playground instance to test the software directly in your browser. No setup required – just click and go! The scheduled final release date for WordPress 7.0 is April 9, 2026. 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. Make sure to check the Make WordPress Core blog for 7.0-related posts in the coming weeks for more information. Thank you to everyone who contributes by testing! Catch up on what’s new in WordPress 7.0: Read the Beta 1 announcement for details and highlights. How to test this release Your help testing WordPress 7.0 Beta 2 is key to ensuring everything in the release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This guide on what to test in WordPress 7.0 will walk you through testing features in WordPress 7.0. 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 bug report. You can also check your issue against a list of known bugs. Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack. Beta 2 updates and highlights WordPress 7.0 Beta 2 contains more than 70 updates and fixes across the Editor and Core since the Beta 1 release. Each beta cycle focuses on bug fixes; and more are on the way with your help through testing. You can browse the technical details for all issues addressed since Beta 1 using these links: GitHub commits for 7.0 since February 20, 2026 Closed Trac tickets for 7.0 since February 20, 2026 Beta 2 also contains a new feature! AI provider management is more intuitive in 7.0 Beta 2 with a new Connectors UI dashboard page. WordPress users can now manage external AI connections in a central place in wp-admin, under Settings > Connectors. The new UI enables users to add, delete, and update external connections. It is powered by an extensible, route-based architecture that allows plugins and themes to hook into the page and expand its functionality. The new Connectors page builds on PHP-based script and menu infrastructure, and adds route components powered by @wordpress/components and @wordpress/admin-ui. A new connections-wp-admin-init hook and registration APIs allow plugins to integrate cleanly. This makes managing external connections easier while giving developers a clearer path to extend the experience. Heads up, block authors! WordPress 7.0 enforces the iframed editor for classic themes when all blocks use Block API version 3. Upgrade your blocks to version 3 to ensure compatibility. More details on Iframed Editor Changes in WordPress 7.0 here. Gutenberg 22.6, released on February 25th, will also be enforced in WordPress 7.0. Here are more details on What’s new in Gutenberg 22.6. A Beta 2 haiku New, and fresh as dew Crafted and refined for you: Beta 2 breaks through. Props to @4thhubbard, @annezazu, @audrasjb, @mukesh27, and @chaion07 for collaboration, proofreading and review. View the full article

WordPress 7.0 Beta 1 is ready for download and testing! This beta release is intended for testing and development only. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, use a test environment or local site to explore the new features. How to Test WordPress 7.0 Beta 1 You can test WordPress 7.0 Beta 1 in any of the following ways: PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the Beta 1 version (zip) and install it on a WordPress website.Command LineUse this WP-CLI command: wp core update --version=7.0-beta1WordPress PlaygroundUse a 7.0 Beta 1 WordPress Playground instance to test the software directly in your browser. No setup required-just click and go! The scheduled final release date for WordPress 7.0 is April 9, 2026. 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 contributes by testing! How important is your testing? Testing for issues is a critical part of developing any software, and it’s a meaningful way for anyone to contribute – whether or not you have experience. Details on what to test in WordPress 7.0 are available here. If you encounter an issue, please share it in the Alpha/Beta area of the support forums. If you are comfortable submitting a reproducible bug report, you can do so via WordPress Trac. You can also check your issue against this list of known bugs. Curious about testing releases in general and how to get started? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack. WordPress 7.0 will include new features that were previously only available in the Gutenberg plugin. Learn more about Gutenberg updates since WordPress 6.9 in the What’s New in Gutenberg posts for versions 22.0, 22.1, 22.2, 22.3, 22.4, 22.5 & 22.6. What’s new in WordPress 7.0? WordPress 7.0 boasts numerous upgrades in the editing and admin experience, delivering enhanced real time collaboration, refined customizability, new dashboard styles, and an expanded developer toolbox for people who create, design, and build with WordPress every day. Working as a team just got easier with the ability for multiple users to edit together in real time, while visual revisions allow a visual comparison between page versions, adding agility to the creation and review process. Working with patterns has been simplified, making layout updates and content changes more intuitive, while view transitions smoothly move you from screen to screen as you click. New and improved blocks and design features in 7.0 make sites more customizable, with video embed backgrounds in the Cover block, a responsive-enabled Grid block, and new Icons, Breadcrumbs and Heading blocks. An updated Navigation block makes menu changes easier and more reliable in fewer steps. Responsive, mobile-friendly controls in 7.0 allow you to hide or reveal blocks based on screen size, while client-side media handling speeds up media processing. The Font Library screen for managing installed fonts is now enabled for all themes, so site editors are always able to browse, install, and organize fonts. For developers, it’s now easier to build modern experiences while staying aligned with Core principles. The new WP AI Client in WordPress 7.0 brings a layer into Core that allows leveraging of AI models from any provider within the WordPress framework. This means plugins and themes can tap into any AI model to expound on its endless options. 7.0 offers even more versatility with the Client Side Abilities API that introduces a standardized way to register and run “abilities” in the browser, supporting richer, more consistent workflows. Additionally, 7.0 introduces PHP-only block registration with auto-generated inspector controls, adding a new dimension to block creation, while Block Bindings updates for pattern overrides expands support to custom dynamic blocks, giving block creators more options. Needless to say, this release offers a wide range of flexibility to creators, teams and developers, while bringing a visual refresh to the admin experience you know and love with a fresh default style. Work together in real time Building on the momentum started in WordPress 6.9, the ability for teams to create and edit together is more refined and robust in 7.0. With this version of WordPress multiple users can edit and collaborate on the same post or page in real time, with data syncing and stabilized notes for smoother teamwork and a more streamlined editing and review process. Real Time Collaboration: Teams can now edit posts and pages together live from multiple locations, with offline editing and data syncing enabled, and a new default HTTP polling sync provider with options for plugins or hosts to include websocket support. With this collaborative content creation workflow, teams can brainstorm more effectively and boost productivity. For the beta period, real-time collaboration is opt-in in order to get broader feedback and testing. Notes: 7.0 introduces real time syncing of notes that helps facilitate collaboration, a keyboard shortcut for new notes, and a series of quality-focused fixes that bring more stability to the Notes feature. A Refined Admin Experience WordPress 7.0 gives the wp-admin experience a boost with a fresh default color scheme, and a cleaner, more modern looking dashboard, while keeping the interface familiar. The upgraded dashboard enhances the editing experience with new visual revision comparisons, and smooth transitioning between screens. Visual Revisions: Working with revisions is even better in 7.0 with the added ability to make visual comparisons to revision versions within the editor. View transitions: Cross-document view transitions in the dashboard offer visual continuity with seamless movement from screen to screen. Customizing content with ease Creators have more flexibility in 7.0 with new tools for content and design, enhanced editing controls, and attention to mobile friendliness. Responsive Editing Mode: Block visibility is now more responsive and mobile-friendly, with the ability for blocks to be displayed or hidden based on screen size. Pattern Editing and contentOnly interactivity: WordPress 7.0 introduces pattern-level editing modes, a tree view for buttons and list blocks, and the ability to opt out of the default content only mode. The new Spotlight mode helps you isolate content in patterns and notes, while the Isolated Editor mode can be used for editing symbols and reusable pieces like synced patterns, template parts, or navigation. Block supports and design tools: 7.0 includes text line indent support, text column support, aspect ratios for wide and full images, dimension width and height support, and dimension presets, tools and controls. New blocks and design options at your fingertips 7.0 delivers a series of new and improved blocks and block features, a streamlined navigation workflow, and more versatile design options like video embeds as section backgrounds. Navigation Block: Navigation workflow is now more intuitive and clear, with improved editing and presentation. 7.0 introduces customizable navigation overlays as template parts, including mobile version overlays that can be hidden or revealed based on custom breakpoint settings. Heading Block: Heading levels are now available as block variations, giving more control over page hierarchy and design. New blocks: 7.0 makes building pages more diverse with new Breadcrumbs and Icons blocks. Cover block embedded videos: Video embeds can now be used as a background in the cover block, opening up opportunities for sleeker and more creative designs. The Grid block is now responsive-enabled allowing grid-based layouts to adapt more smoothly across screen sizes. The Gallery block now has lightbox support that lets the user click through and view each gallery image. Developer’s toolbox Working with WordPress on the backend is now more robust for developers, with new and enhanced API features that support flexibility and lay a foundation for future advancements. The Client Side Abilities API provides a client-side registry for WordPress capabilities that allows you to tap into new and innovative website options. WordPress 7.0 offers even more by introducing the Web Client AI API to Core, enabling access to generative AI models in one central interface. Web Client AI API: The new AI client and API acts as a command center for accessing and communicating with generative AI models, with providers remaining external to WordPress Core, and Abilities API integration. Abilities and Workflows API: With the new client side abilities package users have access to new and hybrid abilities, filter and search functionality for abilities, and an improved command palette and UI. Blocks and patterns created on the server: WordPress 7.0 boasts the ability for PHP-only blocks and patterns to be generated server-side and auto-registered with the Block API. DataForm: Introducing a new details layout, new controls (combobox, adaptiveSelect), and updated trigger for panel layout (dedicated edit button). Additionally, the initial iteration for validation is complete: all controls have support, and all layouts display error messages. DataViews: DataViews has a new activity layout, and a foundation has been laid to be able to register 3rd party types in future releases. CodeMirror update: CodeMirror has been updated to version 5.65.40, aiding more flexible extensibility and library options. Media processing in the browser WordPress 7.0 introduces Client-side media processing, leveraging the browser’s capabilities to handle tasks, like image resizing and compression, for smoother image processing. This enables the use of more advanced image formats and compression techniques, and reduces demand on the web server; providing a more efficient media handling process for both new and existing content, and supporting smoother media workflows. With so many options and enhancements in WordPress 7.0 Beta 1, this is still only the beginning. You can expect future releases to be even better. Just for you: a Beta 1 haiku: As sun kisses moon, Beta 1 ignites in bloom… Seven-oh lands soon. Props to @ellatrix, @jeffpaul, @annezazu, @chaion07, @zunaid321, @audrasjb, @mukesh27, @ankit-k-gupta, @oandregal, @westonruter, @karmatosed, @bph for reviewing and collaborating on this post! View the full article

Today, we are happy to announce our first WordPress-focused micro-credential, designed to help students build practical AI skills, earn a recognized credential, and connect more directly to job opportunities. The program, AI Leaders, is a workforce-oriented credential rooted in WordPress and open source contributions. Students are paid for their time, work on real WordPress projects, and gain hands-on experience applying AI in ways that are directly relevant to the WordPress ecosystem. This pilot represents a meaningful step forward in how the project supports learning, contribution, and career pathways. Beginning in March 2026, AI Leaders launches its first cohort of 80 students from Illinois and Louisiana, with University of Illinois Chicago (UIC) students given priority to apply before enrollment expands to the public. Enrollees begin with an orientation covering generative AI tools and AI literacy. From there, 40 participants are selected for the full course experience. Ultimately, the program leads to the AI Leader WordPress Micro-Credential and an opportunity to pursue living-wage job pathways. Learners who complete the course also earn $1,000 (USD). This pilot is the result of collaboration across several organizations, each playing a distinct role. The program is funded through the UIC Tech Solutions Open Source Fund, with support from the University of Illinois Chicago and Automattic. That funding supports program delivery, participant compensation, and the institutional infrastructure needed to run the pilot. Alongside that funding, the WordPress project and the WordPress Foundation will contribute to the development of the credential itself. This includes shaping the curriculum, grounding the work in real WordPress AI use cases, and ensuring alignment with open source values and public benefit. Visit the AI Leaders site to learn more and apply. Start Your Application This is the first WordPress Foundation-backed micro-credential, and it is intentionally being run as a pilot. We are exploring how the Foundation could support additional credentials over time, across different skill areas and partners, while maintaining clear governance, openness, and alignment with the WordPress project. It represents a step toward a future where WordPress contributors can more easily translate their skills into credentials, careers, and long-term opportunities. WordPress offers a wide range of educational opportunities for people at every stage, from first steps to advanced contribution. Explore workshops, lesson plans, and community-created resources designed to help you build practical skills while connecting with others who are learning and contributing at WordPress.org/education/. View the full article

WordPress 6.9.1 is now available! This minor release includes fixes for 49 bugs throughout Core and the Block Editor, addressing issues affecting multiple areas of WordPress including the block editor, mail, and classic themes. For a full list of bug fixes, please refer to the release candidate announcement. WordPress 6.9.1 is a short-cycle maintenance release. The next major version of WordPress will be 7.0; it is scheduled for release on 9 April 2026 at WordCamp Asia. If you have sites that support automatic background updates, the update process will begin automatically. You can download WordPress 6.9.1 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. For more information on this release, please visit the HelpHub site. Thank you to these WordPress contributors This release was led by Aaron Jorbin and Aki Hamano. WordPress 6.9.1 would not have been possible without the contributions of the following people. Their asynchronous coordination to deliver maintenance fixes into a stable release is a testament to the power and capability of the WordPress community. Aaron Jorbin, Aaron Robertshaw, acmoifr, Adam Silverstein, Adil Öztaşer, Aki Hamano, Alexander Bigga, amanandhishoe, Andrew Serong, Bernie Reiter, brumack, David Arenas, David Baumwald, Deepak Gupta, Deepak Prajapati, Dennis Snell, digitalblanket, Ella Van Durpe, Fabian Kaegy, George Mamadashvili, Hit Bhalodia, iflairwebtechnologies, Isabel Brison, Jaydeep Das, Jb Audras, Jeff Golenski, Jeffrey Paul, jhtjards, Joe Dolson, John Blackbourn, Jon Surrell, Jonathan Desrosiers, Jorge Costa, Justin Tadlock, Karthick, Kirtikumar Solanki, Lena Morita, luisherranz, Madhavi Shah, Manuel Camargo, Maud Royer, Mehraz Morshed, Monarobase, mrwweb, Mukesh Panchal, Muryam Sultana, mydesign78, Narendra Sishodiya, Nik Tsekouras, Ninos, Noruzzaman, Olga Gleckler, Ophelia Rose, Ov3rfly, Ozgur Sar, Paragon Initiative Enterprises, Pascal Birchler, Pavel Vybíral, Peter Wilson, pmbs, Presskopp, r1k0, ramonopoly, Riad Benguella, Ricardo S., Rolly Bueno, Sarah Norris, Scott Reilly, Sergey Biryukov, Shazzad Hossain Khan, siliconforks, Soyeb Salar, spielers, Stephen Bernhardt, studio_m, Takashi Irie, Takashi Kitajima, threadi, Tobias Bäthge, Tomoki Shimomura, Umesh Singh, Vania, Weston Ruter, WFMattR, wolf45, zoe20 How to contribute To get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core channel. Need help? Check out the Core Contributor Handbook. Props to @audrasjb, @davidbaumwald, @westonruter, @jeffpaul, @presskopp for proofreading. View the full article

Faster Way For AI Agents To Test AI code agents are getting better at writing WordPress plugins and themes, but testing can still be the slow part. WordPress contributor Brandon Payton has published wp-playground, a new AI agent skill designed to run WordPress via the Playground CLI, giving agents a fast, repeatable way to run WordPress and verify their work as they iterate. “AI agents work better when they have a clear feedback loop. That’s why I made the wp-playground skill. It gives agents an easy way to test WordPress code and makes building and experimenting with WordPress a lot more accessible.” — Brandon Payton, WordPress Contributor What the Playground skill does When launched, the skill starts WordPress and detects where the current code should live inside a WordPress install. For example, it can mount a plugin into wp-content/plugins or a theme into wp-content/themes by recognizing common file signatures (such as plugin headers or a theme’s style.css). This helps agents move from “generated code” to “running site” with fewer manual steps. Install and try it today. Find more information on this GitHub link: WordPress AI Agent Skills Early results and testing workflow In testing, agents were able to start WordPress, build playful plugins, and validate behavior in a tight feedback loop. Once Playground was running, the agent alternated between tools such as curl and Playwright to interact with WordPress, verify results, apply fixes when needed, and then re-verify with Playground. Faster startup and smoother iteration Helper scripts handle startup and shutdown, so an agent doesn’t waste time guessing when WordPress is ready. Using helper scripts reduced the “ready to test” moment from roughly a minute to a few seconds on the author’s machine. The Playground CLI can also log in automatically for easier WP-Admin access during testing. Install and try it now For those who want to try it in Claude Code, Codex, or another AI agent, installation requires Node.js and npm and looks like this: # Run this in a project directory to install the skills for that project npx openskills install WordPress/agent-skills # Make skills available to non-Claude agents npx openskills sync A new repo for WordPress agent skills This release also comes with a new home for this kind of work: https://github.com/WordPress/agent-skills. It’s an early step in exploring how AI agents can collaborate with WordPress tooling, and contributions from the community are welcome. Future additions being explored include persistent Playground sites based on the current directory, running commands against an existing Playground instance (including wp-cli), and Blueprint generation. View the full article

WordCamp Asia is back in 2026, this time in Mumbai, India, and it’s building on a year that showed just how ambitious and connected the WordPress community has become. Now is the time to get involved. Get your ticket, explore sponsorship opportunities, and help spread the word. Get Your Event Pass Become a Sponsor About WordCamp Asia In 2025, more than 1,400 attendees from 71 countries gathered in person, with nearly 15,000 more joining online for WordCamp Asia 2025. With notable guests like WordPress Co-founder Matt Mullenweg and Gutenberg Lead Architect Matías Ventura, and a diverse lineup of speakers and panelists from across the ecosystem, WordCamp Asia 2025 brought together a community actively shaping the future of the open web. It’s the people. It’s the friendships and the stories. Matt Mullenweg, WordPress Cofounder WordCamp isn’t just about sessions and schedules. It’s about connection. It’s about learning directly from people who are building, scaling, and sustaining WordPress in the real world. It’s about sharing ideas, debating the future of the open web, and leaving with renewed energy for the work ahead. And in 2026, that spirit returns stronger than ever. Tickets for WordCamp Asia 2026 are on sale now, and this is the moment to secure your spot. WordCamps are intentionally priced to remain accessible, and early ticket sales help organizers plan an inclusive, high-quality experience for everyone. Join 3,000+ Web Professionals April 9 – 11, 2026 | Jio World Convention Centre, Mumbai, India Get Your Event Pass WordCamp Asia is also made possible by the organizations that step up to support it. Sponsorship plays a critical role in keeping the event accessible, supporting contributors and volunteers, and ensuring the experience reflects the values of the WordPress project. For sponsors, WordCamp Asia 2026 offers a rare opportunity to connect with a highly engaged, global audience in a setting built on trust, collaboration, and shared purpose. Sponsorship packages are designed to support a wide range of organizations, from local companies to global businesses building products and services on WordPress. Beyond visibility, sponsors become part of the story—helping sustain the ecosystem and invest directly in the community that makes WordPress possible. If your company is interested in becoming a sponsor or you would like to know more, please reach out. Become a Sponsor At every level, WordCamp Asia is powered by people. Organizers, volunteers, speakers, sponsors, and attendees all contribute to an experience that reflects WordPress’s shared values of openness and collaboration. It’s a place where new voices are welcomed, long-time contributors reconnect, and ideas move from conversation to action. WordCamp Asia 2026 is more than an event—it’s a moment to come together, reflect on where we are, and help shape what comes next. Whether you’re attending for the first time, returning for another year, or supporting the event as a sponsor, your involvement helps strengthen the WordPress ecosystem and the global community behind it. We’ll see you in Mumbai. View the full article

Over the past few weeks, a new space has taken shape on WordPress.org for students who want to learn, build, and contribute. WordPress Education programs bring together initiatives that help students enter the WordPress ecosystem through clear, accessible entry points that lead to real-world practice. With hands-on initiatives and supportive communities, participants can grow new skills and take their first steps as contributors. Across campuses and communities worldwide, learners publish real projects, build practical experience, and gain confidence as part of open source creation. CC0 licensed photo by Virendra Kumar Yadav from the WordPress Photo Directory. A clearer path into the WordPress ecosystem WordPress Education is designed to help students turn knowledge into practice, discover their strengths, and understand how their contributions can make a real impact through three core programs: WordPress Campus Connect, WordPress Credits, and WordPress Student Clubs. Through hands-on campus events, such as WordPress Campus Connect, on-campus groups like WordPress Student Clubs, and a practice-based program called WordPress Credits, participants can gain practical experience, publish real-world projects, and build confidence as contributors to a global culture of open-source creation. At its heart, these WordPress education programs are about three simple ideas: Learn. Build. Connect. This update brings WordPress education programs together in one place, with an easy way to explore initiatives, understand how they work, and take the next step. You will find: A home for WordPress Education programs and updates Clear “how to get involved” paths for students, educators, mentors, organizers, and sponsors Stories, highlights, and examples of real projects created through the programs Links to the Education Handbook for program guidelines and resources Want to learn more about WordPress education opportunities? Visit The Portal You can also view more information from the WordPress Community Education Programs Handbook. Learn how this serves as a central guide and resource for all community-driven educational initiatives. WordPress Campus Connect WordPress Campus Connect is a growing global learning initiative that brings hands-on WordPress learning directly to the students on their campus. The organizers can come from within educational institutions or from the local communities to help deliver WordPress programming and create the future stewards of WordPress. Learn more: https://wordpress.org/education/campus-connect/ WordPress Credits WordPress Credits is a contribution-based program by the WordPress Foundation that connects higher education students with the global WordPress community. Educational institutions partner with the WordPress Foundation to offer students credits toward their degrees for contributing 150 hours to the WordPress project. Learn more: https://wordpress.org/education/credits/ WordPress Student Clubs WordPress Student Clubs empower students to build on-campus WordPress communities that keep learning going throughout the year. In the spirit of our local community meetups, these groups operate as on-campus equivalents, keeping students engaged and connected with their local WordPress communities. Learn more: https://wordpress.org/education/student-clubs/ Support This Growing Movement Help spread the word, and let friends, students, and others know how they can contribute to this growing effort, including a widely expanding translation effort. WordPress Education has already been translated into 10 new languages. WordPress Education is powered by people who believe in open learning and the power of collaboration. View the full article

WordPress Playground had a busy year in 2025, with updates that make it more capable for day-to-day development, plugin previews, and learning environments. The project’s latest year-in-review highlights progress across performance, compatibility, database support, and tooling, expanding what can be done in a WordPress environment that runs in the browser and through the command line. From faster load times to broader plugin support, the throughline is clear: Playground is moving beyond quick demos and into workflows that help developers and educators test, iterate, and share WordPress experiences more easily. Try Playground Now Key Takeaways Plugin previews are more reliable: 99% of the top 1,000 plugins can be installed and activated successfully, making demos and evaluations more trustworthy. Everything is faster: A performance upgrade reduced average response time by 42%, and further optimizations improved overall “time to first useful click.” Database tools work in browser: Improved database compatibility enabled tools like phpMyAdmin to be used directly on playground.wordpress.net. More practical tooling for real work: Testing configurations and previewing changes can happen in one place, without a complete local environment first. New visual gallery of blueprints: A new visual gallery of blueprints provides excellent starting points for various types of sites. Global adoption: Playground was used 1.4 million times globally, with growing documentation translations and community contributions. Reliable Plugin Previews and Experimentation A headline update from 2025 is the focus on compatibility. In testing with the top 1,000 plugins from the WordPress plugin directory, 99% installed and activated successfully. That matters because it raises confidence in what Playground is best known for: letting people try things quickly, without a complex setup, and with fewer surprises. This highlighted that Playground is increasingly useful as a general-purpose PHP sandbox. Alongside WordPress, it can support standard PHP tools and projects, which makes it easier to explore how WordPress fits into broader development workflows and to share reproducible environments with others. If you try something new and unexpected in Playground, the update encourages you to share what you learn in the #playground Slack channel, so the community can build a clearer picture of what works well today and what is improving next. Faster Load Times Speed was a central theme in 2025. A recent year-in-review report revealed a 42% reduction in average response time, and this is not just a single change. A series of improvements make Playground feel quicker in the moments people notice most, such as loading WordPress, opening wp-admin, and switching between tasks. Several behind-the-scenes updates were described in plain terms as “less waiting”: checks happen earlier, parts of the experience load in a smarter order, and more content is reused from cache, so repeat actions are snappier. For people using Playground to review a plugin, validate a bug fix, or teach a class, these improvements mean the same thing: faster feedback loops, with fewer pauses that break concentration. Better Tooling and Compatibility In 2025, Playground also became more “toolbox-like” in the browser. The update highlighted features that reduce context switching, such as editing files on the page, building and testing starter configurations (Blueprints) in a dedicated editor, and launching database tools such as phpMyAdmin and Adminer with a single click. On the database side, a significant compatibility upgrade was introduced to improve support for more complex database behavior. The practical outcome is that more WordPress sites and plugins behave as expected in Playground, and more developer tools can run inside the environment. Blueprints also advanced in ways that benefit both builders and sharers. The updates focus on making starter setups easier to create, browse, and reuse, especially when a demo requires content, media, or a specific configuration that should launch consistently. One of the clearest ways to see that progress is the WordPress Blueprints Gallery, a community library of ready-to-launch WordPress environments. From practical “building block” examples (such as starting with a specific login role) to demos that automatically install themes and plugins, to richer setups that generate posts and featured images via WP-CLI, the gallery demonstrates how quickly an idea can become a fully functional site that you can browse and share. Examples: For anyone who wants to experience the power of WordPress without the setup, the gallery serves as a strong reminder of what Playground makes possible: shareable, repeatable site experiences that work the same way every time — ideal for demos, workshops, testing, and “try it now” links. Clear adoption signals back all of this. The review reports 1.4 million uses globally, documentation translations in multiple languages, and growing integration across the plugin directory through Playground-powered previews. It also points to a steady increase in community contribution, from documentation and support to talks and real-world workflows built on top of Playground. A huge thank you to everyone who tried Playground over the past year, whether you launched a quick demo, tested a change, taught a workshop, or helped make the documentation more accessible in your language. And if there’s anything that would make Playground even more helpful for your day-to-day work, the project actively welcomes ideas and feature requests via the WordPress Playground GitHub issues tracker. Looking Ahead As we closed out 2025 and now look forward to 2026, we can see several forward-looking initiatives, including work on MySQL binary protocol support (to enhance broader compatibility with MySQL tools) and continued exploration of debugging enhancements, such as expanded XDebug access. For anyone who last tried Playground as a quick demo environment, 2025’s updates suggested a shift in direction: Playground is increasingly positioned as a practical layer for testing, teaching, previewing, and reviewing WordPress, both in the browser and in local workflows. View the full article

Become a driving force behind WordPress innovation by joining the Global Community Sponsorship Program: a comprehensive initiative that supports the events and people powering our open source mission. As a Global Sponsor, your organization gains meaningful visibility across the international WordPress ecosystem while helping to fund events that foster growth, collaboration, and community. Why Choose Global Sponsorship? Instead of managing multiple individual sponsorships, this streamlined program consolidates your efforts into one efficient and impactful partnership. Efficiency and Simplified Administration Skip the complexity of coordinating invoice payments with numerous volunteer teams. Our centralized approach saves time and resources. In 2026, sponsors will benefit from: A dedicated Slack channel for direct communication with the WordPress Community Support team and Community Program Managers Monthly updates listing upcoming WordPress events, their current planning stages, and scheduled dates Expanded Reach and Impact Your sponsorship amplifies your presence worldwide, ensuring consistent visibility across global WordPress community events. Stability and Reliability Your commitment strengthens locally organized events by providing predictable funding that supports venues, logistics, and growth. Flexible Branding Options Adapt across your portfolio—Global Sponsors can represent different brands at different events (subject to approval and advance notice). Program Benefits Global LeaderRegional PowerhouseCommunity Builder Best for: Established brands seeking global reach and year-round visibility.Companies aiming for regional dominance and strong brand recognition.Organizations supporting the next generation of WordPress education.Sponsorship payable in full or through quarterly installments$180,000$110,000$60,000Top tier sponsorship benefits at all local WordCamp events (excludes flagships) with priority access to claim a sponsor table at in-person WordPress eventsOption to feature multiple brands across eventsDedicated sponsor landing pageComplimentary WordPress event tickets for your teamRecognition across all WordPress eventsSponsor Spotlight post on WordPress.org/news featuring highlights from recent WordCampsQuarterlyAnnuallyInclusion of your company logo in signage and materials for WordPress Campus Connect eventsAll signage & materials for the year (digital and printed)Signage & materials for 5 events per year (printed only)All signage & materials for the year (digital and printed)Opportunity to be featured in an exclusive digital binder for WordPress Campus Connect event organizersPriority placement (logos & text)Feature listing (text only)Feature listing (text only)Regular recognition in monthly education buzz report How Sponsorship Funds Are Used Global Sponsorship funds directly support: Local WordPress events worldwide (venue rental, catering, A/V, and more) Meetup.com license fees for over 671 WordPress Meetup groups globally Administrative costs like insurance, banking, and annual financial audits that ensure transparent operations Your partnership helps sustain the community that powers more than 43% of the web. Together, we can keep the WordPress project thriving and expanding for years to come. If your company is interested in joining the Global Sponsorship program or you would like to know more, please reach out. Contact WordPress Community Support Please see Rules for Sponsor Materials for more details about terms of sponsorship. Please also see our sample sponsorship agreement. If you’d like to go one step further, please consider donating directly to the WordPress Foundation. We operate lean—every dollar goes toward keeping WordPress free, supporting education, and funding the community that makes the web a better place. In short, your donation helps us keep the lights on and the mission alive. View the full article

State of the Word 2025 brought the WordPress community together for an afternoon that felt both reflective and forward-moving, blending stories of global growth with technical milestones and glimpses of the future. This year also marked the twentieth State of the Word since the first address in 2006, a milestone noted in the WordPress history book Milestones: The Story of WordPress as the beginning of a tradition that has helped the project tell its own story. From the outset, the keynote carried a sense of momentum shaped by thousands of contributors, educators, students, and creators whose steady participation continues to define the open web. It was a reminder that WordPress is more than software. It is a community writing its future together. What we have is more than code. It’s momentum, it’s culture, and it’s a system that lets people learn by doing and lead by showing up. — Mary Hubbard, WordPress Executive Director Mary opened the evening by reflecting on her first full year as Executive Director, a year spent listening deeply and seeing firsthand how people across regions learn, contribute, and lead. Her remarks grounded the keynote in the lived reality of a community that grows because people invest in one another, teach openly, and build trust through contribution. I’ve met people using WordPress to unlock new careers. I’ve met contributors who started a single translation or forum post and are now leading major pieces of the project. In LatAm, Europe, and the States, I’ve seen students get access to WordPress tools and start building faster than we could have ever imagined. I’ve watched communities build in public, resolve disagreements in the open, and collaborate across languages and time zones. That reflection offered a clear reminder of what makes WordPress resilient through change: a culture of showing up, learning by doing, and supporting others along the way. The project moves forward because people choose to participate in ways both large and small, strengthening the foundation that has carried WordPress for more than two decades. With that foundation in place, the keynote moved through a series of stories and demonstrations that highlighted where WordPress stands today and where it is headed next — from a historic live release of WordPress 6.9 to expanding global education pathways, emerging AI capabilities, and deeper collaboration across the entire ecosystem. WordPress by the Numbers Project Cofounder Matt Mullenweg began with a wide-angle view of the project’s growth. WordPress powers over 43% of the web, with 60.5% of the CMS market. Shopify, its nearest competitor, holds 6.8%. Among the top 1,000 websites, WordPress’s share climbed to 49.4%, up 2.3% from the previous year. Multilingual usage continued its strong rise. Over 56% of WordPress sites now run in languages other than English. Japan stood out, with WordPress powering 58.5% of all Japanese websites and 83% of the CMS market. Japanese became the second most-used language on WordPress at 5.82%. Spanish followed, then German, French, and Brazilian Portuguese. The plugin ecosystem saw explosive growth. The directory surpassed 60,000 plugins, and plugin downloads were on pace to reach 2.1 billion by year-end. Over 1,500 themes have been released this year as well. Contributors also hit new highs. The 6.8 release included 921 contributors, the largest group yet. WordPress 6.8 saw 79.5 million downloads, up 13%, and WordPress 6.9 included contributions from 230 first-time contributors and more than 340 enhancements and fixes. A Release Moment to Remember This year’s keynote delivered something WordPress had never attempted before: a live on-stage release of WordPress 6.9. Mary set the moment up earlier in the program, calling WordPress 6.9 “fast, polished, and built for collaboration.” She explained that it reflected a year of intentional iteration, improved workflows, and deeper cross-team participation. Matt took the stage with some of the release leads, the release button in hand. The room counted down, and then WordPress 6.9 shipped live, instantly updating millions of sites around the world. It was both a celebration and a testament to the reliability and trust the WordPress community has built into its release processes. Shipping a major version of WordPress in real time, on stage, without drama, is something the early contributors could hardly have imagined. That reflection connected back to WordPress’s origin story. Matt talked about discovering the B2 forums, asking questions, and eventually reaching the point where he could answer someone else’s. That transition from learner to contributor remains at the heart of the project today. Two decades later, WordPress has grown from those early interactions into a platform that can ship a major release in front of the world, powered by thousands of contributors building together. WordPress and the Future of AI As the keynote shifted toward the future, Matt acknowledged what has become an essential truth of the moment: it would be impossible to talk about the next chapter of WordPress without talking about AI. He reminded the audience that in 2022, long before ChatGPT entered global conversation, he encouraged the community to “learn AI deeply.” The speed of change since then, he said, has exceeded every expectation, and WordPress has been preparing for it in ways both visible and behind the scenes. Matt introduced one of the most important architectural developments of the year: the Abilities API and the MCP adapter. The Abilities API defines what WordPress can do in a structured way that AI systems can interpret, while the MCP adapter exposes those abilities through a shared protocol. This means AI agents — whether built by individuals, companies, or larger platforms — can understand and interact with WordPress safely and predictably. Instead of relying on one-off integrations or brittle interfaces, WordPress now participates in a broader ecosystem of tools that can query its capabilities and perform tasks using a standard, governed approach. Matt then highlighted how developers are already using AI in their everyday work through tools like Cursor, Claud Code, and next-generation CLIs. These tools can explore entire codebases, generate documentation, produce tests, refactor large components, and even coordinate sequences of WP-CLI commands. For many developers, they expand what a single person can accomplish in an afternoon. They don’t eliminate the need for human judgment — they amplify it. With that foundation laid, Matt turned the audience’s attention to Telex, the experimental environment designed to turn natural-language prompts into Gutenberg Blocks. Telex has already moved beyond experimentation and into real use. Matt showed examples from community creator Nick Hamze, who uses Telex to power micro-business tools that represent practical, revenue-generating workflows that previously required custom engineering. Matt then widened the lens to show what companies across the ecosystem are building with AI. Hostinger’s Kodee can generate a complete WordPress site from a single description. Elementor AI demonstrated similarly rapid creation inside its own editor, producing full sections and layouts in seconds. WordPress.com showcased how its AI tools help users draft, rewrite, and refine content while keeping language aligned with the site’s voice. Yoast demonstrated how AI can support SEO workflows by generating structured suggestions and improving readability. Together, these examples illustrated that AI is not arriving in one place — it is arriving everywhere. Experimental browsers can navigate WP Admin autonomously, performing tasks such as clicking buttons, opening menus, changing settings, and performing multi-step tasks without requiring any custom plugins or APIs. This raised a key question that Matt encouraged the community to consider: Which AI capabilities should live inside WordPress itself, and which should remain external, operating through the browser or operating system? Matt closed the section by discussing WordPress-specific AI benchmarks and evaluation suites. These shared tests will measure how well AI systems understand and execute WordPress tasks, from enabling plugins to navigating WP Admin to modifying content and settings. The goal is to create a foundation where future AI tools behave predictably and responsibly across the entire ecosystem, giving creators confidence that intelligent tools understand the platform deeply. A Global Community Growing Together Mary then returned to the stage to celebrate the ecosystem that supports WordPress’s growth. Across continents, diverse groups of people have hosted WordPress events, training new contributors and welcoming newcomers into the project. WordCamp growth in 2025 reflected that: more than 81 WordCamps across 39 countries, powered by over 5,000 volunteers and attended by nearly 100,000 people, with sixteen more events still underway. Education played a major role in this community expansion. Learn.WordPress.org served over 1.5 million learners this year, with clearer pathways into more structured programs like Campus Connect and WordPress Credits. This bridging was deliberate. Many learners arrive through tutorials or workshops but need clearer guidance on how to deepen their skills. By reshaping navigation and improving wayfinding across WordPress.org, the project began closing that gap. She spotlighted Costa Rica’s Universidad Fidélitas, where WordPress moved beyond extracurricular interest into formal academic integration. Long before signing an agreement with the WordPress Foundation, their students were hosting WordCamp San José, forming student clubs, and treating WordPress as a crucial part of digital literacy and professional development. Students of the WordPress Fidélitas Club Wapuu appeared across events as a familiar companion and a cultural thread running through contributor tools and community projects. Its presence was a reminder that creativity and playfulness are as essential to open source as documentation or code. Matt highlighted the story of Youth Day in Managua, Nicaragua. Seventy-five young people spent a full day building their first WordPress sites. Sessions were taught by teenagers, for teenagers. They learned to pick themes, customize layouts, create contact forms, and publish content. Contribution often starts with a simple moment of confidence, and those early sparks can shape entire careers. Together, these moments illustrated a project expanding not just in numbers, but in depth, diversity, and global reach. WordPress is growing because communities are finding their own ways to embrace it. What’s New in WordPress 6.9 Joining virtually, WordPress Lead Architect, Matías Ventura, shifted the keynote from vision to practice. Matías offered a detailed walkthrough of what makes WordPress 6.9 one of the most refined, collaborative, and forward-looking releases the project has shipped in years. He returned to the four familiar lenses of creation — writing, designing, building, and developing — and showed how each evolved in this release cycle. He began with notes in the Block Editor, one of the most anticipated features. Notes allow collaborators to comment directly on individual blocks in a post or page. When a note is selected, the surrounding content subtly fades, helping contributors stay focused on context. Because notes are built on WordPress’s native comment system, they integrate seamlessly with existing communication workflows, including email notifications. Matías highlighted that notes development exemplified collaboration at its best, with contributors from various companies working together to bring the feature to life. From there, he turned to refinements across the writing and design experience. Editor interactions feel smoother and more consistent. Patterns behave more predictably. Spacing and typography controls are clearer, more organized, and more intuitive. Together these capabilioties make the experience of writing and designing inside WordPress calmer, more reliable, and more empowering. Block bindings now provide a more intuitive, visual way to connect blocks to dynamic data sources. Users can switch or remove bindings with a single click, and developers can register additional sources to support custom workflows. This work lays the foundation for a future where dynamic data flows more naturally through blocks, enabling site creators to build richer interfaces without writing code. On the developer front, Matías focused on three foundational upgrades that represent major steps forward in how WordPress will evolve over the coming years. The first was the Abilities API, a unified registry that describes what WordPress can do — across PHP, REST endpoints, the command palette, and future AI-driven interactions. The HTML API introduces new ways of working with and modifying HTML server-side. The API ensures safer, more reliable handling, lowering the barrier for theme and block developers who work with dynamic or structured markup. The Interactivity API delivers smoother, faster interactions without requiring heavy JavaScript frameworks. Improved routing, better state management, and clearer conventions help developers create rich, modern interfaces without leaving the WordPress philosophy of simplicity and flexibility. After Matías wrapped his presentation, Matt stepped back in to highlight several developments that build on the foundations of 6.9 and strengthen the overall WordPress ecosystem. He pointed first to the Plugin Check Plugin, a tool designed to help developers align with current WordPress standards and catch common issues early, making plugins more reliable for users and easier to maintain over time. Matt then spoke about ongoing progress in data liberation, noting improvements to the WordPress importer that make it easier for people to bring their content into WordPress without disruption or loss, an important step toward ensuring the open web remains portable and resilient. He also highlighted advances across the Playground ecosystem, including WordPress Studio, the Playground CLI, and an expanding set of Blueprints. These allow developers and learners to spin up complete WordPress environments in seconds, test ideas, and experiment without servers or configuration. Matt closed this portion by emphasizing work on safer updates, which help WordPress avoid partial installs and ensure that updates complete smoothly even in less predictable hosting conditions, reinforcing WordPress’s commitment to stability as the platform continues to grow. Matt emphasized that WordPress 6.9 is not defined by any single headline feature, but by a broad spectrum of refinements across the entire experience. It is a release that deepens reliability, expands capability, and sets the stage for future innovation. Insights from the AI Panel The keynote transitioned into a live AI panel moderated by Mary Hubbard. The panel brought together four perspectives from across the ecosystem: James LePage (Automattic), Felix Arntz (Google), and Jeff Paul (10up), and Matt Mullenweg. Their conversation touched on the philosophy, practice, and future of AI inside WordPress — not as a distant trend, but as an active part of the project’s evolution. A central theme was AI’s ability to amplify human creativity. James LePage put it plainly: It’s not that we’re going to just add sparkle buttons everywhere. We’re going to do some crazy stuff here — things we’re going to build into the way you interact with creating content, with expressing yourself digitally. We want to give you more power, more control, and make you more effective at creating. Jeff Paul echoed this sentiment, emphasizing that AI should make developers more productive by handling repetitive work and freeing them to focus on higher-level decisions. Felix Arntz expanded the idea further, describing how Google sees AI as a way to make the web more accessible and intuitive, especially for new creators who may not have formal technical training. From left to right: Mary Hubbard, Matt Mullenweg, Jeff Paul, Felix Arntz, James LePage Looking ahead, the panelists predicted deeper contextual integrations, AI-assisted debugging and scaffolding for developers, and workflows where agents can take on sequences of tasks while remaining directed by human decisions. They also highlighted the importance of standards, shared protocols, and privacy-focused design as essential components of WordPress’s long-term approach. The next 20 years looks like WordPress remaining what it is today, which is the center of the open web. The panel closed on a forward-looking but steady note. AI is accelerating, but WordPress is designing its foundations with flexibility and values that endure. The tools may change, but the commitment to openness, agency, and creative freedom remains the compass. Questions That Push Us Forward Matt introduced the Q&A as one of his favorite parts of State of the Word because it reveals what people are imagining, struggling with, or eager to build. The first question addressed the growing interconnectedness of today’s web. What happens, a participant asked, when a major provider like Cloudflare goes down? As tools and agents rely more heavily on external services, failures can cascade. Matt acknowledged that outages are increasingly visible, but also argued that each one strengthens the system. “Every failure, every edge case, everything that you never imagined is just another opportunity to find that new edge case,” he said. Resilience is not avoidance of failure, but the ability to grow stronger after it. Another question focused on the longevity of web content. With platforms shutting down or links breaking over time, how can creators ensure their work endures? Matt pointed to the Internet Archive as one of the great stabilizers of the open web. He highlighted a new plugin that automatically scans posts and replaces dead links with archived versions, helping preserve the historical fabric of the web even as individual services come and go. The next question turned to real-time collaboration inside WordPress. A participant asked how co-editing fits into the future of WordPress and how these tools might help creators work more confidently. Matt talked about how collaboration tools can support people who are just starting their creative journeys — whether they are entrepreneurs, students, or first-time site builders. He described real-time editing as part of a broader vision of WordPress “just doing the work for you” in high-pressure or early-stage creative moments. The final question considered long-term decision-making. Matt noted that predicting what will change is difficult, but identifying what will remain the same is much easier. For WordPress, he said, the invariant is clear: people will always want agency, openness, and the ability to publish on their own terms. These values guide decisions not only in the present, but across decades of future evolution. TBPN Podcast Appearance After the Q&A, the keynote shifted gears with a live crossover segment featuring TBPN (the Technology Business Programming Network), a tech-focused podcast. The segment introduced a lively, unscripted energy into the room. The hosts kicked things off by asking Matt what the “word of the year” should be. He chose “freedom”, connecting it directly to the core philosophy of open source. He described open source licenses as a kind of “bill of rights for software,” giving users inalienable rights that no company can revoke. In a world increasingly shaped by software platforms and digital ecosystems, these freedoms form the heart of what keeps the web open and accessible. Conversation then moved to Beeper, the multi-network messaging client. Asked whether Beeper aims to “tear down walled gardens,” Matt rejected that framing. Instead, he offered a more collaborative metaphor: bringing gardens together. Most people have friends and colleagues scattered across WhatsApp, Instagram, LinkedIn, Messenger, and SMS. Beeper doesn’t replace those apps — it brings messages together into a unified interface.. The conversation eventually returned to publishing. Matt referenced the same principle he noted earlier: the importance of identifying what won’t change. For WordPress, he said, that means doubling down on freedom, agency, and the ability to publish without gatekeepers. Even as AI evolves, even as platforms shift, even as new tools emerge, these are the values that will guide the project forward. Building the Web We Believe In As the keynote drew to a close, Matt returned to a message that had threaded through every section of the evening. The future of WordPress is not arriving from outside forces — it is being crafted, questioned, tested, and expanded by the people who show up. Contributors, students, educators, community organizers, designers, developers, business owners, and first-time site builders all play a role in shaping the platform. He spoke about the opportunities ahead: new tools that expand what creators can build, collaborative features that make teamwork feel natural, and AI systems that enhance creativity rather than diminish it. Across continents, generations, and skill levels, people are discovering WordPress as a path to learning, empowerment, and expression. The values that brought the project this far remain the ones that will carry it forward: freedom, participation, learning, and community. These aren’t abstract principles. They are lived every day in the decisions contributors make, the ideas they pursue, and the care they bring to the work. Future Events If you’re feeling inspired to revisit past moments from the project’s annual address, the State of the Word YouTube playlist offers a look back at years of community milestones and product progress. The excitement continues into 2026, with major WordPress events already on the horizon: WordCamp Asia in Mumbai, India,WordCamp Europe in Kraków, Poland, and WordCamp US in Phoenix. We hope to see you there as the community continues building what comes next. View the full article

Each WordPress release celebrates an artist who has made an indelible mark on the world of music. WordPress 6.9, code-named “Gene,” honors the American Jazz pianist Gene Harris. A piano veteran, self taught at the age of six, Harris infused mainstream jazz with elements of soul, blues, and gospel, creating a warm, signature sound that is both elegant and iconic. Harris’ bluesy jazz lived at the intersection of worlds, weaving a rich landscape of texture and mood, with a thread of soulfulness that ignited listeners. Welcome to WordPress 6.9 WordPress 6.9 brings major upgrades to how teams collaborate and create. The new Notes feature introduces block-level commenting when writing posts and pages that streamlines reviews, while the expanded Command Palette makes it faster for power users to navigate and operate across the entire dashboard. The new Abilities API provides a standardized, machine-readable permissions system that opens the door for next generation AI-powered and automated workflows. This release also delivers notable performance improvements for faster page loads and adds several practical new blocks alongside a more visual drag and drop to help creators build richer, more dynamic content. Download WordPress 6.9 “Gene” Introducing Notes: Seamless, Block-Level Collaboration Collaborate Smarter : Leave Feedback Right Where You’re Working With notes attached directly to blocks in the post editor, your team can stay aligned, track changes, and turn feedback into action all in one place. Whether you’re working on copy or refining design in your posts or pages, collaboration happens seamlessly on the canvas itself. Command Palette Throughout the Dashboard Your tools are always at hand. Access the Command Palette from any part of the dashboard, whether you’re writing your latest post, deep in design in the Site Editor, or browsing your plugins. Everything you need, just a few keystrokes away. Fit text to container Content that adapts. There’s a new typography option for text-based blocks that’s been added to the Paragraph and Heading blocks. This new option automatically adjusts font size to fill its container perfectly, making it ideal for banners, callouts, and standout moments in your design. The Abilities API Unlocking the next generation of site interactions. WordPress 6.9 lays the groundwork for the future of automation with the unified Abilities API. By creating a standardized registry for site functionality, developers can now register, validate, and execute actions consistently across any context—from PHP and REST endpoints to AI agents—paving the way for smarter, more connected WordPress experiences. Accessibility Improvements More than 30 accessibility fixes sharpen the core WordPress experience. These updates improve screen reader announcements, hide unnecessary CSS-generated content from assistive tech, fix cursor placement issues, and make sure typing focus stays put even when users click an autocomplete suggestion. Performance enhancements WordPress 6.9 delivers significant frontend performance enhancements, optimizing the site loading experience for visitors. 6.9 boasts an improved LCP (Largest Contentful Paint) through on-demand block styles for classic themes, minifying block theme styles, and increasing the limit for inline styles – removing blockages to page rendering and clearing the rendering path by deprioritizing non-critical scripts. This release comes with many more performance boosts, including optimized database queries, refined caching, improved spawning of WP Cron, and a new template enhancement output buffer that opens the door for more future optimizations. And much more For a comprehensive overview of all the new features and enhancements in WordPress 6.9, please visit the feature-showcase website. Check out What’s New Learn more about WordPress 6.9 Learn WordPress is a free resource for new and experienced WordPress users. Learn is stocked with how-to videos on using various features in WordPress, interactive workshops for exploring topics in-depth, and lesson plans for diving deep into specific areas of WordPress. Read the WordPress 6.9 Release Notes for information on installation, enhancements, fixed issues, release contributors, learning resources, and the list of file changes. Explore the WordPress 6.9 Field Guide. Learn about the changes in this release with detailed developer notes to help you build with WordPress. The 6.9 release squad Every release comes to you from a dedicated team of enthusiastic contributors who help keep things on track and moving smoothly. The team that has led 6.9 is a cross-functional group of contributors who are always ready to champion ideas, remove blockers, and resolve issues. Release Lead: Matt Mullenweg Release Coordination: Akshaya Rane, Amy Kamala Tech Leads: David Baumwald, Ella van Durpe, Héctor Prieto Design Lead: Francisco Vera Triage Leads: Aki Hamano, Ryan Welcher Test Leads: Jonathan Bossenger, Krupa Nanda Thank you, contributors The mission of WordPress is to democratize publishing and embody the freedoms that come with open source. A global and diverse community of people collaborating to strengthen the software supports this effort. WordPress 6.9 reflects the tireless efforts and passion of more than 900+ contributors in countries all over the world. This release also welcomed over 279 first-time contributors! Their collaboration delivered more than 340 enhancements and fixes, ensuring a stable release for all – a testament to the power and capability of the WordPress open source community. 2046 · Aakash Verma · Aaron Jorbin · Aaron Robertshaw · Aarti Chauhan · Aashish Sharma · aatospaja · Abdur Rahman Emon · Abu Hurayra · Adam Harley (Kawauso) · Adam Silverstein · Adam Zieliński · Aditya Bansode · Aditya Dhade · aditya shah · Aditya Singh · aduth · agulbra · Ahmed · ajaxStardust · Ajit Bohra · Akanshu Singh · Akeda Bagus · Aki Hamano · Akira Tachibana · Akramul Hasan · Akshat Kakkad · Akshay Dhere · Akshaya Rane · Albert Juhé Lluveras · alejandrogonzalvo · Alex Cuadra · Alex Lende · Alex Lion (阿力獅) · Alex Stine · Alexandre Buffet · Alexei Samarschi · Alexis Pandaan · alordiel · Alvaro Gómez · Amber Hinds · Amin · Aminul Islam · Aminul Islam Alvi · Amit Bhosale · Amy Kamala · Anatol Broder · Anders Norén · Andrea Fercia · Andrea Roenning · Andrei Draganescu · Andrew Hoyer · Andrew Nacin · Andrew Ozz · Andrew Serong · André Maneiro · Andy Fragen · Anita C · Ankit K Gupta · Ankit Kumar Shah · Ankit Panchal · Anne McCarthy · Anne-Mieke Bovelett · Anton Vlasenko · Antonio Sejas · Anuj Singh · Anveshika Srivastava · apmeyer · Ari Stathopoulos · Arkadiusz Rzadkowolski · Armando · Artemio Morales · Arthur Chu · Artur Piszek · ArtZ91 · asafm7 · asdofindia · Ashish Kumar (Ashfame) · Ashraful Haque Akash · askapache · Aslam Doctor · Aurooba Ahmed · aut0poietic · Axel DUCORON · Ayesh Karunaratne · Azhar Deraiya · Béryl de La Grandière · bartnv · bchecketts · Beee · Ben Dwyer · Benazeer · Benjamin Denis · Benjamin Zekavica · Benny · Benoit Chantre · Bernhard Kau · Bernhard Reiter · bernhard-reiter · bgermann · bhattaganesh · Bhavesh Desai · BiDbMAK · Bigul Malayi · Birgir Erlendsson (birgire) · Birgit Pauli-Haack · Bishal Shrestha · bobbyleenoblestudios · BogdanUngureanu · bonger · Boro Sitnikovski · Brad Griffin · brad hogan · Brad Jorsch · bradshawtm · Brandon Hubbard · Brandon Kraft · Brandon Zhang · Brennan Goewert · brhodes · Brian Alexander · Brian Coords · Brian Gardner · Brian Haas · brumack · Bryan Schneidewind · bshuchter · burnuser · byteninjaa0 · Cédric Chevillard · Callum Bridgford-Whittick · Calvin Alkan · Carlo Cannas · Carlos Bravo · Carlos G. P. · CarlSteffen · Carolina Nymark · Carolina Romo · Catalin Ciobanu · catgofire · cbirdsong · ccharel · Chad Butler · Chad Chadbourne · Chakrapani Gautam · Chi-Hsuan Huang · Chillifish · ChloeD · Chouby · Chris Zarate · chriscct7 · chrisdotdotdot · chrismattix · christinecooper · Christoph Daum · Christy Nyiri · cikrimcin · Ciprian Popescu · cjhaas · ckoerner · claimableperch · Code Amp · codebuddy · coleatkinson1 · Colin Stewart · ColinD · Cooper Dalrymple · Coralie Tixeront · Corey Salzano · Corey Worrell · Cornwell · Cory Hughart · Courtney Robertson · cucocreative · Cullen Whitmore · Cyrille37 · Daan van den Bergh · Dakota Chichester · damchtlv · Damir · Damon Cook · Dan Cameron · Dan Waldschmidt · Daniel Bachhuber · Daniel Iser · Daniel Richards · Daniele Scasciafratte · daniellacatus · danielmorell · Danny Schmarsel · dannyreaktiv · Darren Ethier (nerrad) · Darshit Rajyaguru · Dave Ryan · daveguitaruno · David Aguilera · David Arenas · David Artiss · David Baumwald · David Calhoun · David Herrera · David Levine · David Perez · David Riviera · David Smith · DavidB · dawidadach · Dean Sas · Debabrata Karfa · DEBARGHYA BANERJEE · Denis de Bernardy · Denis Žoljom · Dennis Ploetner · Dennis Snell · Dennys Dionigi · Densi Nakum · derekherman · Devasheesh Kaul · Dhananjay Kuber · Dhrumil Kumbhani · Dhruval Shah · Dhruvang21 · Dhruvik Malaviya · diebombe · Dilip Bheda · Dilip Modhavadiya · Dion Hulse · divinenephron · dj.cowan · Dominik Schilling · dominiquepijnenburg · donalirl · doughamlin · DougMelvin · drawcard · dretzlaff · Drew Jaynes · Drivingralle · dsawyers · dustintechsmith · eclev91 · eduwass · Ehti · elialum · Eliezer Peña · Ella van Durpe · Elvis Morales · emaildano · Emerson Maningo · Emilie LEBRUN · Emran Ahmed · Enaan Farhan · Enrico Battocchi · Enrique Sánchez · epeicher · Eric · Eric Andrew Lewis · Erick Hitter · Erik · Erik Joling · Eshaan Dabasiya · ethanscorey · Evan Mullins · Even Tobiesen · Fabian Kägy · Fabian Todt · Faisal Ahammad · Faisal Alvi · fakhriaz · Falguni Desai · Felix Arntz · Felix Renicks · Fellyph Cintra · Florian TIAR · Francisco Vera · FrogDesk Strategy · Fumiki Takahashi · Gael Denysiak · Gajendra Singh · Gan Eng Chin · Garrett Hyder · Gary Jones · Gary Pendergast · Gaurang Dabhi · Gautam Mehta · Gennady Kovshenin · George Mamadashvili · George Stephanis · Georgi Stoyanov · gernberg · giuliorubelli · Glen Davies · Gopal Krishnan · Grant M. Kinney · Greg Ziółkowski · Guido · Guido Scialfa · Guillaume TURPIN · Gulamdastgir Momin · H. Adam Lenz · H. Kabir · hanimbarek · hanneslsm · Hans-Gerd Gerhards · Hardik Raval · Hareesh S · Harsh Gajipara · Harshal Kadu · harshbhonsle08 · harshdeepgill · Harun · Helen Hou-Sandi · HelgaTheViking · Hidenori ISHIKAWA · Hilay Trivedi · Himani Panchal · Himanshu Pathak · Hiroshi Sato · Hit Bhalodia · Hitendra Chopda · Hitesh Talpada · Hozefa Saleh · Hrohh · hugod · hugosolar · humanify · huubl · Huzaifa Al Mesbah · Héctor Prieto · Ian Dunn · ignatiusjeroe · Igor Radovanov · ikriv · imokweb · Imran · Indira Biswas · Ipstenu (Mika Epstein) · Iqbal Hossain · Isabel Brison · Ishika Bansal · Ivan Ottinger · Jabe · Jacob Cassidy · Jagir Bahesh · Jaimin Prajapati · Jakaria Istauk · Jake Spurlock · jakeparis · James Koster · James LePage · James Monroe · James Sansbury · James Titus · Jamie · Jamie Burchell · Jamie Marsland · janthiel · Jarda Snajdr · jarekmorawski · Jarkko Saltiola · Jason Adams · Jason LeMahieu (MadtownLems) · Jason Sauerwald · Javier Casares · Jay McPartland · Jayaram · Jaydip · Jean-Baptiste Audras · Jeff Chi · Jeff Matson · Jeff Ong · Jeff Paul · Jeffrey de Wit · Jeffro · jeflopo · Jenny Dupuy · Jeremiah Bratton · Jeremy Felt · Jeremy Massel · Jeroen Schmit · jeryj · Jesin A · jessedyck · Jessica Lyschik · Jigar Bhanushali · Jigar Panchal · jikamens · jnweaver · Joan Namunina · JoAnne Obata · JochenT · jodamo5 · Joe Dolson · Joe Hoyle · Joe McGill · Joen Asmussen · Johannes Jülg · John Blackbourn · John Brand · John Godley · John James Jacoby · John Parris · John Regan · JohnVieth · Jon Surrell · Jonathan Bossenger · Jonathan Champ · Jonathan Desrosiers · Joni Erkkilä · Jonny Harris · Jono Alderson · jordesign · Jorge Costa · Jos Velasco · Joseph Scott · Josh Habdas · Joshua Goode · jrmd · Juan Aldasoro · Juan Cook · JuanMa Garrido · juliengardair · Juliette Reinders Folmer · Justin Ahinon · Justin Tadlock · Jyotirmoy Roy · K. Adam White · Kai Hao · Kailey (trepmal) · Kaito Hanamori · Kakoma · Kalpesh · Karin Christen · Karol Manijak · Karthick Murugan · Karthikeya Bethu · Kaspars · Kat Hagan · Kateryna K. a11n · Kathryn Presner · Katrina Massey · Kausar Alam · Kaushik Domadiya · Kawshar Ahmed · kaygee79 · Kazuto Takeshita · Kelly Choyce-Dwan · Kelly Hoffman · Kelly Mears · Kerfred · Kerry Liu · kesselb · Kevin Leary · kgagne · Khoi Pro · Khushi Patel · killerbishop · Kingsley Felix · Kira Schroder · Kishan Jasani · kitchin · Kjell Reigstad · kkmuffme · Kleor · Knut Sparhell · Konstantin Obenland · Konstantinos Xenos · kpapazov · kprocyszyn · krishaamer · Krunal Bhimajiyani · Krupa Nanda · kshaner · kub1x · kubiq · kunalpuri123 · Kush Sharma · Kushagra Goyal · Lachezar Gadzhev · lakrisgubben · Lakshyajeet Singh Goyal · Lalit Kumawat · Lance Willett · Laura Byrne · Lauri Saarni · ldanielgiuliani · Lee Willis · leedxw · leemon · Lena Morita · Leonidas Milosis · Levin Baria · lgseo · LilGames · liviopv · logiclink · LogicRays Technologies · lordandy1984 · Lovro Hrust · Lucas Martins · Luigi Teschio · luisherranz · LukasFritzeDev · Lukasz · Luke Cavanagh · maccyd · Madhavi Shah · Madhu Dollu · Maggie Cabrera · Maikuolan · manfcarlo · manhatthien98 · Manuel Camargo · Manzoor Wani · maorb · Marc · Marc Armengou · Marcio Duarte · Marco Ciampini · Marcus · Marcus Kazmierczak · marian1 · Marie · Marin Atanasov · Mario Santos · mariohamann · mariushosting · Marty · MartyThornley · Mary Baum · Mary Hubbard · Mat Lipe · mathiscode · Matias Benedetto · Matias Ventura · Matt Mullenweg · Matt Robinson · Matt West · Matteo Enna · Matthias Pfefferle · mattryanwalker · Max Schmeling · Maxime Pertici · Mayank Tripathi · Mayur Prajapati · Md Abdullah Al Arif · Md Abdullah Al Fahad · Md Abul Bashar · MD ISMAIL · MD Kawsar Chowdhury · Md Masum Molla Alhaz · Md Obidullah (obiPlabon) · Md Rashed Hossain · Md Sabbir Hossain · Md. Najmul Islam · Md.Mehedi Hasan · mdmoreau · mdviralsampat · Meet Makadia · megane9988 · Meher Bala · Mel Choyce-Dwan · Micha Krapp · Michael Burridge · Michael Keck · Michael Nelson · Michael Sumner · michaelreetz · Michal Czaplinski · Michelle Schulp Hunt · Miguel Fonseca · Miguel Lezama · Mikael Korpela · Mike · Mike Fitzpatrick · Mike Hansen · Mike Jolley · Mike McAlister · Mike Ritter · Mikin Chauhan · Milan Ricoul · Minal Diwan · Miroku · missveronica · Mitchell Austin · mkeck · mlaetitia1986 · mleray · mleraygp · Mobarak Ali · Mohammad Rockeybul Alam · Mohammed Kateregga · Moses Cursor Ssebunya · mrwweb · mtg169 · mujuonly · Mukesh Panchal · Mukul Singh · Mumtahina Faguni · Núria Nadal i Rovira · n8finch · Naman Vyas · NANI SAMIREDDY · Narendra Sishodiya · Naresh Bheda · Nasim Miah · Naveen Dwivedi · Navneet Kaur · Nazar Hotsa · Nazmul Hosen · Ned Zimmerman · nexbridge · Nextendweb · Neycho Kalaydzhiev · Nick · Nick · Nick Diego · Nick Halsey · nickbrazilian · nickjbedford · nickpagz · nickwilmot · Nico · nidhidhandhukiya · Niels Lange · nigelnelles · Nik Tsekouras · Nikan Radan · Nikunj Hatkar · Nimesh · Nino Mihovilic · Ninos · Noah Allen · Noel Santos · Noruzzaman · nosilver4u · oceantober · oferlaor · okat · Okawa Yasuno · Olga Gleckler · Oliver Campion · Omar Alshaker · Ophelia Rose · Optimizing Matters · owi · Paal Joachim Romdahl · Pablo Honey · Palak Patel · Paragon Initiative Enterprises · Parin Panjari · Parth vataliya · Partho Hore · Pascal Birchler · Patel Jaymin · Patricia BT · Patrick Lumumba · Patrick Piwowarczyk · Paul · Paul Bearne · Paul Biron · Paul Bonneau · Paul Kevan · Paulo Trentin · paulstanos · pcarvalho · Pedro Figueroa · Per Egil Roksvaag · Peter Ingersoll · Peter Westwood · Peter Wilson · petitphp · Philip John · Philip Sola · Philipp Bammes · Phill · piskvorky · Pooja Bhimani · poojapadamad · porg · prab18hat · Praful Patel · Pranjal Pratap Singh · Prasad Karmalkar · prasadgupte · Prashant Baldha · Pratik Londhe · Presskopp · prettyboymp · puggan · quentinr64600 · Rachel Baker · Rafiqul Islam · Raluca · Ramanan · Rami Yushuvaev · Ramon Ahnert · Ramon Corrales · Ramon James · Ravi Chudasama · Ravi Gadhiya · rcrdortiz · Rehan Ali · Rejaul Alom Khan · Remy Perona · Renato Alves · renishsurani · retrofox · Rezwan Shiblu · Riad Benguella · riadev · Rich Tabor · Richard Korthuis · Riddhi Dave · Rinat · Rinkal Pagdar · Rishabh Gupta · Rishav Dutta · Rishit Gupta · Risto Jovanovic · Ritoban · Robert Anderson · Robert Chapin · Robert Ghetau · Robert O'Rourke · Robmcclel · Rodrigo Primo · roelof · Rolly Bueno · Ronak prajapati · room34 · Rostislav Wolný · Rotem Gelbart · Rufaro Madamombe · Rutvik Bhambhi · Ryan McCue · Ryan Welcher · S Page · Sören Wünsch · Sabbir Ahmed · Sabbir Sam · SACHINRAJ CP · Sahil Jadhav · Sainath Poojary · Sajjad Hossain Sagor · sakibmoon · Sam · sam_a · Samir Malpande · Sampat Viral · Samuel Paget · Samuel Wood (Otto) · Sandeep Dahiya · Sandip Sinh · Sandy McFadden · Sarah Norris · sarah semark · Sarthak Nagoshe · Satish Prajapati · saurabh.dhariwal · Saxon Fletcher · scholdstrom · Scott Buscemi · Scott Kingsley Clark · Scott Taylor · scribu · Sebastian Pisula · Seif Radwane · Sergey Biryukov · Seth Rubenstein · SH Sajal Chowdhury · Shadi G شادي جـ · Shail Mehta · Shalin Shah · Shane Muirhead · Shashank Jain · Shashank Shekhar · Shazzad Hossain Khan · Sheri Grey · Shipon Karmakar · Shreya Shrivastava · Shubham Patil · Shyamsundar Gadde · sidharthpandita · siliconforks · Silpa TA · simonefontana · Slava Abakumov · smerriman · Sneha Patil · Sophie Dimitrov · Sourabh Jain · Sourav Pahwa · Soyeb Salar · Spenser Hale · spstrap · Sridhar Katakam · stankea · Stanko Metodiev · staurand · Stefan Pasch · Stefan Velthuys · Stephen Bernhardt · Stephen Harris · Steve Dufresne · strarsis · Subrata Sarkar · Sudip Dadhaniya · Sujan Sarkar · Sukhendu Sekhar Guria · Sumit Bagthariya · SunilPrajapati · sunnykasera · sunyatasattva (a11n) · supernovia · SuzuKube · svedish · Svetoslav Marinov · Sybre Waaijer · syhussaini · T4ng · Taco Verdonschot · Takashi Irie · Takuro · Tammie Lister · tatof · tecnogaming · Tetsuro Higuchi · tharsheblows · thelmachido a11n · ThemeAWESOME · theMikeD · Thomas Kräftner · Thorsten Frommen · Till Krüss · Tim Havinga · Tim Sheehan · Timo Tijhof · Timothée Brosille · Timothée Moulin · Timothy Jacobs · TJarrett · Tobias Bäthge · Tobias Zimpel · tobifjellner (Tor-Bjorn “Tobi” Fjellner) · Tom de Visser · Tom J Nowell · Tomoki Shimomura · Toni Viemerö · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · Travis Smith · traxus · Trevor Mills · tristanleboss · Troy Chaplin · Trupti Kanzariya · tsteel · Tung Du · Tushar Bharti · Tushar Patel · Tussendoor B.V. · Ugyen Dorji · Umesh Nevase · Umesh Singh · Unsal Korkmaz · upadalavipul · Utsav Ladani · Utsav tilava · Valentin Grenier · Vape tsimshatsui · vbbp · Vedansh Mishra · Vegard S. · vgnavada · Vicente Canales · vidugupta · Vijendra Jat · Viktor Szépe · Vinit · Vipul Ghori · Vipul Gupta · Vipul Patil · Vishit Shah · vladimiraus · vortfu · Vrishabh Jasani · Walter Ebert · WebMan Design | Oliver Juhas · websupporter · webwrotter · Weston Ruter · whaze · widhy980 · Will Skora · wplmillet · xate · xavilc · xerpa43 · xipasduarte · Yagnik Sangani · Yash · Yash B · Yash Jawale · Yogesh Bhutkar · YogieAnamCara · Yui · Zebulan Stanphill · Zeel Thakkar · Zunaid Amin · Łukasz Strączyński · 耗子 More than 71 locales have fully translated WordPress 6.9 into their language. Community translators are working hard to ensure more translations are on their way. Thank you to everyone who helps make WordPress available in 200+ languages. Last but not least, thanks to the volunteers who contribute to the support forums by answering questions from WordPress users worldwide. Get involved Participation in WordPress goes far beyond coding. And learning more and getting involved is easy. Discover the teams that come together to Make WordPress and use this interactive tool to help you decide which is right for you. View the full article

The third Release Candidate (“RC3”) for WordPress 6.9 is ready for download and testing! This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC3 on a test server and site. Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.9 is the highest quality possible. You can test WordPress 6.9 RC3 in four ways: PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the RC3 version (zip). and install it on a WordPress website.Command LineUse this WP-CLI command: wp core update --version=6.9-RC3WordPress PlaygroundUse the 6.9 WordPress Playground instance to test the software directly in your browser. No setup is required – just click and go! The scheduled final release date for WordPress 6.9 is December 2, 2025. The full release schedule can be found here. Your help testing RC versions is vital to making this release as stable and powerful as possible. Please continue checking the Make WordPress Core blog for 6.9-related posts in the coming weeks for more information. What’s in WordPress 6.9 RC3? Want to look deeper into the details and technical notes for this release? Take a look at the WordPress 6.9 Field Guide. For technical information related to issues addressed since RC2, you can browse the following links: Gutenberg commits for 6.9 since November 18 Closed WordPress Core Trac tickets since November 18 How you can contribute WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can get involved with the world’s most popular open source web platform, regardless of your technical expertise. Get involved in testing Testing for issues is crucial to the development of any software. It’s also a meaningful way for anyone to contribute. Your help testing the WordPress 6.9 RC3 prerelease 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 important. This detailed guide will walk you through testing features in WordPress 6.9. For those new to testing, follow this general testing guide for more details on getting set up. If you encounter an issue, please report it to the Alpha/Beta/RC area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs. Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.. Update your theme or plugin For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users. Thanks for continuing to test your themes and plugins with the WordPress 6.9 prereleases. If you haven’t yet, please conclude your testing and update the “Tested up to” version in your theme and plugin readme files to 6.9. If you find compatibility issues, please post detailed information in the support forum. Test on your hosting platforms Web hosts provide vital infrastructure for supporting WordPress and its users. Testing on hosting systems helps inform the development process while ensuring that WordPress and hosting platforms are fully compatible, free of errors, optimized for the best possible user experience, and that updates roll out to customer sites without issue. Want to test WordPress on your hosting system? Get started with configuring distributed hosting tests here. Help translate WordPress Do you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? मराठी? ಕನ್ನಡ? You can help translate WordPress into more than 100 languages. An RC3 haiku Some folks make money, some folks make time to travel, and we Make WordPress. Props to @akshayar, @davidbaumwald, @westonruter, @ellatrix, @mobarak and @tacoverdo for proofreading and review. View the full article

The second Release Candidate (“RC2”) for WordPress 6.9 is ready for download and testing! This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC2 on a test server and site. Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.9 is the best it can be. You can test WordPress 6.9 RC2 in four ways: PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream).Direct DownloadDownload the RC2 version (zip) and install it on a WordPress website.Command LineUse the following WP-CLI command: wp core update –version=6.9-RC2WordPress PlaygroundUse the 6.9 RC2 WordPress Playground instance to test the software directly in your browser without the need for a separate site or setup. The scheduled final release date for WordPress 6.9 is December 2, 2025. The full release schedule can be found here. Your help testing RC versions is vital to making this release as stable and powerful as possible. Please continue checking the Make WordPress Core blog for 6.9-related posts in the coming weeks for more information. What’s in WordPress 6.9 RC2? Get a recap of WordPress 6.9’s highlighted features in the Beta 1 announcement. For more technical information related to issues addressed since RC1, you can browse the following links: GitHub commits for 6.9 since November 11 Closed Trac tickets since November 11 Want to look deeper into the details and technical notes for this release? These recent posts cover some of the latest updates: Notes Feature in 6.9 Abilities API in WordPress 6.9 WordPress 6.9 Frontend Performance Field Guide Interactivity API’s client navigation improvements in WordPress 6.9 Block Bindings improvements in WordPress 6.9 Changes to the Interactivity API in WordPress 6.9 Consistent Cache Keys for Query Groups in WordPress 6.9 DataViews, DataForm, et al. in WordPress 6.9 Preparing the Post Editor for Full iframe Integration Theme.json Border Radius Presets Support in WordPress 6.9 Heading Block CSS Specificity Fix in WordPress 6.9 Miscellaneous Developer-focused Changes in 6.9 Modernizing UTF-8 support in WordPress 6.9 How you can contribute WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise. Get involved in testing Testing for issues is crucial to the development of any software. It’s also a meaningful way for anyone to contribute. Your help testing the WordPress 6.9 RC2 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 important. This detailed guide will walk you through testing features in WordPress 6.9. For those new to testing, follow this general testing guide for more details on getting set up. 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 bug report. You can also check your issue against a list of known bugs. Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the#core-test channel on Making WordPress Slack. Update your theme or plugin For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users. Thanks for continuing to test your themes and plugins with the WordPress 6.9 beta releases. If you haven’t yet, make sure to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 6.9. If you find compatibility issues, please post detailed information to the support forum. Test on your hosting platforms Web hosts provide vital infrastructure for supporting WordPress and its users. Testing on hosting systems helps inform the development process while ensuring that WordPress and hosting platforms are fully compatible, free of errors, optimized for the best possible user experience, and that updates roll out to customer sites without issue. Want to test WordPress on your hosting system? Get started with configuring distributed hosting tests here. Help translate WordPress Do you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? मराठी? ಕನ್ನಡ? You can help translate WordPress into more than 100 languages. This release milestone (RC2) also marks the hard string freeze point of the 6.9 release cycle. An RC2 haiku A calm hillside sighs, Work of many now complete — RC2 stays true. Props to @amykamala, @annezazu, @davidbaumwald and @joedolson for proofreading and review. View the full article

Webpros has released an update for EasyApache 4! Take a look at some highlights below, and then join us on the cPanel Community Forums, Discord, or Reddit to talk about this update and much more. If you have additional questions, feel free to reach out on one of our social channels. What’s New in This Release Apache … The post EasyApache4 v25.35 Maintenance Release first appeared on cPanel Newsroom.View the full article

The first Release Candidate (“RC1”) for WordPress 6.9 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 evaluate RC1 on a test server and site. WordPress 6.9 RC1 can be tested using any of the following methods: PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the RC1 version (zip) and install it on a WordPress website.Command LineUse this WP-CLI command: wp core update --version=6.9-RC1WordPress PlaygroundUse the 6.9 RC1 WordPress Playground instance to test the software directly in your browser. No setup is required – just click and go! The scheduled final release date for WordPress 6.9 is 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. Please continue checking the Make WordPress Core blog for 6.9-related posts in the coming weeks for more information. What’s in WordPress 6.9 RC1? Check out the Beta 1 announcement for details on WordPress 6.9. You can browse the technical details for all issues addressed since Beta 4 using these links: Gutenberg commits for 6.9 since November 7, 2025 Core commits for 6.9 since November 7, 2025 Closed Trac tickets since November 7, 2025 Want to know more about this release? Here are some highlights: Site Editor improvements and Refined content creation Ability to hide blocks New blocks Notes on blocks Universal command palette in wp-admin Developer updates Updates to dataviews and dataforms components New abilities API Updates to interactivity API Updates to block binding API Performance Improvements Improved script and style handling Optimized queries and caching Added ability to handle “fetchpriority” in ES Modules and Import Maps Standardizing output buffering The final release is on track for December 2nd. As always, a successful release depends on your confirmation during testing. So please download and test! How you can contribute WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise. Get involved in testing Testing for issues is crucial to the development of any software. It’s also a meaningful way for anyone to contribute. Your help testing the WordPress 6.9 RC1 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 important. This detailed guide will walk you through testing features in WordPress 6.9. Calls for testing Thank you to everyone who helps test the following enhancements and bug fixes: Accordion Block Ability to Hide Blocks Classic themes loading block styles on demand Modified notes notifications Abilities API 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 bug report. You can also check your issue against a list of known bugs. Thank you to everyone who helps with testing! Update your theme or plugin For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users. Thanks for continuing to test your themes and plugins with the WordPress 6.9 beta releases. With RC1, you’ll want to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 6.9. If you find compatibility issues, please post detailed information to the support forum. Test on your hosting platforms Web hosts provide vital infrastructure for supporting WordPress and its users. Testing on hosting systems helps inform the development process while ensuring that WordPress and hosting platforms are fully compatible, free of errors, optimized for the best possible user experience, and that updates roll out to customer sites without issue. Want to test WordPress on your hosting system? Get started with configuring distributed hosting tests here. Thank you to all web hosts who help test WordPress! Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack. An RC1 haiku As the sun rises, RC1 breaks its cocoon and emerges strong. Props to @akshayar, @davidbaumwald, @jeffpaul, @desrosj, @westonruter, @ellatrix, @priethor, @krupajnanda and @cbravobernal for proofreading and review. View the full article

cPanel, L.L.C. has released an update for EasyApache 4! Take a look at some highlights below, and then join us on the cPanel Community Forums, Discord, or Reddit to talk about this update and much more. If you have additional questions, feel free to reach out on one of our social channels. Packages Updated ea-cpanel-tools ea-freetds ea-nginx … The post EasyApache4 v25.34 Maintenance Release first appeared on cPanel Newsroom.View the full article

WordPress 6.9 Beta 3 is available for download and testing! This beta version of the WordPress software is still under development. Please don’t install, run, or test this version of WordPress on production or mission-critical websites. Instead, you can evaluate Beta 3 on a test server and site. WordPress 6.9 Beta 3 can be tested using any of the following methods: PluginInstall and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.)Direct DownloadDownload the Beta 3 version (zip) and install it on a WordPress website.Command LineUse this WP-CLI command: wp core update --version=6.9-beta3WordPress PlaygroundUse the 6.9 Beta 3 WordPress Playground instance to test the software directly in your browser. No setup is required – just click and go! The final release of WordPress 6.9 is scheduled for December 2, 2025, and the 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! Please continue checking the Make WordPress Core blog for 6.9-related posts in the coming weeks for more information. Find out what’s new in WordPress 6.9: Read the Beta 1 announcement for details and highlights. How to test this release Your help testing the WordPress 6.9 Beta 3 version is key to ensuring that everything in the 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 provides a walk through on 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 bug report. You can also check your issue against a list of known bugs. Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack. Beta 3 updates and highlights WordPress 6.9 Beta 3 contains more than 80 updates and fixes since the Beta 2 release. Each beta cycle focuses on bug fixes, and more are on the way with your testing! You can browse the technical details for all issues addressed since Beta 2 using these links: Gutenberg commits for 6.9 since October 28, 2025 Closed Core Trac tickets for 6.9 since October 28, 2025 Comparing commit changes in Core Trac for 6.9 since October 28, 2025 A Beta 3 haiku Code is poetry, and poetry is magic. So code is magic. Props to @akshayar , @jeffpaul, @krupajnanda, @mosescursor, and @westonruter for proofreading and review. View the full article

We want to provide you with advance notice of an important change to cPanel & WHM. Beginning with version 134 (scheduled for March 2026), cPanel & WHM will discontinue support for Rocky Linux 8 and Rocky Linux 9. Why This Change? We regularly evaluate our supported operating systems to ensure … The post Rocky Linux Support Deprecation Announcement first appeared on cPanel Newsroom.View the full article

Webpros has released an update for EasyApache 4! Take a look at some highlights below, and then join us on the cPanel Community Forums, Discord, or Reddit to talk about this update and much more. If you have additional questions, feel free to reach out on one of our social channels. ea-tomcat101 EA-13223: Update ea-tomcat101 from v10.1.47 … The post EasyApache4 v25.33 Maintenance and Security Release first appeared on cPanel Newsroom.View the full article