Description:
Standard Joomla template overrides created under the active site template do not affect J2Commerce product list output when a J2Commerce subtemplate plugin such as is selected.app_uikit
The component provides template and layout override structures, suggesting that files can be overridden from the Joomla site template. In practice, the active subtemplate plugin intercepts J2Commerce rendering events and loads files from its own and directories.tmpllayouts
As a result, changes made in the expected Joomla override locations are ignored.
The only reliable solution was to clone the plugin, create a separate subtemplate plugin and modify the files inside that plugin.app_uikitapp_template
Expected result:
Overrides placed in the active Joomla template should take precedence over files provided by a J2Commerce subtemplate plugin, or the documentation and interface should clearly explain that plugin-based subtemplates bypass standard component overrides.
Actual result:
The plugin-generated output takes precedence, and ordinary Joomla template overrides have no visible effect.
This makes maintaining a custom storefront difficult because:
- core or plugin files should not be edited directly;
- standard Joomla overrides appear to be supported but are ignored;
- creating a complete duplicate subtemplate plugin becomes necessary;
- fixes must be duplicated for initial rendering and AJAX rendering events.
Please clarify the intended override hierarchy and provide a supported override path for plugin-based subtemplates such as .app_uikit
