Joomla has just shipped two simultaneous bugfix releases β version 6.0.1 and 5.4.1 β ironing out a range of issues reported since the major 6.0 launch. Here's everything you need to know about what changed, how to update, and whether you should migrate to Joomla 6 right now.
What Are Joomla 6.0.1 and 5.4.1?
Released on 25 November 2025, Joomla 6.0.1 and 5.4.1 are pure bugfix updates β no new features, no security advisories. Both releases target their respective active branches and address regressions and edge-case failures discovered by the community after 6.0.0 shipped.
| Release | Branch | Type | Support Until |
|---|---|---|---|
| Joomla 6.0.1 | 6.x | Bugfix | Active (next LTS) |
| Joomla 5.4.1 | 5.x | Bugfix | Bug patches until Oct 2026 Β· Security until Oct 2027 |
If you haven't moved to Joomla 6 yet, don't panic β the Joomla 5.4.x branch remains fully supported with bug patches until 13 October 2026 and with security patches until 12 October 2027.
Step 1 β Check for Automated Updates
If your site has the Joomla! Core Automated Updates feature turned on, there's a good chance the patch has already been applied while you were sleeping. Here's what to expect:
- Automated update enabled: The update from 5.4.0 β 5.4.1 or 6.0.0 β 6.0.1 runs automatically. All Super Users will receive an email confirming the result once complete.
- Automated update disabled: Head to System β Update β Joomla! in your administrator backend and trigger the update manually. The process typically takes under a minute on shared hosting.
- Verify the result: After updating, visit System β System Information and confirm the Joomla version shown matches 6.0.1 or 5.4.1 respectively.
Step 2 β What's Fixed in Joomla 6.0.1?
The 6.0.1 milestone closed 24 notable pull requests. Here are the most impactful fixes:
- Default menu submenu staying open on page load β a layout regression in the default frontend template that caused submenus to render expanded on first load.
- TinyMCE dark mode β the bundled WYSIWYG editor now respects admin dark mode preferences properly.
- Featured articles display when "All Categories" selected β category blog views were failing to display featured content under certain configurations.
- Article version history (frontend + PostgreSQL) β saving and displaying content history was broken for PostgreSQL users; the frontend version history panel also received fixes.
-
PHP 8.5 compatibility β two Composer packages (
joomla/testandjoomla/http) were updated to resolve deprecation warnings introduced in PHP 8.5 aroundReflectionProperty::setAccessible()andcurl_close(). - z-index fix for Choices.js dropdown β dropdown menus in admin forms were sometimes appearing behind modals.
- DELETE API endpoints returning wrong status β API calls to delete non-existent resources now correctly return HTTP 404 instead of a misleading success response.
- NPM security audit β resolved several security vulnerabilities in indirect development-only dependencies.
The complete changeset is available on GitHub: Joomla 6.0.1 milestone.
Template_extended creation date was incorrectly set to 2017 and has been corrected. If you're extending this template, re-check your child template metadata after updating.
What's Fixed in Joomla 5.4.1?
The 5.4.1 release is a separate set of backported fixes targeted specifically at the 5.x branch. While the full changelog differs from 6.0.1, it follows the same principle: stability and reliability improvements with no breaking changes.
Full list of changes: Joomla 5.4.1 milestone on GitHub.
Step 3 β Should You Upgrade from Joomla 5 to 6?
Good news: moving from Joomla 5.4.x to 6.x is classified as an upgrade, not a migration. You won't need to rebuild your site from scratch. Here's why:
- Clean extensions work out of the box: Any Joomla 5 extension that has already removed deprecated code and uses up-to-date Joomla APIs will run on Joomla 6 without modification.
- Behaviour 6 backward-compatibility plugin: For extensions that haven't fully modernized yet, enabling the Behaviour 6 β Backward Compatibility Plugin in the Plugin Manager gives them additional time to catch up while keeping your site functional.
- Check your extensions first: Filter the Joomla Extensions Directory by Joomla 6 to see which of your installed extensions already support J6, and which ones need the b/c plugin.
- Test on a staging copy first: The Joomla team strongly recommends running the upgrade on a copy of your live site before applying it to production.
Step-by-step migration guide: Joomla 5 to 6 planning & upgrade
Need premium templates and extensions ready for Joomla 6?
MonsterONE gives you unlimited access to thousands of Joomla templates, extensions, and web assets β all regularly updated for the latest Joomla releases. One subscription covers every project on your roster.
Browse Joomla 6 Templates βStep 4 β Download & Install
All official packages are hosted on the Joomla downloads portal. Here are the direct links:
| Version | Package type | Link |
|---|---|---|
| Joomla 6.0.1 | Full install (new sites) | Download ZIP |
| Joomla 6.0.1 | Update package (existing 6.0.0 sites) | Downloads page |
| Joomla 5.4.1 | Update package (existing 5.4.0 sites) | Downloads page |
Bonus Tip: Stay Ahead of PHP Compatibility
The 6.0.1 release included PHP 8.5 compatibility fixes, which is a signal worth acting on. PHP 8.5 is expected to become widely available on managed hosting in 2025β2026. Running an outdated PHP version is one of the most common causes of mysterious Joomla failures after a server-side upgrade.
; Check your current PHP version in Joomla
Administrator β System β System Information β PHP Version
; Recommended minimum for Joomla 6
PHP 8.2 or higher (8.3+ preferred)
If your host offers PHP version switching in cPanel or Plesk, test with PHP 8.3 on a staging environment before making the change on your live site.
Troubleshooting Common Update Issues
Most Joomla updates are uneventful, but here are solutions to the most frequent problems:
- Update says "No update available": Go to System β Update β Update Sites and click Rebuild to force Joomla to re-fetch the update manifest from the server.
-
White screen after update: This is almost always a PHP error. Enable error display temporarily in
configuration.phpby setting$error_reporting = '-1';and reload. Check the Joomla log files under /administrator/logs/. - Extension breaks after update: Disable the problem extension and enable the Behaviour 6 β Backward Compatibility plugin. Contact the extension developer for a J6-ready update.
- Database errors on PostgreSQL: Version history issues on PostgreSQL were specifically addressed in 6.0.1. If problems persist, run the Database Fix tool at System β Maintenance β Database.
For known issues specific to this release, check the official Version 6.0.1 FAQ.
Final Checklist Before & After Updating
- β Full site backup (files + database) completed
- β Staging environment tested first (recommended for Joomla 5 β 6 upgrades)
- β Extensions checked against Joomla 6 compatibility list
- β PHP version verified (8.2+ required, 8.3+ recommended)
- β Automated update emails reviewed or manual update triggered
- β Joomla version confirmed in System Information after update
- β Frontend and admin tested for layout regressions
- β Version history and content editing verified (key fix in 6.0.1)
- β TinyMCE editor tested in both light and dark admin mode
- β API integrations tested if using Joomla REST API (DELETE endpoints fix)
Conclusion
Joomla 6.0.1 and 5.4.1 are both recommended updates for all active Joomla sites. The fixes are targeted and well-tested β especially if you're running PostgreSQL, using the REST API, or managing rich content with version history enabled. The PHP 8.5 compatibility work is also a forward-looking improvement worth having in place before your host upgrades its PHP environment.
If you're still on Joomla 5.4.x and hesitant about moving to 6, that's a perfectly valid choice β you have until October 2026 for bugfix support and October 2027 for security coverage. When you are ready to move, the upgrade path is smoother than any previous major version transition in Joomla's history.