i was getting annoyed at having to manage options in two places,
default.config and the database.
so, i've modified the install script to push all values from
default.configinto the database, if they are not there already.
NOTE: upon updating from svn or grabbing next snapshot, be sure to run the
install script (it won't hurt your existing data) or as an alternative, sav=
once on the options screen before grabbing the new files, to be sure all th=
values are stored.
what this means for the devs:
1. all new options need to be put into default.config when created. then
they'll get put in the database upon running install.php. (an alternative
would be to put these values directly into the install script, but i think
it's simpler elsewhere)
2. Kev, your defaultOptions model is deprecated. i've commented it out in
the code, if we need to rollback or something. all options are now in the
db, so it's not necessary to load them from the file.
Get latest updates about Open Source Projects, Conferences and News.