Most "Joomla 7 breaking changes" lists are guesses. This one is built from two sources you can check yourself. First, the Joomla 6.2 source: Joomla marks every API it plans to remove with a @deprecated … will be removed in 7.0 tag, and libraries/src alone contains about 375 of them. Second, the 7.0-dev branch on GitHub, compared file by file with 6.2 (October 2026, version string 7.0.0-alpha1-dev).
What the 7.0-dev branch has already changed
- The compatibility plugin is renamed and switched off. Backward Compatibility 6 is gone, and Backward Compatibility 7 (
plg_behaviour_compat7) replaces it. It still carries the ≈450J*aliases (JFactory,JText…), off by default, plus the moved Filesystem, Input, CLI, Crypt and Form classes. But the 7.0 update script installs it disabled. Code that only runs on Joomla 6 because the compat plugin is on will stop on Joomla 7 unless someone turns it back on. - PHPass passwords: the PHPass password handler is deleted (more below).
- Moved to the compat plugin:
Cryptand its ciphers, the old Mcrypt AES class, andRadiobasicFieldwith its layout. - PHP: the minimum is still 8.3 on the branch.
Most of the APIs below are still present in the branch at the time of writing: removal happens in steps, and some will move into the compat plugin instead of disappearing. Treat "marked for removal in 7.0" as "don't start a release cycle depending on it". There is no fixed release date. Joomla's two-year major cycle (4.0 in 2021, 5.0 in 2023, 6.0 in 2025) points to late 2027, when Joomla 5.4's security support also ends.
Find them in your own code first
Joomla can tell you exactly which of these your extension uses. On a Joomla 6 test site, turn on Log Deprecated API (Global Configuration → Logging), use every screen of your extension, and read the log:
# terminal – group the log by message, most frequent first
grep -v '^#' administrator/logs/deprecated.php | cut -f4- | sort | uniq -c | sort -rn | head -40
The log only sees code that runs. A grep catches the rest:
# terminal – from your extension's root
grep -rnE "Factory::(getUser|getDbo|getSession|getLanguage|getDocument|getConfig|getCache|getMailer|getDate)\(" --include=*.php .
grep -rnE "::getInstance\(|addIncludePath\(|addModelPath\(|getDbo\(\)|setDbo\(" --include=*.php .
grep -rnE "new CMSObject|extends CMSObject|->getProperties\(\)|->get\('(items|item|state|pagination|form)'" --include=*.php .
grep -rnE "triggerEvent\(|->addScript\(|->addStyleSheet\(|HTMLHelper::(stylesheet|script)\(|HTMLHelper::_\('(behavior|bootstrap\.framework|jquery|formbehavior|sortablelist)" --include=*.php .
grep -rnE "class Plg[A-Z]\w+ extends CMSPlugin|allowLegacyListeners" --include=*.php .
Marked for removal in 7.0 – high impact: found in most older extensions
Static Factory getters
| Removed in 7.0 | Use instead |
|---|---|
Factory::getUser() | $app->getIdentity(), or UserFactoryInterface for another user |
Factory::getDbo(), Factory::$database | DatabaseInterface from the container, or $this->getDatabase() in models and tables |
Factory::getSession(), getLanguage(), getDocument(), getConfig() | $app->getSession(), getLanguage(), getDocument(), getConfig() |
Factory::getCache() | CacheControllerFactoryInterface → createCacheController() |
Factory::getApplication() and Factory::getContainer() stay. They're the two entry points everything else goes through. The details and a migration walkthrough are in Factory getters after Joomla 6.
Legacy plugins
Since Joomla 5.4, CMSPlugin::registerListeners() and the whole mechanism that maps method names to events are deprecated, and $allowLegacyListeners goes with them. In Joomla 7 a plugin must implement SubscriberInterface and receive event objects. A plugin class like PlgContentExample with onContentPrepare($context, &$article, &$params, $page) stops being called. It doesn't throw, which makes it the quietest breaking change on this list. The pattern is in Joomla 6 plugin events explained.
Event classes change too: the positional "legacy arguments order" support is deprecated, and argument setters move from setFoo() to onSetFoo(). That matters if you wrote your own event classes.
MVC: the old way to get models, tables and controllers
| Removed in 7.0 | Use instead |
|---|---|
BaseDatabaseModel::getInstance(), BaseModel::addIncludePath(), LegacyModelLoaderTrait | $app->bootComponent('com_x')->getMVCFactory()->createModel('Items', 'Administrator') |
Table::getInstance(), Table::addIncludePath() | $mvcFactory->createTable(…) or new MyTable($db) |
BaseController::getInstance(), addModelPath() | the component's MVC factory |
$model->getDbo() / setDbo(), $table->getDbo(), $this->_db | getDatabase() / setDatabase() |
$view->get('Items') (deprecated in 5.3) | $this->getModel()->getItems() |
$view->document (public property) | $this->getDocument() |
Joomla\CMS\MVC\Model\State | Joomla\Registry\Registry |
$this->get('Items') in views deserves special mention. It's in nearly every component written since Joomla 1.5, including code generators' output, and it was deprecated only in 5.3:
// administrator/components/com_example/src/View/Items/HtmlView.php
public function display($tpl = null): void
{
$model = $this->getModel();
$this->items = $model->getItems(); // was: $this->get('Items')
$this->pagination = $model->getPagination(); // was: $this->get('Pagination')
$this->state = $model->getState(); // was: $this->get('State')
$this->filterForm = $model->getFilterForm(); // was: $this->get('FilterForm')
parent::display($tpl);
}
CMSObject
Joomla\CMS\Object\CMSObject, the base of countless helper and item classes since Joomla 1.5, is removed. Its get(), set(), getProperties() and setError() go with it. Joomla names the replacement: \stdClass for plain data, Registry for key/value data. Your own classes get typed properties and exceptions instead of setError().
Assets added the old way
| Removed in 7.0 | Use instead |
|---|---|
$doc->addScript(), $doc->_scripts, _styleSheets, _script, _style | Web Asset Manager: registerAndUseScript(), addInlineScript() |
HTMLHelper::stylesheet() (deprecated in 5.3) | $wa->registerAndUseStyle() |
HTMLHelper::_('behavior.core' / 'formvalidator' / 'keepalive' / 'multiselect' / 'combobox') | $wa->useScript('core' / 'form.validate' / 'keepalive' / 'multiselect' / 'awesomplete') |
HTMLHelper::_('jquery.framework'), 'bootstrap.framework' | $wa->useScript('jquery'); load Bootstrap components individually |
HTMLHelper::_('formbehavior.chosen'), 'sortablelist.sortable' | choices.js (fancy-select layout); draggablelist.draggable |
Templates and overrides are affected here as much as extensions. Many older templates call $doc->addScript() in index.php.
Marked for removal – medium impact: common in older components
- Application:
$app->getCfg()→$app->get().triggerEvent()→$app->getDispatcher()->dispatch(). StaticgetRouter()andgetInstance()→ the container.$app->input(magic property) →getInput(). - Toolbar:
Toolbar::getInstance()→ToolbarFactoryInterfaceor$this->getDocument()->getToolbar(). Custom buttons implementingfetchButton()→render().addButtonPath()→ namespaced buttons. - Forms and language:
Form::getInstance()→FormFactoryInterface.Language::getInstance()→LanguageFactoryInterface. - Routing:
Route::_()stops failing silently on router errors, and the old integer/-1 forms of the TLS argument go away. - Users:
User::getInstance()→UserFactoryInterface. - CLI:
Joomla\CMS\Input\Cliand the old CLI application → console commands.
Low impact, but check this one: old password hashes
UserHelper::HASH_MD5 and HASH_PHPASS are marked for removal, and the PHPass password handler is already deleted from the 7.0-dev branch. Joomla has re-hashed passwords on login for years, so active users are fine. But accounts migrated from Joomla 1.5/2.5 that haven't logged in since still carry the old hash, and on Joomla 7 they can't log in. They'll need a password reset. Check before the upgrade:
# terminal – accounts still on legacy hashes (bcrypt starts with $2y$, argon2 with $argon2)
mysql -e "SELECT COUNT(*) AS legacy, MAX(lastvisitDate) AS last_login
FROM jos_users
WHERE password NOT LIKE '\$2y\$%' AND password NOT LIKE '\$argon2%';" mydb
Also on the list, rarely used
Table\UcmandCoreContent::storeUcmBase(), part of the old UCM layer (5.4).HtmlDocument::countMenuChildren(): count the active menu item's children yourself.AdministratorApplication::purgeMessages(): use the Messages model.CMSApplication::isTwoFactorAuthenticationRequired(), a leftover of pre-4.2 2FA.Form\Field\RadiobasicField:RadioField(moved to the compat plugin in 7.0, removed in 8.0).Tag::ajaxfield()andBehavior::highlighter(), without replacement.
What doesn't change
If your code already uses namespaced classes, a service provider, the MVC factory, SubscriberInterface, the Web Asset Manager and getDatabase(), almost nothing on this list applies to you. Those patterns have been the recommended way since Joomla 4.0. Joomla 7 removes the bridges, not the road. Code that runs on Joomla 6 with the compat plugin's options switched off and an empty deprecated.php is very likely Joomla 7 ready today.
