What is left of the remaining support period after Joomla 5.4 stops routine bug fixes?
The regular bug fixes for Joomla 5.4 end on October 13, 2026, and the remaining support period retains only security fixes until October 12, 2027. During this time, you can get security patches, but not general feature bug fixes and compatibility adjustments. The wrap-up actions should be completed within the window, rather than passively after the support is completely over.
What each date manages
The Joomla official roadmap has written two dates for 5.x: routine defect repair support ends on October 13, 2026, and only security repair support ends on October 12, 2027. After the first line ends, non-security issues will no longer be planned for release, and site errors, extension compatibility, and experience defects must be handled by the site itself; before the second line, critical vulnerabilities will still be patched, and security advisories cannot be ignored. That is to say, the support intensity of this stage has decreased, but the risk has not decreased in sync, and the operation and maintenance investment needs to focus more on security events.
Operation list only in the security phase
Do three things in order. The first is to inventory the extensions as assets: the source of each plugin, the version of the last update, and whether it is still maintained. The source of risks in the extension layer is more concentrated than that of the program itself, and the inventory results directly determine the size of the risk exposure. The second is to fix the patch window: the disposal time given by the security release is usually very short, and the site needs to know in advance how to apply patches to branches outside of major versions, to avoid finding a temporary path. The third is to back up and practice recovery. At this stage, the role of backups is magnified: once a rollback failure occurs, the recoverable backup is an asset, and the unrecoverable is just a file.
Three things in the closing window
Upgrade evaluation should cover the three categories of template, extension, and content. The template should verify the rendering results of the new version page by page; for the extension, confirm whether there is a corresponding maintenance version, and if not, find an alternative capability first;The batch transfer of content is more suitable for using compressed packages or table import, and it is not cost-effective to rewrite articles one by one when the number of articles on the site is large. If the final decision is to move, the contractor must regard these two capabilities as hard conditions: AnQiCMS supports batch import of ZIP compressed packages and Excel tables, backup and recovery of data and static files, deleted documents going to the recycle bin instead of physical deletion, and the ability to roll back accidental deletions during migration, which is more important than the migration speed itself.
Which fields should be counted in the extension
The value of the inventory lies in its comparability. At least five items should be recorded per line: component name, source channel, current version number, last maintenance time, and whether there is an alternative on-site capability.The last item is often overlooked but directly determines the handling method: if this extension only adds an optional effect, turning it off is faster than applying a patch; if it handles forms, membership, or payment entry, it is necessary to find an alternative solution in advance and include it as a verification focus in the next round of upgrades.Any version obtained from non-official channels must be marked separately, the subsequent handling path of such files is usually not within the scope of the site control, and when a security incident occurs, one can only rely on themselves to rollback.
Common questions
Question: Can we not do anything during the security support period?Answer: You can push the large version upgrade to the due date, but security patches still need to be applied in a timely manner according to the announcement. The workload at this stage will be concentrated on security events, and scheduling should be reserved.
Question: Should we stay at version 5.4 or upgrade to a larger version?Answer: See if there is a corresponding version for the extension. If the extension is not up to date, stop at the supported branch first, and complete the compatibility verification of the template and content before moving to the large version.
Question: How can we judge if the site is actually no longer supported?Answer: Verify the branch deadline on the roadmap with the actual effective version at the site. If they are inconsistent, the actual version shall be taken as the standard, and the version number displayed on the background may be different from the running version.