Drupal: staying in organizations with module changes

Question

The deeper I get with Drupal, the more I have to make changes to the code in other people's modules. Usually these are small changes, and still it makes no sense to rewrite the functionality of the module for my own needs.

I try not to make any changes to the Drupal core, as it seems like you're asking for problems.

But sooner rather than later, I will need to update these modules with new versions, and then return my changes again. How do you stay organized while making these changes, updating modules and reapplying your changes backwards?

I take as many notes as possible, but the web is growing around me!

Answer 1

Another key is to support explicit .patch files for any changes you make and include documentation in them. If you need to upgrade to a new version of the module, install a blank copy and reapply the hotfix. If this is not a repeated use, you know that you have a problem.

What supports your own source tree in SVN / git / etc may be convenient.

Answer 2

Do you change the module in a way that other people can use?

Then send the patch to the support module so that everyone benefits, and you have no problem staying organized.

Answer 3

question .

Nick Sergeants , , Drupal CVS, CVS, SVN.

Answer 4

.

1.) , , , .

2.) , - VCS (, Subversion) ..;)

Subversion drupal Drupal.org.

, (, (http://drupal.org/project/features)), , , , .

Answer 5

, Eaton , , , . , .

, , -, " ", , , , , - . , , , D.O. , . , , . , , .

Answer 6

" Drupal: " ( Wrox ) cvs/svn .

It's just $ 32 free shipping on amazon right now (as low as $ 24, but remember shipping for $ 4, you could also get it new. I recommend checking your library for it if it doesn't try try interlibrary loan, but this book describes exactly what you are looking for, step by step.