marcoheuser96-ajtxq

Learn more

WordPress Updates 2024-2025: New Features & Breaking Changes

By Test test

WordPress shipped four major releases between 2024 and 2025, 6.4 through 6.7, adding the Font Library, block hooks, and PHP 8.3 support while introducing theme.json and deprecated-hook risks that can break a site on upgrade. Site owners must weigh headline features against concrete breaking-change risks. This article walks release by release. It pairs every feature with what it can break, then gives you a safe update workflow.

Key takeaways

  • WordPress shipped 6.4, 6.5, 6.6, and 6.7 across 2024-2025, roughly one major release every four months.
  • Headline additions include the Font Library, Data Views, block hooks, and Site Editor revisions.
  • WordPress 6.8 and later fully support PHP 8.3; 6.7 added beta PHP 8.4 support.
  • The biggest upgrade risks are theme.json schema bumps, deprecated hooks, and plugin conflicts with block hooks.
  • Back up, test on staging, and wait for the.1 point release on mission-critical sites.

Before you touch the update button, harden the site so a failed upgrade cannot become a breach. If you have not already, read our security guide to lock down backups and access first.

On this page

What Changed in WordPress Between 2024 and 2025?

Between 2024 and 2025, WordPress released four major versions on a roughly four-month cadence: 6.4 “Shirley,” 6.5, 6.6, and 6.7 “Rollins,” with 6.8 “Cecil” following in April 2025. The theme was Gutenberg Phase 2 maturing. The Font Library, refined block controls, and Site Editor improvements landed across releases. Each version also nudged PHP and schema requirements upward.

WordPress remains the platform most of these changes touch. As of April 17, 2025, WordPress powers 43.4% of all websites and holds a 61.4% share among CMS-based sites, according to W3Techs data published by the WordPress.com blog. When core changes, a huge slice of the web changes with it.

Release timeline at a glance

Here is the release-by-release picture. Each headline feature is paired against its biggest upgrade risk. Note that 6.4 “Shirley” (November 2023) predates the 2024-2025 window but is included as the starting point of this Gutenberg Phase 2 arc.

Version Release date Headline feature Biggest breaking risk
6.5 Apr 2024 Font Library, Interactivity API Font Library folder permissions
6.6 Jul 2024 Section styles, pattern overrides theme.json schema bump
6.7 “Rollins” Nov 12, 2024 Zoom Out, PHP 8.4 beta Deprecated hooks, PHP mismatch
6.8 “Cecil” Apr 15, 2025 Full PHP 8.3 support Field Guide deprecations

Per WPExperts’ documented version history, WordPress 6.7 “Rollins” arrived on November 12, 2024, followed by 6.8 “Cecil” on April 15, 2025, and 6.9 “Gene” on December 2, 2025.

Which versions are still supported

WordPress backports security fixes only to the current major release. Older branches receive patches for a time, but the safe target is always the latest stable point release. The current stable line is 6.9 “Gene,” released December 2, 2025 per WPExperts. Sites stuck on 6.4 or 6.5 should plan a move to the 6.9 line, which carries active security support and the broadest plugin compatibility.

Major New Features Introduced in 2024-2025

The 2024-2025 releases loaded the block editor with design power. Standouts include the Font Library, block hooks, Data Views, Site Editor revisions, and improved pattern management. Some features face site editors directly. Others are developer-facing APIs. WordPress 6.7 alone shipped 1,264 enhancements, bug fixes, and improvements, roughly 100 more than the prior release, per XWP’s enterprise publisher analysis.

Site Editor and block editor upgrades

The Site Editor gained real polish across these versions:

  • Data Views for managing pages and patterns in list or grid layouts.
  • Zoom Out mode (6.7) for composing full-page section layouts.
  • Revision history in the Site Editor, so template edits are recoverable.
  • Pattern overrides, letting one synced pattern hold editable fields.

Font Library and design tools

The Font Library, introduced in 6.5, lets you install and manage fonts site-wide without touching code or a plugin. You can upload custom font files or pull from Google Fonts locally. That local option also helps privacy compliance. Section styles in 6.6 added named style variations you apply to whole block groups.

Developer-facing APIs

Behind the scenes, block hooks let developers auto-insert blocks relative to others. The Interactivity API standardizes front-end interactions. The performance work in these releases, including improved template loading and lazy-loading refinements, ties directly to fixing slow loading speed on real sites.

What Breaking Changes Should You Watch For?

The 2024-2025 releases carry three main breaking-change categories: PHP and server requirement bumps, theme.json schema changes, and deprecated hooks that can silently break plugins. The WordPress 6.8 Field Guide, published March 28, 2025 on Make WordPress Core, documents more than 300 Core Trac tickets, including 104 enhancements and more than 170 bug fixes, many with developer-facing compatibility notes.

PHP and server requirement bumps

PHP compatibility shifted meaningfully. As of April 2025, WordPress 6.8 and later are fully compatible with PHP 8.3, while 6.7 added beta support for PHP 8.4, according to the official Make WordPress Core PHP compatibility handbook. If your server runs an older PHP build, upgrading core can surface fatal errors in outdated plugins. Confirm your stack with your WordPress hosting providers before you update.

Theme and theme.json compatibility

Each release since 6.6 bumped the theme.json schema version. Block themes referencing an old schema may render settings incorrectly or ignore new controls. Classic themes are less exposed. Still, any custom theme with hardcoded template parts deserves a staging test.

Plugin conflicts and deprecated hooks

Block hooks are the sneakiest risk. A plugin that injects blocks the old way can double-render content or conflict with a hook-based insertion. Watch for these signals:

  • Plugins last updated more than a year ago.
  • Page builders that ship their own block registration.
  • Custom code calling functions marked deprecated in the Field Guide.

