separation of mantis source files from customization files
Posted: 14 Apr 2007, 09:30
mantis mingles the custom_*-files with all the mantis files in the base mantis directory.
Since I'm a fan of separating application-specific files (i.e. the application itself) from those used to customize the application, I use the following separation method:
* all customization files are collected in the subdirectory _custom
* the original custom_*-files only contain ...
where CUSTOMDIR is defined once in custom_constant_inc.php.
Of course these "forwarders" are a workaround, but neccessary since I don't want to touch the mantis application source code itself (so that I don't have to remember my changes and to apply any manual changes to future versions of mantis itself).
I would prefer mantis to look for the customization files in the directory _custom by default. That should be possible by a simple extension of core/core.php.
(Being new to mantis I don't know whether this is the correct forum to announce my question/proposal.)
Since I'm a fan of separating application-specific files (i.e. the application itself) from those used to customize the application, I use the following separation method:
* all customization files are collected in the subdirectory _custom
* the original custom_*-files only contain ...
Code: Select all
<?php
$file = CUSTOMDIR . 'custom_constant_inc.php';
if (file_exists($file)) {
require_once($file);
}
?>
Of course these "forwarders" are a workaround, but neccessary since I don't want to touch the mantis application source code itself (so that I don't have to remember my changes and to apply any manual changes to future versions of mantis itself).
I would prefer mantis to look for the customization files in the directory _custom by default. That should be possible by a simple extension of core/core.php.
(Being new to mantis I don't know whether this is the correct forum to announce my question/proposal.)