Based on the following post: Surveys - Customize HTML layout to match enterprise visual code I was able to customize my survey. Now I’m trying to do more changes but unfortunately I’m afraid they will be lost on upgrade because for some reason the system is not picking files from the custom folder. Specifically files in folder modules/Surveys/Entry
How can I force the system to first pick up custom files for this module?
Any help will be appreciated.
I don’t see the problem. You should create entrypoints which override entrypoints for module
- make file:
- write code:
$entry_point_registry['survey'] = array(
'file' => 'custom/module/Surveys/MySurvey.php',
'auth' => true,
- create file:
custom/module/Surveys/MySurvey.php with your code.
That’s a good answer. The thing is that I’m planning to do other changes to the other folders as well.
For remember seen this post make customizations persistent from upgrades will try to see if it applies to my situation.
You can ask here about each change. Sometimes you can’t change file A in an upgrade-safe way, but it is required by file B, so indirectly you can make a custom B require your custom A.
Other times you can do similar things but with classes. I have a feeling that many (though not all) of the things that people say are not possible to customize in SuiteCRM are actually possible, though they require a few tricks…
I appreciate your responses. Will start testing and I’m sure I will come back with more questions .
I think that about 80% may be customised if you understand the code a little.
You can do for
Calendar and other modules which have file
- write custom code in
It will work after upgrade.
The problem with these more complicated approaches, which involve copying more files, is that it increases the odds that a future upgrade, despite not breaking your customizations, breaks the new SuiteCRM code instead, because it overrides parts of the new changes coming in…
It’s a trade-off, you need to choose which provides more benefits and less risks in your case.