placement of editied sugar modules

[josh7272]

Hi,

I am looking at customising some core modules. This is with respect to the suggested customisations on previous threads regarding modules/Campaigns/ProcessBouncedEmails.php

As I am hesitant about these sorts of things, and I want to know if there is a recommended mechanism to achieve the testing of this. For example, does sugar implement some pathing mechanism such that I should place my changed file in custom/modules/Campaigns/ProcessBounceedEmails.php - and this will override the core module, but leave it in place for a) fallback and b) upgradability

Am I barking up the wrong tree here?
Any suggestions?
Thx,
Simon

[Angel]

The use of /custom works for some files, but not all. Not every file can be overridden, hence the reason why you might have noticed discussions regarding upgrade safe and core modifications.

What you want to shoot for is the former, as upgrades will respect your changes, etc. However, not every imaginable customization is possible via such upgrade safe modifications. In those cases, the only choice you have is to manually merge files upon upgrading.

Give this a look, it might help you get going:

http://www.sugarcrm.com/wiki/index.p..._Customization

[josh7272]

OK Thanks - that looks like a start.

It's a little confusing though. Am I correct to assume that my example of modules/Campaigns/ProcessBouncedEmails.php would be appropriate for column 2 of Actions (classic) ...<actions>.php

Is that the correct interpretation?
Also, do I need to restart apache/php to pick up the new version?

Thx,
Simon