For people who use Joomla, Joomla 7 will look a lot like Joomla 6. For the code behind a site, it's the version that stops accepting Joomla 3-era shortcuts. This post separates the two, so you can tell whether Joomla 7 is a routine update for your site or a project.
It's based on the Joomla 6.2 source and the 7.0-dev branch as of October 2026 (alpha). Details can still change, but the direction is set.
What stays the same
- Articles, categories, menus, modules, custom fields, tags, workflows, Smart Search, multilingual associations.
- The database: no structural change so far beyond the plugin swap below. Content and users come across as in any update.
- PHP 8.3 as the minimum. If your host runs Joomla 6, it runs Joomla 7.
- The admin (Atum) and Cassiopeia, which keep evolving in minor releases rather than being redesigned.
- Extensions built on Joomla 4+ patterns: namespaced classes, service providers, event subscribers, the Web Asset Manager.
What changes
| Area | Joomla 6 | Joomla 7 |
|---|---|---|
| Compatibility plugin | "Backward Compatibility 6", enabled | "Backward Compatibility 7", installed disabled |
Old J* class names | available if Classes Aliases is on | only if someone enables the compat plugin and its aliases |
Factory::getUser(), getDbo() … | work, deprecated | marked for removal |
| Legacy plugins (method-name events) | work, deprecated | marked for removal: such a plugin stops reacting |
$doc->addScript(), HTMLHelper::stylesheet() | work, deprecated | marked for removal |
| MD5 / PHPass password hashes | accepted, re-hashed on login | PHPass handler removed: those accounts need a reset |
The pattern: Joomla 6 kept old code running and logged it. Joomla 7 stops running it. A site that shows no deprecation warnings on Joomla 6 is in good shape. A site that only works because the compatibility plugin is on will break, quietly in the case of plugins, loudly in the case of missing classes.
Check your own site in 15 minutes
These checks need shell or file access to a copy of the site, not the live one.
1. Is the site leaning on the compat plugin?
System → Plugins → search "compatibility". If Backward Compatibility 6 has "Classes Aliases" switched on, find out which extension needed it: switch it off on the copy and click through the site. Whatever breaks will break on Joomla 7.
2. Does the template use old APIs?
# terminal – in the site root of the copy
grep -rnE "addScript\(|addStyleSheet\(|HTMLHelper::(stylesheet|script)\(|JFactory|JHtml|JText|Factory::get(User|Document|Language|Dbo)\(" \
templates/*/index.php templates/*/html templates/*/*.php
Each hit is a small fix in the template or an override. Templates from vendors that still release updates usually get fixed for you. Templates nobody maintains need a developer.
3. What does Joomla itself report?
Turn on Log Deprecated API (Global Configuration → Logging) on the copy, use the site's main pages and forms, then look at administrator/logs/deprecated.php. Every line names the file responsible, so you can see at a glance whether it's the template, a third-party extension or your own code.
4. Old password hashes?
# terminal – accounts that never logged in since their hash became outdated
mysql -e "SELECT COUNT(*) FROM jos_users WHERE password NOT LIKE '\$2y\$%' AND password NOT LIKE '\$argon2%';" mydb
A handful of old accounts is normal on long-running sites. Decide whether to delete them or to warn them before the upgrade.
What it means by type of site
- Brochure site on core + a maintained template: expect a normal major update, like 5 → 6. Test on staging, update, done.
- Site with a shop, forum, membership or CRM extension: the extension's Joomla 7 release decides your timing. Ask the vendor now. See how this played out for VirtueMart and CiviCRM on Joomla 6.
- Site with custom extensions: budget for code work, and start before Joomla 7 is released. The fixes run on Joomla 6 too, so there's no reason to wait. The developer's side is in Joomla 7 breaking changes.
Timing
There's no release date. Joomla's two-year major cycle points to late 2027, which is also when Joomla 5.4's security support ends. Joomla 6 will keep getting security fixes well after 7.0 is out, as 5.4 does now. So there's no rush to be first on Joomla 7. There is good reason to be ready for it, because being ready is mostly fixing what Joomla 6 already logs.