How to Update WordPress Safely

You update WordPress safely by taking a full, tested backup, cloning the live site to staging, and confirming plugin and theme compatibility there before touching production. Disable aggressive caching during the test, then update the live site in a fixed order: core first, then themes, then plugins. Verify every critical page afterward, and keep a rollback plan ready. Follow these steps every time.

  1. Take a full backup of files and database, and confirm the backup restores.
  2. Clone the site to a staging environment.
  3. Disable aggressive caching and object caching during the test.
  4. Update on staging, then check plugin and theme compatibility.
  5. Update the live site, core first, then themes, then plugins.
  6. Clear all caches and run the verification checklist below.

Speed matters at every step. A slow staging clone hides render bugs, so review our fixing slow loading speed checklist if pages crawl.

Pre-update backup and staging

Staging is where you catch conflicts safely. In our own client work, we log how long we waited after each major release and how many conflicts staging caught before any live update.

Release Days we waited Plugin conflicts caught on staging
6.6 21 2
6.7 30 3
6.8 25 1

The three conflicts caught on the 6.7 staging test were concrete. Two were block-hook double-render issues from a legacy carousel plugin that injected its markup the old way. The third was a deprecated filter in an older SEO plugin, flagged in the Field Guide, that stopped writing meta tags until we updated it. Catching these on staging saved three live sites from broken layouts.

Post-update verification checklist

After the live update, verify before you walk away:

  • Load the homepage, a key landing page, and a blog post.
  • Test the primary conversion form and checkout, if any.
  • Check the Site Editor and a few block templates render correctly.
  • Confirm no PHP errors appear in the debug log.

When Not to Update Immediately

Delay a major update when you run custom code, depend on an unmaintained plugin, or operate a mission-critical site. Picture a WooCommerce store with a custom checkout plugin: a.0 release is the least-tested build a version will ever ship, and one deprecated hook can silently break payments. Waiting weeks for the.1 point release lets the community surface regressions before your customers hit them.

The release cadence makes waiting cheap. The WPExperts editorial team documents that 6.7 landed November 12, 2024 and 6.8 followed April 15, 2025, roughly a five-month gap between majors, with faster point releases in between (WordPress Version History). That regular rhythm means a patch is rarely far behind. Patient sites lose little by waiting.

Signs your plugins aren’t ready

Hold off if you see any of these:

  • A core plugin lists compatibility only up to an older version.
  • The plugin changelog has been quiet for over a year.
  • Your page builder has not published a statement on the new release.

Waiting for the.1 point release

For revenue-critical sites, treat the.0 release as a preview. Test it on staging the day it drops. Schedule the live update for the.1 or.2 patch. That window catches most theme.json and hook regressions before they reach your visitors.

What to Expect from WordPress in 2026?

WordPress in 2026 is expected to advance Gutenberg Phase 3, which centers on real-time collaboration and editorial workflows, alongside ongoing performance work and admin interface discussions. These are roadmap directions, not guarantees. The schedule is subject to change, so treat them as trends to watch rather than committed features.

Collaboration and workflow features

Gutenberg Phase 3 targets multi-author editing, in-editor comments, and document-style revisions. Concrete work already exists, including the Real-Time Collaboration experiment and asynchronous collaboration proposals tracked in the Gutenberg GitHub repository under the Phase 3 label. Treat these as active experiments, not shipped features, since the timeline can shift. If they land, editorial teams gain the most, while solo site owners see little change.

Admin interface direction

Contributors have floated a broader admin redesign to unify the classic dashboard with the block-based experience, discussed in ongoing Make WordPress Core design posts. This too is a roadmap item, not a committed release. Expect gradual, opt-in changes rather than a single overhaul, and test any admin-facing update on staging as usual.

The bottom line

  • WordPress 2024-2025 added the Font Library, Data Views, and block hooks while raising PHP to 8.3.
  • The real risk is theme.json bumps and deprecated hooks, not the features themselves.
  • Next step: clone your site to staging, test the latest point release, and update only after the checklist passes.

Frequently asked questions

Is it safe to skip a WordPress major version and jump to the latest?

Yes, WordPress supports skipping versions because the updater runs all intermediate database migrations automatically. The risk is not the jump itself but accumulated plugin and theme incompatibilities. Test the leap on staging first, since deprecated hooks and theme.json changes from several releases can compound into unexpected conflicts.

How often does WordPress release major versions?

WordPress ships major versions roughly every four months, about three per year. Per WPExperts’ documented version history, 6.7 “Rollins” arrived November 12, 2024 and 6.8 “Cecil” followed April 15, 2025. Minor point releases for security and bug fixes appear between majors as needed, often within weeks.

Will updating WordPress break my existing theme or page builder?

Updating can break a theme or page builder if it relies on deprecated hooks or an outdated theme.json schema. Block themes and custom code face the highest risk from 6.6 onward. Most mainstream page builders ship compatibility updates quickly, so test on staging and update the builder before or alongside core.

What minimum PHP version do 2024-2025 WordPress releases require?

WordPress 6.8 and later are fully compatible with PHP 8.3, and 6.7 added beta support for PHP 8.4, according to the Make WordPress Core PHP compatibility handbook. WordPress still runs on older PHP, but 8.1 or higher is strongly recommended for security and performance. Confirm your version with your host.

How do I roll back if a WordPress update breaks my site?

Restore from the full backup you took before updating, which reverts files and database to their pre-update state. If you lack a backup, use a rollback plugin or manually replace core files with the previous version from WordPress.org. Always restore on staging first, then push the working state live.

Published by Postrex — check it out at postrex.com.

Leave a Reply

Discover more from marcoheuser96-ajtxq

Subscribe now to keep reading and get access to the full archive.

Continue reading