How to Find a Joomla Extension Record in #__extensions
Understand what #__extensions contains
Joomla's extensions table stores records for installed extensions and related core extension entries. Joomla's programmer documentation also notes that an extension's manifest version is stored in the manifest_cache column of #__extensions. The #__ prefix is a placeholder; use the site's actual configured table prefix when querying the database directly.
Identify the extension before querying
Determine the extension type and element you are looking for. A component may have an element such as com_example; a plugin also has a folder or group; modules have their module element and client location. Using several identifying fields is safer than assuming a human-readable name is unique.
Use a read-only query first
In phpMyAdmin or another database client, select the Joomla database and run a SELECT rather than an UPDATE. A practical starting point is to inspect rows where element matches the extension's known element, then review extension_id, name, type, element, folder, client_id, enabled, manifest_cache, and other relevant fields.
Account for plugins and multiple clients
For plugins, the folder field helps distinguish groups such as system, content, or user. Site and Administrator modules can also require client context. If more than one row matches a broad search, do not pick an extension_id until the type, element, folder, and client information identify the intended extension.
Use extension_id when correlating Joomla records
The extension_id is Joomla's internal identifier for that installed extension record. Other Joomla data can refer to it, including the SQL schema tracking table for extensions that use Joomla's schema-update mechanism. Record the ID exactly rather than copying one from another site, because IDs are installation-specific.
Inspect manifest_cache without treating it as SQL schema state
The manifest_cache field can include metadata such as the extension version from its manifest. Joomla tracks the SQL schema version separately in #__schemas. Those two versions are distinct and should not be assumed to match merely because an update succeeded or failed.
Do not edit the row just to make an extension look installed
Changing #__extensions directly can create a misleading state without installing files, registering dependencies, running SQL migrations, or performing extension-specific installer logic. Use direct edits only as part of a documented recovery procedure with a current backup and a verified understanding of the affected records.
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.