How to Find Joomla Schema Versions in #__schemas
Know what Joomla stores in #__schemas
Joomla uses #__schemas to track the last SQL schema update version processed for extensions that participate in its schema-update mechanism. The table uses an extension ID together with a version_id. The #__ prefix represents the site's actual Joomla table prefix.
Find the extension ID first
Locate the target extension in #__extensions and record its extension_id. Do not assume an ID from documentation, another website, or another backup will match this installation. Extension IDs are database-specific and can differ between sites.
Query the schema record read-only
After selecting the correct Joomla database, run a SELECT against the real prefixed schemas table for that extension_id. Review extension_id and version_id. If there is no row, record that fact rather than immediately inserting one; absence can have different meanings depending on how the extension packages and tracks SQL updates.
Understand what version_id means
For extension SQL updates, Joomla reads numbered SQL files from the schemas path defined in the extension manifest. The version_id in #__schemas records the last update-file version Joomla processed. On an update, Joomla processes SQL files numerically later than the stored schema version and then records the last processed version.
Do not confuse schema version with manifest version
The version shown for an extension in Joomla comes from its manifest metadata and is stored in manifest_cache in #__extensions. Joomla's programmer documentation explicitly treats that version and the SQL version in #__schemas as separate values. They are often kept aligned by developers, but Joomla does not infer one from the other.
Compare the record with the actual package
If you are diagnosing an update problem, inspect the installed extension's manifest and the SQL update filenames shipped with the exact package. A schema record that is lower than available update files can indicate pending or failed database work, but the package and installer history are needed before deciding what should run.
Keep diagnosis read-only until the mismatch is proven
Do not raise version_id merely to suppress an error. Setting it too high can cause Joomla to skip SQL migrations that the database still needs. Back up first and use the extension developer's supported repair or reinstall process whenever possible.
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.