Re: Something like prepareDBSettingContext and saveDBSettings...
Reply #2 –
Meh, unless you guys have done serious changes, prepareDBSettingContext and saveDBSettings are geared totally towards pages of settings that fit into the show_settings template scenario. Anything that doesn't likely needs not only its own template but also a lot of handling and logic.
(It's not like there aren't places where fudging is done to make it fit into the prepareDBSettingsContext mindset, e.g. warning system combining multiple values into one $modSettings entry)
Having one uber template is cool but it can get very warty doing more than it originally intended.
Re: Something like prepareDBSettingContext and saveDBSettings...
Reply #4 –
I did one twist I on what saveDBSettings does in a new function, that basically allows you to use a standard confg_vars array, followed by a prepareDBSettingContext and then our buddy show_settings for display as normal.
The difference is that instead of adding rows per config var it instead interprets the config vars as the table cols ... so it adds/edits a single row to a specified table, with the supplied data as the insert col values. Could be lots more flexible but suited a need I had at the time and helped me avoid creating more templates.
So its yet another in the line of prepareDBSettingContext and saveDBSettings
Re: Something like prepareDBSettingContext and saveDBSettings...
Reply #8 –
I think the validation class and some other tricks cover pretty much all of that.