$temp_id = 2;
$newObj = $modx->newObject('modSystemSetting');
$newObj->set('key','spform_id');
$newObj->set('value',$temp_id);
$newObj->set('namespace','spform');
$newObj->set('area','SPForm');
$newObj->save();$cacheManager= $modx->getCacheManager(); $cacheManager->clearCache();
$modx->reloadConfig();
The catch is that the system setting isn’t available in $modx->config[’spform_id’] until I manually clear the site cache, even though both the document and the snippet are uncached.
$s= $modx->newObject('modSystemSetting');
$s->set('key','aaa_test');
$s->set('value','test');
$s->set('area','test');
$s->set('namespace','test');
$s->save();
$modx->reloadConfig();
echo $modx->config['aaa_test']; die();
It tells the packaging system which settings are part of the core and which are part of 3rd Party Packages. I might add a combo to the system settings grids that filter by namespace.
Also, what are the ramifications of setting "namespace" to "spform" versus "core"?
Is there a plan to load (and maybe unload) system settings on demand by namespace as we do with lexicons? That would free us up to use system settings in snippets without taking a significant performance hit.
MODX Staff
So-called 3rd-party settings are not for simple Elements, and you must realize that every setting that is created is available globally to every developer in the site.
MODX Staff
Those not in the core namespace, which are installed as part of the core distribution.
Can you clarify what you mean by "3rd-party settings." I’m not sure I understand the term.
MODX Staff
That’s always been the purpose of default properties provided with snippets and plugins (and modules), to provide default values to be overridden by tags, or edited by developers when installing an Element.
I got excited when I first saw it because I thought it would let people set, and change, the default parameters of a snippet without having to edit the snippet itself. I still think that would be useful, as long as the values could be over-ridden by the parameters in the snippet call.
MODX Staff
I think the text is misleading, but this is what the default properties tab is for, defining default properties for the Element -- snippets and plugins that are "dependents" of a module can share that module’s default properties (i.e. they are inherited from the module), and this might be where the confusion stems from.
Right, but what’s the purpose of the "default properties" *tab* of the snippet create/edit page? The text there suggests that it has to be used with a module but it’s not clear to me why you would use it or what it would do.
