Hi,
I am working hard on the new upgrade procedure. A new script allows to upgrade a DaDaBIK installation just by putting the new zip package into the "upgrades" folder and run the script; everything (files copy, database changes, ... ) is handled by this script.
One of the difficult parts is keeping your config.php settings if the config file (instead of the config_custom file) has been edited.
I am thinking about moving the config settings to the database: this would simplify the upgrade and maybe it's a good thing to do anyway.
In the config.php file we would only store the database connection parameters, while all the other parameters could be changed from the admin section, as it happens for Data -> Settings now.
It would be a big change and quite a lot of additional work, so I am curious to hear your thoughts about this, do you see any disadvantages in having the settings in the admin section instead of in a file?
I am working hard on the new upgrade procedure. A new script allows to upgrade a DaDaBIK installation just by putting the new zip package into the "upgrades" folder and run the script; everything (files copy, database changes, ... ) is handled by this script.
One of the difficult parts is keeping your config.php settings if the config file (instead of the config_custom file) has been edited.
I am thinking about moving the config settings to the database: this would simplify the upgrade and maybe it's a good thing to do anyway.
In the config.php file we would only store the database connection parameters, while all the other parameters could be changed from the admin section, as it happens for Data -> Settings now.
It would be a big change and quite a lot of additional work, so I am curious to hear your thoughts about this, do you see any disadvantages in having the settings in the admin section instead of in a file?
Last edited:
Upvote
7