Am 14.07.2011 13:19, schrieb Holger Kohnen: > many modules require admin changes, so one overloading mechanism will > not solve the > admin-template-update-problem(atup). My simple approach would solve this by at least beeing able to put the module-modifications all together into the "theme-directory", instead of having to write them to the default template-files. The main-problem I have, is to be able to update the whole shop including admin-changes without running into trouble because of some small lost tpl-changes.
I know that lots of Shop maintainers do not at least use the theming / CustomTpl for changing the frontend. I'm not sure if they do not use it because of not knowing about it, or because of the very little additional work while creating a new design. So the hook is even more complicated to understand and maybe keeps "lazy" ones or beginners away from using it. Simple CustomTheme for Admin is at least easy to handle and understand. I see the advantages of the hook- / XML-sollution, but I am not sure if it is not easyer to implement the simple solution in near future (maybe in 4.5.1) and add the powerfull hook-thing when there is time and at least 4.5 is "stable" - if you understand what i mean. This would finaly result in two options to resolve the task of extending the backend. Simple: overload-folder, powerful: hook / XML Regards, Kai
_______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
