Admin theme is not taken into consideration in icms_view_Tpl constructor

[fiammybe]

When your admin theme is different from your frontend theme, the icms_view_Tpl class will always take the value in $icmsConfig['theme_set'] to identify where to look for eventual theme overrides (check out line 70, where the compile_id is constructed.
This could be the reason why the template overrides in a admin theme don't seem to work.
I think this information cannot be determined by the icms_view_Tpl class on its own, it needs input from the calling class.

[fiammybe]

this does work when you define a template in a template set, instead of adding a template file to a theme. @skenow this boils down again to the discussion what the difference is between template sets and themes...

[skenow]

Functionally, the results could be part of either the theme or the templates. What I understand templates and template sets do is they enable an admin to add a module without having to edit the theme to provide layouts for its pages and blocks.

From what we see, adding the possibility of a separate admin theme wasn't fully complete when it comes to the functionality we have on the user side for overrides.

Just thinking through this, wherever the icms_view_Tpl class is instantiated, the _compile_id would have to be set based on being in the admin area or not. For example, in function icms_cp_header(), try adding a line after

$icmsAdminTpl = new icms_view_Tpl();

to change the compile_id

$icmsAdminTpl->_compile_id = $icmsConfig['template_set'] . '-' . $icmsConfig['theme_admin_set'];