There are several ways to specify parameters that control how sigplus works and appears. This article elaborates on these options and their relative precedence to one another.
sigplus configuration is based on the concept of parameter stack. Initially, a single configuration object is pushed into the stack and each time a new configuration context is created, a new object is added on top of it. Unless overridden, the new object copies all properties of the topmost item in the stack.
The following contexts are in play when you use the sigplus content plug-in in an article:
- settings as configured on the plug-in page in the administration back-end (global settings)
- custom settings defined as key=value pairs, typed into the Custom settings multi-line text box on the plug-in page in the back-end
- settings passed via key=value pairs in the activation start tag (local settings)
The following contexts are applicable when you use the sigplus module:
- settings as configured on the content plug-in page in the administration back-end
- settings as configured on the module page in the back-end
- custom settings defined as key=value pairs on the module page in the back-end
Except for the very first context, which typically sets values for all possible parameters, subsequent contexts redefine only a subset of the parameters. In particular, you typically override settings for only a couple of parameters in the activation tag.