RT SiteConfig: Difference between revisions
Jump to navigation
Jump to search
m (5 revisions imported) |
(Added note about difference to customization with local-directory) |
||
| Line 4: | Line 4: | ||
You should never make any changes to [[RT Config|RT_Config]].pm - that is what [[RT SiteConfig|RT_SiteConfig]].pm is for. So for any changes you want made, copy the variables from [[RT Config|RT_Config]].pm and set them to your spec's in [[RT SiteConfig|RT_SiteConfig]].pm.. | You should never make any changes to [[RT Config|RT_Config]].pm - that is what [[RT SiteConfig|RT_SiteConfig]].pm is for. So for any changes you want made, copy the variables from [[RT Config|RT_Config]].pm and set them to your spec's in [[RT SiteConfig|RT_SiteConfig]].pm.. | ||
NOTE: This does not use the logic of the _local_-directory (see: [[CustomizingWithLocalDir]]) where the file is completely replaced. Here only the vars set in [[RT SiteConfig|RT_SiteConfig]].pm override those specific vars in [[RT Config|RT_Config]].pm, the rest of the vars in [[RT Config|RT_Config]].pm are left unchanged and still in action. | |||
Latest revision as of 04:13, 6 October 2016
see SiteConfig
The RT_SiteConfig.pm file is to preserve your settings between upgrades.
You should never make any changes to RT_Config.pm - that is what RT_SiteConfig.pm is for. So for any changes you want made, copy the variables from RT_Config.pm and set them to your spec's in RT_SiteConfig.pm..
NOTE: This does not use the logic of the _local_-directory (see: CustomizingWithLocalDir) where the file is completely replaced. Here only the vars set in RT_SiteConfig.pm override those specific vars in RT_Config.pm, the rest of the vars in RT_Config.pm are left unchanged and still in action.