View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0018812||phpList 3 application||Configuration||public||09-08-17 14:46||06-10-18 22:04|
|Target Version||Fixed in Version|
|Summary||0018812: config_diff.php in addition to config.php|
|Description||Every time I upgrade phpList, I have to trace each and every change I made to config.php|
Unless you ever plan to move it into the GUI and be done with it, how about loading a file called config_diff.php after you load config.php?
That way, we'll put all our modified settings only in config_diff.php and not touch config.php at all.
Obviously we'll still need to monitor new and removed settings, but it'll be easier than now.
|Tags||No tags attached.|
@lwc Thank you for the report. When you upgrade phpList you can use your old config.php file for most releases, because changes there are made rarely. When changes are made, e.g. config options are added, then default fallback values are used in case they are not defined in config.php. Therefore the diff does not seem necessary. Changes to config.php, when they do happen, are stated in the release notes on phplist.org.
Do you agree?
No, I don't think it's safe to rely on the rarity of the changes and the trustfulness of fallbacks.
Plus it doesn't let me actually track what did I ask to change from the defaults without using a comparison program every time.