4

Overriding core files was how we used to make changes until collectively we figured out that was storing up trouble for the future. Another possibility is that if you think this is likely to be a small, useful improvement for most users of this aspect of CiviCRM then you could propose it as a change for core - go here and use the 'improvement' template. If ...


3

The simple answer to "Can I use the CRM directory that is auto-created by civix to easily store custom versions of existing CiviCRM PHP files?" is no, not easily. While it can be made to work, if you just use a modified copy to replace the core file, then you have to keep your file in sync after every upgrade, which is not fun. So yes it takes ...


3

A couple versions ago the concept of "hidden" extensions was introduced. The theory was it would allow for moving bits of code out of core and into extensions without anyone noticing any difference at first, and then at some point make them visible/optional. You'll find them in the civicrm_extensions database table and also in the ext folder in the ...


2

You can create a folder somewhere outside the main tree, so that when you upgrade core you don't overwrite your extensions, and then in civi under Admin - System Settings - Directories, you put the file path to that folder where it says "Extensions Directory". If you already have some other extensions installed, they might have gone under sites/...


Only top voted, non community-wiki answers of a minimum length are eligible