How to Disable a Broken Joomla Extension Directly in the Database
Use database editing only for recovery
Direct database editing bypasses Joomla's normal management workflow. Back up first; use Joomla management when Administrator is usable.
Identify the exact record
SELECT from #__extensions and match type, element, and for plugins folder. Current manifest documentation ties extension identity to these records.
Know the safe scope
A direct enabled change is most useful for a confirmed broken plugin. Do not assume every component, package, library, module instance, or template can be safely disabled by one flag.
Make the smallest change
For a confirmed plugin set only enabled=0, using all identifying conditions and verifying exactly one affected row.
Test the original failure
Reload the failing request and use the resulting evidence. Do not disable unrelated extensions indiscriminately.
Do not delete the row
Joomla install/uninstall can handle files, database changes, scripts, and other state; deleting a registration row is not an uninstall.
Repair normally afterward
Once Administrator works, use normal Joomla extension management and the vendor's supported repair/update procedure.
Verify and retain the backup
Test the affected feature, frontend, Administrator, and logs before considering recovery complete.
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.