I did a test with MIGXdb, needed to add small additions to get it work with tables, which have another primary-key than 'id' (modx_system_settings uses the field 'key' as primary)
the changes: (only fields.php and getlist.php)
https://github.com/Bruno17/MIGX/commit/ad259f0d30f43e317a64aa2f08530646c40023b5
after that changes, which will also be in the next release, its working with this steps:
create a namespace:
mysettings
create some system-settings:
key: mysettings.phonenumber
name: phonenumber
namespace: mysettings
area: global
key: mysettings.faxnumber
name: faxnumber
namespace: mysettings
area: global
go to components->migx -> tab 'MIGX'
create a new MIGX-config
tab Settings:
name: mysettings
formCaption: Setting
uniqueMIGXid: mysettings
tab Formtabs:
->create new tab:
caption: setting
->create new field:
fieldname: value
caption: Value
click: done,done to save and close both windows.
tab Columns:
->create two columns:
Header:Id - field:id - width:30
Header:Value - field:value - width:30
tab ContextMenues:
check 'update'
tab migxdbsettings:
classname: modSystemSetting
getlistdefaultsort: modSystemSetting.key
checkResource: no
where: {"namespace":"mysettings","area":"global"}
click 'done' to save the configuration
create a new TV
name: mysettings
inputType: migxdb
configs: mysettings
assign it to your template(s)
That's it. Now you should be able to edit your settings, which are in the namespace 'mysettings' and the area 'global', on each of your resources
[ed. note: Bruno17 last edited this post 11 years, 8 months ago.]