On an upgrading basis...
Is it safe to completely change the config_defaults_inc.php? The main thing I want to know is? Does that file remain unchanged after each upgrade. In other words, after I make the upgrade, instead of configuring config_defaults_inc.php all over again. Is it safe to just replace the file with the previous working version (in my case replacing the default 1.0.5 with my working/configured 1.0.3)?
I did this at home and everything worked fine, except for the version, still showing 1.0.3...
Afterwards, I found out that the version is just a variable that can be changed (in config_defaults_inc.php). If this is right, this procedure would highly decrease time consumption between upgrades.
Hope you guys can help...
Thanks!
Upgrade: Replacing config_defaults_inc.php
Moderators: Developer, Contributor
In reality, your changes are meant to go into a file called config_inc.php (there's a sample somewhere in the main directory, I believe).
Only your changed variables go in to that file.
The idea is that on upgrade you can just copy over the top of config_defaults_inc.php to get any of the new variables, but it won't undo anything that you've already changed, because all of your changes are in a different file that is not overwritten.
Hopefully that makes sense!
Only your changed variables go in to that file.
The idea is that on upgrade you can just copy over the top of config_defaults_inc.php to get any of the new variables, but it won't undo anything that you've already changed, because all of your changes are in a different file that is not overwritten.
Hopefully that makes sense!
But then there´s this...
config_inc.php carries all the configs relative to connecting to the host, connecting to the database etc. That´s really the main config. But config_defaults_inc.php has configuration relative who is the guy that can delete bugs (in my case only the manager and up)... Again, it has configs relative to smtp servers for sending notifications... Etc...
config_inc.php doesn´t cover that section does it?
config_inc.php carries all the configs relative to connecting to the host, connecting to the database etc. That´s really the main config. But config_defaults_inc.php has configuration relative who is the guy that can delete bugs (in my case only the manager and up)... Again, it has configs relative to smtp servers for sending notifications... Etc...
config_inc.php doesn´t cover that section does it?
Palula, perhaps this explanation will help:
Whenever a Mantis page is generated, the files config_defaults_inc.php and
config_inc.php are read in that order. config_defaults_inc.php can set all the variables it wants to, but config_inc.php gets the final say.
So to set your own custom values, do that in config_inc.php—and preserve that file while updating!
Whenever a Mantis page is generated, the files config_defaults_inc.php and
config_inc.php are read in that order. config_defaults_inc.php can set all the variables it wants to, but config_inc.php gets the final say.
So to set your own custom values, do that in config_inc.php—and preserve that file while updating!