Compatibility Notes for 1.1

The Smartsite iXperion development team puts much effort into guaranteeing compatibility with previous, official releases. Sometimes however bugfixes may introduce problems with code that relied on the buggy behavior. In these case, our policy is to document the change and the possible consequences.

Locator.Query changes (work item 5229)

A bug in the base class for Locator.Query would result in improperly escaped data. The fix for this bug impacts the way query parameters are handled in sxml. The workaround required you to encode any parameters yourself, which will result in double escaping in Smartsite iXperion 1.1. Example:

Smartsite SXML	Copy Code
{url.setparameter($url, returnUrl, string.urlencode("http://mydomain.com/smartsite.net?id=whatever"))}

Should now be written as:

Smartsite SXML	Copy Code
{url.setparameter($url, returnUrl, http://mydomain.com/smartsite.net?id=whatever)}

The compatiblity setting "compatAlwaysEncodeQueryParams" was introduced to revert to the handling of releases older than 1.1.

ContentAccess Inheritance (work item 4920)

The database triggers controlling inheritance of content access have changed in Release 1.1. When new items are added (or copied), browse access is inherited from the parent folder for all items, independant of manager access. Before, different rules applied to folders and items, depending on the deprecated "Restricted" field of the new item and browse- and manager access settings on the parent folder. This made browse access inheritance difficult to predict.

Manager access is also inherited from the parent folder, but this inheritance is handled by cms code. Note that this is not a change from previous versions.

Other acces types are not inherited.

Viper overload matching changes (work item 5249)

ViperRegistration now matches the overload that requires the least amount of type conversions for the given set of arguments. This may require changes in the way vipers are called. For instance the viper

Smartsite SXML	Copy Code
{datetime.formattimespan(DateTime from, DateTime to)}

can no longer be called using implicit conversion of strings to DateTimes, because of the overload

Smartsite SXML	Copy Code
{datetime.formattimespan(DateTime from, String locale)}

which requires only one such conversion. In this example an exception will be raised, because no DateTime literal will match a valid locale identifier:

Smartsite SXML	Copy Code
{datetime.formattimespan("0:00:00", "17:00:00")}

needs to be called like

Smartsite SXML	Copy Code
{datetime.formattimespan("0:00:00", convert.todate("17:00:00"))}

Single sign on in the manager (work item 4995)

Smartsite iXperion 1.1 introduces single sign on functionality in the manager. When you login in the manager, you are also automatically logged in onto the publication server.

BBDecode viper (work item 4770)

Support for the font tag was dropped. If a font tag is found, the BBDecode viper will just return it's inner text.

Table AccessLevels (work item 4844)

The table AccessLevels has been removed from the site database. It is no longer used.

Friendly Urls word separator (work item 5078)

Friendly Urls now, by default, use a hyphen ("-") as word separator.

You can change the default character used as a word separator by setting the variable @whitespacechar within the stored procedure pr_FriendlyNames. After changing this value, execute pr_FriendlyNames 'PREP' to synchronize the Manager configuration with the new whitespace character.

Updates to the procedure pr_FriendlyNames will preserve the configured value for @whitespacechar.

Autonomous AIM flag only allowed within translations and rendertemplates (work item 5192)

The Autonomous AIM flag (AIMSource.Autonomous registration type within vipers and AIMScanMode.Autonomous scanning mode within macro's) is only intended to be used within translations and rendertemplates.

Therefore, now an exception will be thrown when the Autonomous flag is being used outside translations and/or rendertemplates.

Sitemap and view hierarchy macros inserted an extra levelformat when the root item was not displayed (work item 4967)

Using the default formatting, this resulted in an extra outer ul element, making the output non-compliant with xhtml. If the output has been fixed by dropping the ul element from the resultformat, the new version will have no outer element, once more breaking compliance.

To revert to the old behaviour set compatStartHierarchyAtLevelZero to false or set release compatibility to 1.02 or below.