|
<releaseSettings> element
Defines opt-in settings for publication server behavior.
Introduced in 1.3 build 3, release settings are settings used to modify the behavior of the publication server. The settings defined here have in common that you are advised to use them, but they introduce a functional change, thus forcing you to double-check existing sites before enabling them.
Possible release settings
| Name | Description | Introduced in |
|---|---|---|
| immutableLocators |
See KB article |
1.3b3 |
| SyntaxErrorOnDoubleMacroIds | Like in HTML, macro Ids must be unique in SXML. However, when an errorhandler (macro with error parameter set) surrounded multiple macros having the same id, this syntactically incorrect situation was suppressed. You can make Smartsite throw a syntax error (non catchable error) instead by setting SyntaxErrorOnDoubleMacroIds to "true". |
1.3b3 |
| placeHolderSortNullValues |
The Placeholder macro can now assign a default value to the sort column for rows that have no value in the sort column. When you set the ReleaseSetting "placeHolderSortNullValues" to true, the placeholder will now assign the default value to rows that have no value set in the sort column. The default value is 0 for integer columns and "" for string columns. When set to true, the placeholder macro may output its rows in a different order compared to earlier versions. |
1.3b3 |
| EncodeUrlParameterSpaceAsDash | Setting this value to true makes Smartsite represent spaces in URL Parameter values as dashes, whereas normally spaces would be escaped as '$2D' | 1.4 |
| SwitchProviderOnSupportedDomainsList | When using multiple Active Directory membership providers, determining the appropriate provider for the domain of the user trying to login was performed by looking up the domain within the membershipMappings element and use the providerName attribute to get the name of the provider. As of iXperion 1.4 build 3, the preferred method is giving each membership provider its own settings configuration section, including membershipMappings element. In that case, each membershipMappings element then contains all supported domains for a particular provider and the providerName attribute becomes obsolete. See Multi-domaining support revisited for more information. |
1.4b3 |