Dolphin Blank v.7.0.9

This is just a dolphin directory structure void of all the files.  I use this for storing a copy of any Dolphin source files I modify.  It's quite useful when you have a number of altered source files on your server, and need to apply an upgrade patch.  I unzip an upgrade patch, then use Beyond Compare to show file differences between the upgrade patch, and my repository of change files in this directory structure.  If any of the files in my directory structure will be overwritten by uploading the Dolphin upgrade patch to the server, Beyond Compare makes it easy to transfer the file customizations to the corresponding files in the upgrade patch.  Then, when the upgrade patch is uploaded to the server, the custom edits will be in place.

You must of course, be diligent about storing to this directory structure, a copy of any source files you change. 

Thanks for the submission!  Shame not enough people realize the importance of keeping track of their changes until a patch breaks all the things.  Personally, I use Git when working on sites, but that method isn't for the sane.

Not only do you have to keep a repository of changed files, it's really important to add comments to the areas of the file that you've changed.   I add a "Edited by Name" comment to each and every edit.  That way, I just search any or all files for my name, to find edits.

Git makes tracking changes easier, but I still add a comment (with start and end comments).  Here's the process for updating a live site (when a madman's involved):

1. Change to code happens through Git repo.
2. Latest revision from Git is installed on a development site and tested.
3. Nothing broken?  Add the new code to the live site.

Database changes are taken into consideration.  Use of branches allow versions from Dolphin.  Git is then mirrored to a CVS repo on a 450MHz Pentium III machine running BeOS R4.5.

Great method of development for large sites that can't have people mucking around on the live site.  Massive waste of invaluable time for all other sites.  CVS is useless and should be avoided at all costs.

When working on client sites, I have a file which notes all the modified files and additions (e.g., $file was updated, $module was installed).  Combine that with the comments in the code noting the start and end of changes, and patches become a breeze.  Just need to edit them first.

I'll leave now.

A little too technical for the average Dolphin user here... that's why I posted something even a caveman could do.