toup Posted November 3, 2014 Share Posted November 3, 2014 Hello there, I just realized that when a module can be updated (thru prestashop addons), the "configure" link is not accessible. I'm curious as of why it is the case. In many cases, and specially during developpement cycles, you want to control inbound new code in your project. I know modules are thoroughtly tested but it disturbs me that I have to update a module before to change a setting in it, i'd like to be able to configure the outdated version of my module without updating it, and to have the freedom to review new version changes of the module and decide wether or not my prestashop installation is in shape for getting that upgrade. This shouldn't be an issue in production shops (were all codes/templates overrides are done "right"), but in shops still in developpement, custom code and tweaks in templates/module/core might get overwritten by updating code, and some custom features relying on old code might break on update too. This shouldn't be a risk i'm taking when I just want to tweak a setting somewhere. Am I just working the wrong way or does it disturb anyone else ? Link to comment Share on other sites More sharing options...
Recommended Posts