-
I was playing with the admin template and I noticed a very weird thing. Could somebody look at it and confirm it? I know that cache needs to be cleared after any change in code. I did it. Admin template header is used this way:
1Q. help to getCoreTemplate() is outdated? this line: e107_themes/templates/user_template.php (if override not found or $override is false)
2Q $override parameter for all keys has to be the same? I tried to change this parameter for the "header" key:
no change, $reg_path is still core/e107/templates/admin and $override is still false inside e107::getCoreTemplate() method I found that the first calling is with key "nav" in admin_shortcodes, after changing $override there, it was changed for the header too. $reg_path is correct then: core/e107/templates/admin/ext Maybe this is clearer: Combination:
all $overrides inside getCoreTemplate() ale false, path is core/e107/templates/admin for header too Combination:
correct, core/e107/templates/admin/ext + core/e107/templates/admin/ for header Combination:
correct, core/e107/templates/admin/ext for both keys So should it work this way? Or this is just a way how to forbid overriding core templates? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Core templates should work this way, however there is currently no support for customizing the Admin Area. So there is hardcoded values used to prevent customization. |
Beta Was this translation helpful? Give feedback.
Core templates should work this way, however there is currently no support for customizing the Admin Area. So there is hardcoded values used to prevent customization.