By HAik-2 on

I am customising some of the modules to meet my requirments however I am afraid that updating them (update module) will overwrite my changes. I spent all the day in creating new modules out of the released modules i.e. rename them, create custom specific dbase tables etc. that I could avoid the overwriting and loosing my changes. Not with much success as the process is pretty lengthy and time consuming (sometiomes the original module clashes wit the custom one). I would appreicate if anybody could advise that whats the best practice in such situations.

thank you
HAik

⋅ Categories: Drupal 5.x

Comments

dww’s picture

dww
we/he/they
commented

Neither http://drupal.org/project/update_status (D5 contrib) nor the update.module going into D6 core (http://drupal.org/node/94154) ever touch your code. They just tell you if new versions are available.

___________________
3281d Consulting

aterink’s picture

aterink commented

I think he was referring to keeping changes to his modules when new versions are released.

I'd be interested to know seeing as I've made a few changes to several and when I upgrade them my tweaks will be lost. Would it be easier to make my changes into a patch that I can apply when I need to(I have no idea how to create patches) or go through and just copy my changes with each module change?

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

http://www.lullabot.com/articles/strategies_for_patch_management

Contribute your changes back to the community, so that it benefits everyone, and so you're not on the hook for maintaining those changes between versions.

HAik-2’s picture

HAik-2 commented

Thank you all for your advise.
At the moment I decided to keep teh customisation to minimum. In order to manage my updates in a simpler way and at teh same time keep the updates status visible I decided. in .info file cahneg teh version i.e. add my initial. This way in teh modul List view I will be able to see if the .module has custom code in it. If an update is available it is still be visible.
If I decide to update a hecked module I decided to backup my custom module. Update it and then go and implement my customisation in teh new version. It is vital to put lost of comments in teh code to keep track of my customisation.
patching sounds pretty good but looked complex to me. maybe i will take thet option when the customisation becomes intensive and non managable.

kind regards,

HAik