How to Find Existing Joomla Template Overrides
Open the template customization screen
In Joomla Administrator, go to System → Templates → Site Templates and select the template you want to inspect. Joomla's Templates: Customise screen provides the file tree, override creation tools, and override-related status for that template. Administrator templates are separate, so make sure you inspect the correct client.
Look inside the template html folder
Template overrides are normally stored under the template's html directory. Expand that folder in the Editor view. Component overrides appear beneath component names such as com_content, module overrides beneath module names such as mod_menu, and Joomla layout overrides can appear under layouts paths.
Use the filesystem when you need a complete inventory
You can also inspect /templates/[template]/html/ with a hosting file manager, SFTP, or shell. For Administrator overrides, inspect the corresponding Administrator template path. Record the files before editing them so you have a clear baseline of what custom output the site already depends on.
Check the Updated Files information
Templates: Customise includes override-management information for files whose upstream source changed during a Joomla or extension update. An entry here means an existing override deserves review; it does not automatically mean the override is broken or unsafe.
Distinguish overrides from alternative layouts
Not every PHP layout under a template's html tree behaves identically. A file using the same layout name as the upstream output can automatically override that output, while appropriately named alternative layouts may be selectable through menu, module, or component options. Identify how each file is invoked before changing it.
Trace an override back to its source
Compare the override with the current source layout from the Joomla component, module, plugin, or shared layouts directory. Joomla's override tools can create supported overrides by copying source output into the proper template structure. Knowing the source file makes later update review much safer.
Document the overrides you intend to keep
Create a small inventory of override path, source extension, purpose, date reviewed, and any related template style or menu dependency. Existing overrides can survive unnoticed for years, so documentation helps distinguish intentional customization from obsolete code when Joomla or an extension is upgraded.
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.