How to Fix a Joomla Database Schema Update That Did Not Run

When Joomla or an extension updates its files but a required database migration does not run, code and database can end up at different versions. The safe repair is to preserve the current state, identify exactly which migration failed, and rerun the supported update path rather than forcing the schema tracker forward.

Recognize and document the failed migration

Common symptoms include unknown-column errors, missing-table errors, Administrator failures, or an extension expecting a database field that does not exist. Record the complete error, affected extension, old and new versions, and the update action that preceded the failure.

Create a complete recovery point

  1. Back up the database.
  2. Back up the Joomla files from the same current state.
  3. Verify both backups are usable before making repairs.
  4. Use a staging copy first when the site or extension is important.

Both halves matter because a failed update may leave PHP files and database schema at different release levels.

Determine which SQL updates should have run

  1. Find the extension's extension_id in jossa_extensions.
  2. Read its current version_id from jossa_schemas.
  3. Inspect the exact package manifest and its declared schema/update directory.
  4. List the numbered SQL update files later than the recorded schema version.
  5. Compare those migrations with the actual database structure and the installer error.

This establishes where processing appears to have stopped without altering anything.

Rerun the supported installer or repair path

If the extension developer supports reinstalling the same package, use Joomla's installer or the vendor's repair procedure. For Joomla core, use the database/update structure repair provided for the installed release when applicable. A supported installer path can execute both SQL and PHP migration logic that a manually copied SQL statement would miss.

Do not advance jossa_schemas to hide the failure

Changing version_id to a later value without applying the underlying migration can make Joomla believe the database is current. Later updates may then skip required table, column, index, or data changes. Change schema tracking manually only as part of a documented recovery where the database state has been independently proven.

Verify the database and application together

  1. Confirm the expected database objects now exist.
  2. Recheck jossa_schemas and ensure it represents migrations actually completed.
  3. Test the affected Administrator and frontend workflows.
  4. Review Joomla, PHP, and database logs for residual SQL errors.
  5. Keep the recovery backup until normal operation is confirmed.

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.

Open a Support Ticket