When working with FileBackup in combination with a DB backup tool, we're able to restore/move an environment while even the file-properties (rights) are saved. As all files are restored, the config.php of the moved environment still holds the path to the original domain.
Is there a way to make the paths in the config.php variable or editable through the backend. That way no editing of the config.php through FTP would be necesarry.
Why isn't some variable used f.e. the root-path where the config.php is stored, to make it more flexible?
Ronny
I installed "Config GUI", that works..
[solved] Method on editing the config.php from the backend?
[solved] Method on editing the config.php from the backend?
Last edited by RonnyK on Fri Aug 10, 2007 12:02 pm, edited 1 time in total.
Re: Method on editing the config.php from the backend?
I have seen some threads on making the paths more universal, but the database address, name, password, etc. is the problem, from my point of view...
but yes I believe in the forge there is a module to modify the config.php....
but yes I believe in the forge there is a module to modify the config.php....
Re: Method on editing the config.php from the backend?
Thanks for that, I wouldn't have found that based on the name. I thought it had to do with "Configuring the GUI" instead of the "Config.php GUI".
I understand the logic of the DB/Username/PW to be stored in the config.php, but what is the reason of the paths being there fixed as well, as the can be pulled dynamically based on the root-path? Is there a reason for putting it in there fixed?
Ronny
I understand the logic of the DB/Username/PW to be stored in the config.php, but what is the reason of the paths being there fixed as well, as the can be pulled dynamically based on the root-path? Is there a reason for putting it in there fixed?
Ronny
Last edited by RonnyK on Wed Aug 08, 2007 6:08 am, edited 1 time in total.


