After upgrading, how to point customized core file ...?

Developing for Dolibarr
, ,
1

Hi

As @eldy rightly said, “One size doesnt fit for all” resulting in customizations of dolibarr. While new features are handled through module builder, while enhancing / customizing few of the existing features, it is inevitable to modify one or more of the core files.

These modifications get lost during upgradations resulting in lot of rework. When releases are quite often, (like 16.0, 16.1, 16.3, 16.5, 17.0), needless to say about the work.

Is there any way to configure execution of dolibarr to the customized core files / folders by default and later modify them after upgradation…? or any other method…? @ksar or @eldy can guide please.

thanks and regards,
yesbee.

2

I always make a new local branch from the required dolibarr remote and then merge my modified version into it, works quite good thanks to eldy’s strict merge strategy (if big version increment, do major version by major version).