westkoast Posted February 17, 2003 Share Posted February 17, 2003 I've started to notice that same contributions make changes to the same files, so when they just say "replace with this file" in the installation guide...you may be overwriting changes that another contrib. has allready made. Any suggestions on how to keep track of what chanages have been made to files, etc. I'm running into this problem now because I want to "uninstall" a "product stock" contribution that I've been using (it has some very negative effects on the system), but I'm not sure if I've made any other changes to those files.... I need to read the rules more often... Link to comment Share on other sites More sharing options...
mugitty Posted February 17, 2003 Share Posted February 17, 2003 Unless you save a copy of every file and identify it so that you know where you were immediately before any change, I would think that you need to look at the original file from the osC snap that you're using and see if you can pick it out that way using a file compare utility. ... if you want to REALLY see something that doesn't set up right out of the box without some tweaking, try being a Foster Parent! Link to comment Share on other sites More sharing options...
hobbzilla Posted February 18, 2003 Share Posted February 18, 2003 Do a search on google and read up a little bit on 'CVS', 'beyond compare', 'examdiff', 'winmerge' Link to comment Share on other sites More sharing options...
Ajeh Posted February 18, 2003 Share Posted February 18, 2003 I leave my .bak files on my computer. This tells me if I have touched a file or I can reference the version number in a file. Then using Beyond Compare, I can check the files to make sure I don't make a mess of things. :D Link to comment Share on other sites More sharing options...
Farrukh Posted February 18, 2003 Share Posted February 18, 2003 The best way is to learn CVS and keep track of the changes made. And to use a File Comparison software such as Beyond Compare. ExamDiff etc. Link to comment Share on other sites More sharing options...
zzfritz Posted February 18, 2003 Share Posted February 18, 2003 Here is how I have maintained a modicum of sanity in the face of constant change and overlapping contributions: Keep a detailed log of every update and modification I make to the code in my live shop, being careful to identify the fully qualified file names so it can be searched easily. Whenever I modify a script, I put a note to that effect in the comment section immediately below the $Id: line. Download a complete backup to a CD at least once a week, and before making any significant modifications such as uploading contributed code for testing. Only a couple times have I had to backtrack. Maintain a completely separate copy of the undisturbed cvs, for reference, using TortoiseCVS to keep it current and ExamDiff to compare files. Also keep an undistured copy of all contributions as originally downloaded. Link to comment Share on other sites More sharing options...
Harald Ponce de Leon Posted February 18, 2003 Share Posted February 18, 2003 The $Id values are also useful to see how many changes have occured since that version of the file. The complete history of changes of every file in CVS can be seen here: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/tep Not only can you see how many changes have occured, but you can also see the differences between them. (the links show only x -> x-1 differences, however the Id values in the url can be changed to show the differences between x and x-20) , osCommerce Link to comment Share on other sites More sharing options...
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.