Applies to Joomla 7.0 (in development) · extension developers, agencies, site owners planning ahead Status checked 16 Oct 2026

Joomla 7 is not released and has no release date. It is being built, though, in public, and you can already see what kind of release it will be. This is where it stands, checked against the code rather than announcements, and what we would do now in your place.

Where Joomla 7 stands (October 2026)

Branch7.0-dev in joomla/joomla-cms, next to 6.3-dev for the next 6.x release
Version string7.0.0-alpha1-dev
PHP minimum8.3, unchanged from Joomla 6
Compatibility pluginBackward Compatibility 7 replaces version 6, and the update installs it disabled
Already removedthe PHPass password handler; Crypt classes and RadiobasicField moved to the compat plugin
Marked for removalabout 375 APIs in libraries/src tagged "will be removed in 7.0"
Expectedno official date; the two-year major cycle points to late 2027

You can check every line yourself. Clone the branch and grep, or compare it with your Joomla 6 install. We describe the setup in a Joomla 7 dev environment.

What kind of release it is

Joomla 4 was the rewrite: namespaces, DI container, new MVC, Bootstrap 5. Joomla 5 and 6 kept the old ways working next to the new ones, through compatibility plugins. Joomla 7 is the release where that bridge is meant to come down:

  • Static shortcuts: Factory::getUser(), getDbo(), getDocument(), getLanguage(), getSession() and friends, in favour of injected services.
  • Legacy plugins: method names matched to events. Plugins must implement SubscriberInterface.
  • Old MVC entry points: BaseDatabaseModel::getInstance(), Table::getInstance(), include paths, $view->get('Items').
  • CMSObject, the base class of much Joomla 1.5–3 era code.
  • Old asset APIs: $doc->addScript(), HTMLHelper::stylesheet(), the behavior/jQuery/Bootstrap framework helpers.
  • Old password hashes (MD5, PHPass) from sites that started on Joomla 1.5 or 2.5.

None of this is new to developers who followed Joomla 4+ practice. Every replacement exists since Joomla 4.x. The details per API are in Joomla 7 breaking changes.

Who is affected

You have…Joomla 7 impact
A site using only core and well-maintained extensionslow: wait for your vendors' Joomla 7 releases, then upgrade like 5 → 6
Custom extensions written before 2022high: most use Factory::get*, legacy plugins and $this->get() in views
A template with $doc->addScript() or old overridesmedium: the template's index.php and overrides need updating
Extensions that only run on Joomla 6 with "Classes Aliases" onhigh: the compat plugin is off after the 7.0 update
Users from a Joomla 1.5/2.5 site who never logged in sincethose accounts will need a password reset

What to do now

  1. Turn on "Log Deprecated API" on a Joomla 6 staging copy of each site you maintain, click through, and keep administrator/logs/deprecated.php. It's a free, exact inventory of what will break.
  2. Try running with the compat plugin off. On Joomla 6 that's "Backward Compatibility 6" → Classes Aliases off. Whatever fails is your Joomla 7 list, today.
  3. Fix custom code by pattern, not by line: inject the database and user factory, move plugins to SubscriberInterface, get models from the MVC factory. How we do it.
  4. Ask your vendors. For every commercial extension: is there a Joomla 7 plan, and does the current version log deprecations on Joomla 6? A vendor whose current release is full of deprecated calls in late 2026 is a risk to plan around.
  5. Don't wait for Joomla 7 to leave Joomla 5. Joomla 5.4's security support ends in late 2027, around when Joomla 7 is expected. Sites that are cleanly on Joomla 6 by then have one step to take, not two.

Following the work

The 7.0-dev branch history and its pull requests are the primary source. Each removal comes with a PR that names the replacement, and the Joomla manual's migration pages follow. We recheck the branch regularly and update our breaking changes list when something moves from "marked" to "removed".