Request for comments: custom directory

sunsetsystems wrote on Wednesday, April 27, 2005:

I think it would be useful to have a separate directory in the openemr directory tree for site-specific custom files.  If we put everything that the user (installer) might want to change in one directory, then the installation process is more clear and upgrades are more manageable.

This interests me now because I am working on a feature to print statements and collection letters.  I have decided to implement part of this as a user-modifiable PHP function that generates the printable output, given an array of simple parameters (i.e. the function will not have to do any database lookups or know anything about the internals of OpenEMR).  So I’ll need a place to put it.

So I was thinking about creating a directory named "custom" at the root level (i.e. a sibling of interface, library, etc.).  Eventually we could move globals.php and config.php in there too.

Comments?

– Rod

tekknogenius wrote on Wednesday, April 27, 2005:

That’s a good idea. That way some customizations wouldn’t be lost during an upgrade. Is there currently a “map” of the OpenEMR code (directory structure documentation and what goes there). If not, that is something else for the next version… :slight_smile: