[garysmith]

When v3.1 comes out I want to move both my sites over to it. I have quite a few mods...as most of us do using 68. I have a few questions as we move closer to the next version of this really great software.

Is there a program available that will look at both the file being upgraded and the upgraded one coming from you and show where the mods were made?

How will I know which files to upgrade...how and where the mods were made on my “old files” ?

Can you provide the forum with a set of tips/ideas/guidelines on the procedures that should be taken to monitor the changes/mods made from software upgrade to software upgrade?


gsmith

[suzkaw]

Is there a program available that will look at both the file being upgraded and the upgraded one coming from you and show where the mods were made?

Upgrading a site with a lot of mods can be tricky. I use a tool called winmerge for file comparision and you can get it here:
http://winmerge.org/

How will I know which files to upgrade...how and where the mods were made on my �old files� ?

The hard part is you have to compare both files but with v3.1 almost every php file changed in some form or fashion.

So you could download the stock version of v3.0.15 and compare your modified files against it which would give you a better idea of what you have changed. Then you could take those differences and incorporate it into v3.1.

In all honesty there is not a really good way to upgrade a site and keep all your original mods without redoing them. The core code changes and even though a mod worked before doesn't mean it will now. So it is best to try and document any mods you add or any file changes you have made that way you have some sort of idea of what you have done.

This is also why we added the module system that way mods built using it are independant of 68 Classifieds core code.

If anyone else has some advice for upgrading a site like this please share your thoughts.

[garysmith]

So...with respect to the changes "I" make, it might be a good idea to log a small note that explains what i changed and maybe a copy of the code entered into a particular file as a means to track the file modifications...sort-a like a history of changes.

Maybe create a file folder called "v3.1 File Modifications" on your local machine and in it store a copy of all file changes being made to that version. The file changes and date of change then could be tracked.

Am I on the right track here?

Comments welcomed!

gsmith

[Lhotch]

Exactly Gary. Its also a good idea, if your code is a simple block of added content in a template or script, to put comments before and after it so you can quickly identify the section as not being part of the default file.

[garysmith]

Larry,

An example to that might read...

<!--This does this or that...(04/28/06)...(Larry's Special Code Change)--!>

gsmith

[Lhotch]

Originally Posted by garysmith

Larry,

An example to that might read...

<!--This does this or that...(04/28/06)--!>

gsmith

Yep, that will work for the templates. For the php you can just use 2 slashes....ie.

// This does this or that...(04/28/06)