How to Fix an Extension Whose Files Updated but Database Did Not
When an extension's new files are present but its database migration did not complete, the extension can be internally inconsistent: PHP code expects tables, columns, or data that the older schema does not provide. Preserve the failed state, confirm the exact old and target versions, and use the extension developer's supported repair or reinstall path before considering manual schema changes.
Confirm this is really a files-ahead-of-database failure
- Record the extension name, previous version, target version, and update timestamp.
- Capture the exact SQL/PHP error and relevant Joomla, PHP, and database logs.
- Confirm the extension files or manifest report the newer package version.
- Identify symptoms such as missing-table, missing-column, or migration errors.
- Create a current backup of both files and database before attempting repair.
Do not change a schema-version row merely because it appears older. First establish which migrations actually ran.
Understand Joomla's extension SQL update mechanism
An extension manifest can declare an update schema path containing numbered SQL files. Joomla tracks two independent values: the extension manifest version in jossa_extensions.manifest_cache and the last processed SQL update filename in jossa_schemas.version_id.
During an extension update, Joomla reads the stored schema version, sorts the SQL update filenames numerically, executes files after the stored value, and records the last successfully processed update filename. Skipping extension releases is therefore supported when the package includes the required intermediate SQL files.
Check the complete vendor package and upgrade requirements
Verify that the package belongs to the exact extension and Joomla/PHP environment and that it contains the expected manifest and SQL update directory. Read the vendor's release notes for required intermediate versions, migration commands, dependency versions, or post-update actions.
Do not copy a column definition or SQL file from another extension release just because its name resembles the missing object. Extension developers can transform data as well as structure, and running only one guessed statement can bypass required migrations.
Prefer a supported rerun or repair procedure
If the developer explicitly supports installing the same current package over the existing extension, use that method on staging first. Joomla's installer can then process the manifest and extension update logic from the stored schema state. Some extensions instead provide their own repair/migration command; follow the vendor's procedure when one exists.
If the extension update failed because of database privileges, storage, timeout, or a specific SQL error, correct that root cause before rerunning. Repeating the same installer against the same failure condition will not repair the schema.
Inspect and verify schema state after repair
For advanced diagnosis, identify the extension's extension_id, read its manifest version and jossa_schemas.version_id, and compare the schema marker with the SQL update files actually shipped by that package. Do not advance version_id manually unless the vendor's documented recovery specifically requires it and you have verified the corresponding SQL changes already exist.
After the supported repair, confirm the expected database objects exist, the extension loads in Administrator and frontend, and its real workflows succeed. Review the logs and keep the backup until the repaired extension is stable. Joomla's core System → Maintenance → Database repair is for Joomla core schema; it is not a universal migration runner for arbitrary third-party extensions.
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.