Applies to Joomla 7.0-dev (alpha) · PHP 8.3+ · Node 20+ · extension and template developers Updated 16 Oct 2026

The cheapest moment to find out what Joomla 7 breaks in your extension is now, while the changes are still small and land one pull request at a time. This is the setup we use to test extensions against the next major version: a local Joomla built from the 7.0-dev branch, installed from the command line, with the settings that make deprecated code impossible to miss.

Every command below was checked against the branch in October 2026, when it reported version 7.0.0-alpha1-dev.

What you need

ToolVersion on 7.0-devWhere it's defined
PHP8.3 or newer (test on 8.4 and 8.5 too)composer.json → "php": "^8.3.0"
Composer2.x
Node.js / npmNode 20+, npm 10.1+package.json → engines
DatabaseMySQL 8 or MariaDB 10.4+ (or PostgreSQL)
Gitany

PHP extensions: the usual Joomla set (gd, intl, mbstring, mysqli or pdo_mysql, zip, xml, sodium), and xdebug if you step through code.

1. Get the branch and build it

# terminal
git ls-remote --heads https://github.com/joomla/joomla-cms.git | grep -E 'refs/heads/[0-9]'   # see which -dev branches exist
git clone --branch 7.0-dev --single-branch https://github.com/joomla/joomla-cms.git joomla7-dev
cd joomla7-dev
composer install
npm ci

npm ci takes a few minutes. The repository's install script runs the full asset build (build/build.mjs build) right after the packages are installed, compiling the SCSS and JavaScript into media/. If the admin looks unstyled after installation, this step didn't finish. Run it again and read the error.

To update later, pull, then repeat both installs. The lock files change often on a dev branch:

# terminal
git pull && composer install && npm ci

2. Install Joomla from the command line

The installer has a CLI (installation/joomla.php). Its options are generated from the installation form, so they match the fields of the web installer:

# terminal – inside joomla7-dev, with an empty database "j7dev"
php installation/joomla.php install \
    --site-name="Joomla 7 dev" \
    --admin-user="Dev Admin" --admin-username=admin --admin-password='a-long-local-password' \
    --admin-email=This email address is being protected from spambots. You need JavaScript enabled to view it. \
    --db-type=mysqli --db-host=127.0.0.1 --db-user=root --db-pass=root \
    --db-name=j7dev --db-prefix=j7_ --db-encryption=0

Run php installation/joomla.php install --help to see every option on your checkout. The CLI install also makes resetting fast. Drop the database, delete configuration.php, run the same command, and you have a clean site in seconds. That's what you want before each test round.

Serve it with whatever you use locally (MAMP, Herd, DDEV, nginx). For a quick look, PHP's built-in server works for the front end and back end:

# terminal
php -S 127.0.0.1:8070 -t .

3. Settings that make problems visible

# terminal – the Joomla CLI can set configuration values directly
php cli/joomla.php config:set error_reporting=maximum
php cli/joomla.php config:set debug=true
php cli/joomla.php config:set log_deprecated=true
  • Error reporting "maximum" shows notices and deprecations from PHP itself, not only from Joomla.
  • Debug System adds the debug console with queries, timing and the language strings that are missing.
  • Log Deprecated API writes every call to a deprecated Joomla API to administrator/logs/deprecated.php, with file and line. This is the most useful file in the whole exercise.

Then check System → Plugins → "Behaviour – Backward Compatibility 7". On the dev branch it is installed but disabled, and that's how you want to test first. Your extension should run with it off. If it only runs with it on, you know exactly what to fix: J* class names or the moved Filesystem/Input/CLI classes.

4. Install your extension

# terminal – from a built package
php cli/joomla.php extension:install --path=/path/to/pkg_example.zip

# or from a folder (unpacked package)
php cli/joomla.php extension:install --path=/path/to/build/pkg_example

For day-to-day work, symlink your source folders into the dev site after the first install, so edits show up without reinstalling. Joomla follows the symlinks:

# terminal – a module and its language files
ln -sfn ~/code/mod_example/src            modules/mod_example/src
ln -sfn ~/code/mod_example/tmpl           modules/mod_example/tmpl
ln -sfn ~/code/mod_example/language/en-GB/mod_example.ini language/en-GB/mod_example.ini

5. Test, then read the logs

  1. Use every view and every task of the extension, front end and back end, as a guest, as a registered user and as an admin.
  2. Read the logs:
# terminal
grep -v '^#' administrator/logs/deprecated.php | cut -f4- | sort | uniq -c | sort -rn | head -30
tail -n 50 administrator/logs/everything.php 2>/dev/null
tail -n 50 /path/to/php-error.log

Errors you'll typically see on 7.0-dev with older code:

  • Class "JFactory" not found, or any J* class: the compat plugin is off, as it is by default. Use the namespaced class.
  • Class "Joomla\CMS\Filesystem\File" not found: use Joomla\Filesystem\File, which throws exceptions instead of returning false.
  • A plugin that simply doesn't react: a legacy plugin whose method-name listeners aren't registered. Move it to SubscriberInterface.
  • TypeError on Joomla\CMS\Input\Input type hints: hint Joomla\Input\Input.

The full list of what's marked for removal, with replacements, is in Joomla 7 breaking changes.

6. Static analysis against the dev branch

Clicking through finds what runs. PHPStan finds the rest, including code paths you never trigger by hand. Point it at your extension and let it read the Joomla 7 checkout for class definitions:

# ~/code/mod_example/phpstan.neon
parameters:
    level: 3
    paths:
        - src
        - tmpl
    scanDirectories:
        - ../joomla7-dev/libraries
        - ../joomla7-dev/administrator/components
        - ../joomla7-dev/components
        - ../joomla7-dev/plugins
    bootstrapFiles:
        - ../joomla7-dev/includes/defines.php
# terminal
composer require --dev phpstan/phpstan
vendor/bin/phpstan analyse

"Call to an undefined method" and "class not found" here are exactly the Joomla 7 breakages. Running the same config against a Joomla 6 checkout shows which of them are new in 7.

Keep it running

The branch changes weekly. Once a month we pull, rebuild, reinstall from scratch and repeat steps 4–6 for each extension we maintain. It takes an hour, and it means that on release day, "Joomla 7 compatible" is a version bump, not a project.