How to Compare Joomla Files After a Failed Update
File comparison after a failed Joomla update can show whether core extraction stopped early, files were locally modified, or unexpected files are present. The comparison is diagnostic: preserve the failed state first, compare it with the exact official target release, and interpret differences before overwriting anything. A file match alone also cannot prove the database update completed.
Preserve evidence and identify both Joomla versions
- Record the Joomla version that was installed before the update and the target version.
- Save the exact updater error, timestamp, and relevant Joomla/PHP/web-server logs.
- Take a filesystem/database snapshot of the failed state when practical.
- Do not run another update or bulk-copy files until the comparison is captured.
Obtain the official Joomla package for the exact target release from Joomla's official distribution channel. Verify its published checksum when available before treating it as your reference set.
Build a clean comparison tree without mixing in site data
Extract the official target package into a separate directory, never over the failed site. Compare Joomla-owned core paths while deliberately accounting for files that are expected to be site-specific.
configuration.phpis site configuration and is not a clean-package equality target.- Uploaded media, logs, caches, backups, and other runtime data will legitimately differ.
- Third-party extensions and templates are not validated merely by comparing them with Joomla core.
- Custom template overrides can be legitimate even when their corresponding core layout changed.
Do not delete an unexpected file simply because it is absent from the core archive. Identify what installed or created it first.
Compare paths and cryptographic hashes
For a large installation, a recursive hash inventory is more reliable than opening files visually. Generate a list of relative path plus a modern cryptographic hash such as SHA-256 for the clean target and for the comparable Joomla core paths on the failed site.
Classify the report into expected core files that are missing, expected core files whose hashes differ, and additional files. A missing target file is strong evidence that extraction/replacement did not finish. A changed core file can be a partial update, an intentional local edit, or a compromise; the hash report tells you where to investigate, not why the difference exists.
Check database completion separately
A failed update can leave the filesystem at one stage and the database at another. If Administrator remains usable, go to System → Maintenance → Database. Joomla documents that normal updates apply schema changes automatically and that this screen detects structural mismatches when an update did not complete.
If core schema problems are reported and the Joomla files are known to be the intended target version, Update Structure can run outstanding Joomla core schema scripts. If file consistency is still uncertain, do not use database repair as a substitute for establishing the filesystem state first.
Recover to a consistent state and verify it
If the comparison proves a partial core update, prefer Joomla's documented recovery path or restore the complete known-good pre-update files-and-database backup and retry after correcting the original failure. Hand-selecting files from multiple Joomla releases can produce a site that loads while remaining internally inconsistent.
After recovery, confirm the Joomla version and database structure, rerun the core-file comparison if needed, and test Administrator, frontend, extensions, template overrides, scheduled tasks, and logs. Keep the difference report with the incident record so you can explain exactly what changed.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.