Group: Member Post Group: Working Member
Posts: 160
Status:  |
Quote From : mylogon December 4, 2009, 7:42 am The files are part of the original install, and were modified. The way Fantasticao manages this is that it creates a diff file before it updates, and then make the user responsible for reintegrating the changes if they annot do so automatically, i.e., there are errors doing a patch.
I think you most definitely need this feature. Without it, a huge problems can occur in updating customized files, one that the end user would not even be aware of, until things just "do not work" - the call we all hate to get.
Example file for Coppermine:
/home/domain.com/www/gallery/lang/english.php
This is part of the default install, and is, and quite often, must be modified. Many scripts have similar files and problems. A diff file is a necessity, IMHO, and patching should be attempted, and if failed, then the roll back. If fine, then proceeds.
Alon you can PM me, and we can go into private chat, if you are not clear on what I am saying.
I beg to disagree. I am not comfortable to leave to the hands of the owners/admin the "integration" part.
What I will suggest will be to provide a way for users to modify themes or to customize. No one should be changing the core/original file. I don't believe that core files should be changed. It would be a better idea if Softaculous can find a way to provide customizations for the users without modifying the core/original file.
For example in Wordpress, if you change the original file, it will really get overwritten when you do upgrade, and that's how it should be. But they offer customization using folder "wp-content" and the user is free to customize it. Everything in the wp-content folder is not overwritten during the upgrade. I believe that is the correct way to handle customizations and upgrades.
Edited by gieathome : December 4, 2009, 1:51 pm |
Powered By AEF 1.0.8 © 2007-2008 Electron Inc.
