We need a solid, well-thought-out way to not only Read and Update settings, but also Create and Delete them. (and maybe Delete would only work on non-core/default settings; we could only Delete settings we add?)
Here are some quick example which should make the need and usefulness very obvious (especially when we get the ability to load/save batches).
update-setting Host Copyright = 'N'
update-setting Portal('0') EnablePopUps = 'False'
view-setting Portal EnablePopupUps // safe to default to Portal/0?
add-setting Portal('0') myCustomSetting = 'Debug'
delete-setting Portal('0') myCustomSetting
The ability to CRUD custom settings across Host, Portal, and other DNN entities will be incredibly useful.
I just made up the above syntax. You guys can figure out what is best. Second one could easily be
update-setting Portal, 0, EnablePopUps = 'False'
update-setting Portal 'Subsite' EnablePopUps=0
Can't forget that the portal identifier can be a string. Also might be nice to head off the confusion of how to handle boolean and dates so we all aren't wasting time on syntax for the meaning of the values we are trying to set (false, true, 'False', 0, -1, 1, 'Y', 'Yes', etc).
We need a solid, well-thought-out way to not only Read and Update settings, but also Create and Delete them. (and maybe Delete would only work on non-core/default settings; we could only Delete settings we add?)
Here are some quick example which should make the need and usefulness very obvious (especially when we get the ability to load/save batches).
The ability to CRUD custom settings across Host, Portal, and other DNN entities will be incredibly useful.
I just made up the above syntax. You guys can figure out what is best. Second one could easily be
Can't forget that the portal identifier can be a string. Also might be nice to head off the confusion of how to handle boolean and dates so we all aren't wasting time on syntax for the meaning of the values we are trying to set (false, true, 'False', 0, -1, 1, 'Y', 'Yes', etc).