How to Find a Joomla Extension Record in #__extensions

Joomla's #__extensions table stores installed extension records. To find the correct row safely, translate Joomla's #__ placeholder to the site's actual table prefix, start with a read-only SELECT, and match technical fields such as type, element, plugin folder, and client instead of relying only on a display name.

Identify the extension before querying

Record the extension's technical identity in Joomla Administrator: its type, element, and—where relevant—plugin folder/group or site/administrator client. A component might use com_example; a plugin additionally needs its group to distinguish it from plugins with similar names.

Do not copy an extension_id from another Joomla site. IDs are installation-specific.

Use the real table prefix

#__extensions is Joomla notation, not normally the literal table name in phpMyAdmin. Read $dbprefix from configuration.php. If the prefix is abcd_, query abcd_extensions.

Confirm you are connected to the database named by Joomla before running any query.

Start with a read-only SELECT

For a component whose element is known, a diagnostic query can start like this:

SELECT extension_id, name, type, element, folder,
       client_id, enabled, manifest_cache
FROM `yourprefix_extensions`
WHERE element = 'com_example';

Replace the example prefix and element. For a plugin, include the expected folder; for modules or other extension types, also verify type and client context. If several rows match, do not choose one until those fields identify the intended extension.

Understand extension_id and manifest_cache

extension_id is Joomla's internal identifier for that installed extension record and can be used to correlate other Joomla records. The manifest_cache field contains manifest-derived metadata, including the extension version.

That manifest version is not the same as the SQL schema version. Joomla tracks an extension's processed SQL schema version separately in #__schemas, so do not assume the two values match or serve the same purpose.

Correlate the extension with its SQL schema record when needed

  1. Find and record the correct extension_id.
  2. Query the site's prefixed schemas table for that extension ID.
  3. Compare the stored version_id with the versioned SQL update files shipped by the extension.
  4. If the schema record is missing or behind, investigate the extension's supported update/repair path before editing either table.

Joomla processes versioned extension SQL updates based on the schema version it has recorded, independently of the manifest version.

Do not manufacture an installed state by editing the row

Adding or changing a row in #__extensions does not install files, run installer scripts, execute SQL migrations, register dependencies, or perform extension-specific setup. Direct edits can leave Joomla reporting an extension as installed when the rest of the installation is incomplete.

Use direct database changes only as part of a documented recovery procedure with a current backup and an exact understanding of the related records. For ordinary repair, use Joomla's installer/update process or the extension developer's supported procedure.


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