It is now possible to run the cms manager on a 64-bit OS. However, the application pool for the cms manager must be configured to run in 32-bit compatibility mode (Enable 32-bit applications=True).

The 'Preview Logic' field for Translations can now be used in AIM rendering mode, by adding a call to aim.usepreviewlogic() to it.

When passing property values over the querystring, smartlets could read each other's values when sharing property names.

The aimOptions parameter was ignored in the Html.Link() viper.

Only the first request to an item of contenttype File Link, the url was resolved correctly. Subsequent requests returned no reference to the url.

This has been fixed.

Files that are used within content items will have a corresponding entry (using the file's relative url) within external references.

When you try to delete a file using the File Explorer within the cms manager, the external references are checked against the relative url of the file.

If the external references contains an entry with the same url, than it means the file is in use and you will not be able to delete the file (the cms manager will display an error message that the file is in use).

However, sometimes it was possible to delete a file without warning, because under certain circumstances the relative url is/was stored with a leading forward slash within the external references, and the url being checked is without the leading forward slash.

The url check have been adjusted, and now checks the relative url with and without the leading forward slash.

When importing content using the option "Import as Active", the friendly name as specified within the xml is not taken over. This has been fixed.

• check for external webservice http handler configuration within web.config (if appropriate)
• check server instance id's
• check SmartNumbering configuration (if appropriate)

Use CustomRequestBody to set the body, CustomRequestContentType to set its MIME type.

The character set is determined based on (if present, in this order):

• The byte order mark in the response stream
• The encoding attribute in the xml declaration of the response
• The charset parameter of the Content-Type response header
• The default set in the http standard: iso-8859-1

The Recent Edits action now offers a way to load the selection into the CMS TreeView

Several components of the publication engine, such as Smartsite.AspNet.Bridge.ResourceHandler, internally still relied on the COM resource handler SixCoolBlueSkin.dll.

This dependency has been removed and replaced with the .NET equivalent resource handler Smartsite.Resources.CoolSkin.dll.

The TestSuite now displays cumulative time spent in each of the SXML source items in the Dependency List.

The AIM raw data scan did not find links in textfields with AIM=1 and AIMType=<SOFTLINK|HARDLINK> settings.

The database update scripts and add-on modules for SQL Server and Oracle are invoked by the UpdatePublication.hta. This way exact the same technology for executing database scripts are used for both the CLI as the graphical setup.

A more natural syntax is introduced for usage in XSLT. Viper functions are now available directly and can be combined with native and other extension XSLT methods.

You can now see:

• the total render time per dependency during the last rendering
• a visual cue that an opened item was used for the last rendering
• more details about the item

The forward slash is used to split multiple Oracle sql statements. A parser bug prevented the forward slash from being used as a divide operator.

In previous releases, content relations had to have a column named "Nr". By specifying the CTFP "ExternalKeyField", you can now use a column with a different name in the content relation view.

The Scf macro always used the Default Channel for rendering includes.

The generic method Scf.Script.Enabled() could not be used outside of Smartlet items.

In the default formatting scenario, the OuterClass property was not passed to the createsmartletbox() translation call.

This meant that only items that were accessible to groups which contained the user's current role were shown.

Affected macros and vipers include

• Parents
• Siblings
• SiteMap
• XLinks
• Security.ContentAccess.*

The TestSuite sometimes threw a NullReferenceException when validating a field.

Within Smartsite.Logging.config, for each logtype (Information, Warning, Error and Trace) filtering can be enabled by adding an (nested) filters element to the logtype, e.g.:

<logtype name="Trace" defaultminlevel="1" defaultmaxlevel="2">
   <filters>
      <filter category="Module" minlevel="1" maxlevel="5" />
      <filter category="Parser" minlevel="0" maxlevel="0" />
    </filters>
</logtype>

However, the category attribute needed to be specified in the exact same casing as the logmessage-category which is used in code.

As of iXperion 1.3, this is no longer needed. The categories as well as the logtypes are now case-insensitive.

The Smartsite Logging functionality, based on the Microsoft Enterprise Library Logging Application Block, supports four logtypes: Error, Warning, Information and Trace. The logging viper class gives access to this logging library.

However, there wasn't a viper available to add a warning. This has been fixed.

Also, two new logtypes have been added: Verbose and Critical.

The cms manager has its own logging mechanism, which is configured using the Logging registry key within your site's registry key.

As of iXperion 1.3, it is now also possible to bypass this "legacy" logging mechanism and push all log messages to the Logwriter, which is running as integral part of the publication engine.

To enable this functionality, set Enabled to 0 (=false) within the Logging registry key to disable "legacy" logging and add the registry setting CmsLoggingEnabled with value 1 (=true) to enable pushing the log messages.

From then on, the only logging config (loglevels and which category to log) in use is the Smartsite.Logging.config file. Also, the log destination(s) for the cms (manager) logging messages can be configured the same way as you would configure logging for the publication engine.

You could not use the {request.query()} viper to read querystring parameters in a cms:region in an .aspx file.

All viper methods to read and write files are now located in the global viper class filesystem.

The default location for all logging (both publication and cms engine) has been changed.

A folder "LogFiles" directly under the site-root will now be used, with subfolders for the manager (Six), publication engine (Cms) and WCF trace logging (WCF).

The Config Editor does have two new options available on Site-level (within the context menu): "Set Site Url" and "Rename Site".

The option "Rename Site" changes the name of the site. This includes moving the content of the existing site-folder to a folder with the specified site-name, creating a new registry key with the specified Site-name and copying (recursively) everything from the old registry key into the new registry key, and adjusting the site-url's (incl. service addresses) to use the new site-name.

The option "Set Site Url" changes the base-address which is used within various url's within the site, such as the ServerAddress, ManagerAddress, TestServerAddress and the (WCF) service addresses. Also the hostheaders within the Smartsite.config (channels configuration section) are adjusted as needed.

Because the last modified date of the render template was ignored in determining the last modified date of an item, changes to the render template did not trigger cache updates.

A request to an image that was receiving image commands through both the querystring and sxml caused the request to the image to hang.

The new commands are defined in the Smartsite.ImageProcessor.config:

<!-- set DPI resolution -->
<add id="dpi" type="Smartsite.ImageProcessor.Commands.DPIResolutionCommand, Smartsite.ImageProcessor" enabled="true">
  <parameters>
    <add name="resolution" shortcut="dpi" />
    <add name="horizontal" shortcut="dpix" />
    <add name="vertical" shortcut="dpiy" />
  </parameters>
</add>

The DigiD membership provider, when it initializes, loads the profiles as specified within the Smartsite.DigiD.config configuration file.

When this file contains two profiles with the same name, you're site will fail to start with the exception "An item with the same key has already been added."

To give a better error message, the DigiD membership provider does now check for duplicate profiles and throws the exception "Duplicate profile '{profilename}' detected within Smartsite.DigiD.config.".

When running the UpdatePublication.exe, the web.config will automatically be updated to the new recommended configuration.

For IIS 6, the new recommended configuration is:

<httpHandlers>
      <add verb="*" path="*/*.net" type="Smartsite.AspNet.Bridge.Handler,Smartsite.AspNet.Bridge" />
      <add verb="*" path="/res/*" type="Smartsite.AspNet.Bridge.ResourceHandler,Smartsite.AspNet.Bridge" />
      <add verb="*" path="/res/*/*" type="Smartsite.AspNet.Bridge.ResourceHandler,Smartsite.AspNet.Bridge" />
    </httpHandlers>

For IIS 7, the new recommended configuration is:

<handlers>
   <add name="PubResourceHandler" path="/res/*" verb="*" type="Smartsite.AspNet.Bridge.ResourceHandler,Smartsite.AspNet.Bridge" preCondition=""/>
   <add name="net" path="*.net" verb="*" type="Smartsite.AspNet.Bridge.Handler,Smartsite.AspNet.Bridge" resourceType="Unspecified" requireAccess="Script" preCondition="integratedMode,runtimeVersionv2.0"/>
   <add path="*/*.net" verb="*" type="Smartsite.AspNet.Bridge.Handler,Smartsite.AspNet.Bridge" name="Bridge" preCondition=""/>
</handlers>

The .NET stack trace is now available and displayed when a render exception occurs when previewing an item within the cms manager.

The publication engine already had code to disable the so-called File Changes Monitor, which is responsible for causing an appdomain unload when a folder is deleted.

The http handler for the cms manager now also includes code to disable this File Changes Monitor.

In rare occasions, when calling a webservice, you are required to pass specific soap headers as part of the webservice message.

The se:webservice macro does now support this scenario: just specify the "raw" soap header(s) as xml string using the RawSoapHeaders property.

When a <link> element didn't contain a Url, the FeedReader macro would fail.

Function DATALENGTH() has been added to Oracle to retrieve the byte length of a BLOB field.

When adding virtual directories with Default Documents under IIS, Smartsite would erroneously do security checks, resulting in failing requests.

The LDAP Gateway, which is used through COM-Interop when the cms manager has been configured to authenticate against Active Directory, did use Basic authentication by default.

This resulted in a limitation of the search requests that could be performed: you would need to specify the (full) distinguished name of an "OU" (or "cn=Users") and only users within the specified OU were found. Users within another OU (on the same level) couldn't be found.

This was actually a security issue, because a connection established using Basic authentication is limited to search operations on the specified root (the searchBase) only.

The LDAP gateway has been changed, and now automatically switches to Negotiate authentication when the specified username (connectionUsername attribute within the membership provider element) represents an userPrincipalName (username@domain).

This way, search operations are not limited to the root (=searchBase) specified but will also search for the specified user on any level within the domain hierarchy.

Also, the logon handler SixSecurity.LDAP have been changed and will now also use the userPrincipalName to validate the user's credentials.

The Active Directory membership provider had a built-in default for searchUserQuery: "cn=Users".

When the membership provider must query for an user, this searchUserQuery is used to create a new DirectoryEntry, which is then used to execute the search request. So, by default, the membership provider would only find users which are member of "cn=Users".

And although the default searchUserQuery can be overridden (on the membership provider element) with an alternative "OU", the provider should be able to search for an user on the "root" object (and any level within the domain hierarchy).

The Active Directory membership provider has been changed and doesn't specify a built-in default for searchUserQuery anymore.

Therefore, if you don't specify a searchUserQuery within the membership provider element, search operations for an user are executed on the "root" object.

When you do specify a searchUserQuery, then this searchUserQuery is used to create an DirectoryEntry object and that object is used to execute the search request. This means, if you specify a searchUserQuery, all the domain users which must have access to Smartsite must be a (nested) member of the specified "OU".

With the recently added feature of caching the AD/LDAP user objects after a successful logon, a bug was introduced which resulted in user information (such as group membership and primarygroup) not being updated anymore once the user has been added to the database. This has been fixed.

Some dataeditor meta xml files have been adjusted to hide these superfluous relations.

The IISRestart tool which comes with iXperion 1.2 has been enhanced to support IIS 7.0.

However, this has introduced a dependency towards the Microsoft.Web.Administration assembly, which isn't available on Windows 2003.

This was causing the error messages for certain commands, and this has been fixed (by refactoring the code, so .NET doesn't try to load the IIS 7 specific assemblies).

The entered database server login is validated by the script. If it does not exist, the script is able to create the login with a default password.

Some appSettings from smartsite.config were already available within the Config Editor, such as Description, FriendlyName, ServerAddress, etcetera.

But the Config Editor now also offers a special appSettings editor for all other application settings encountered within the appSettings node of the smartsite.config. The editor also allows you to add/delete settings.

Not due to the fact that the userroles configuration is faulty, but because when using an Oracle database the "select count(*)" queries do return an decimal (which can not be cast to an Int), whereas for an SQL database it would have been an Int.

This problem also occurred within the friendly names validator and has been fixed using an explicit Convert.ToInt32().

When copying field data the repository components would apply only the write textfilters to a field, resulting in extra encoding. For example: & would become &amp; etc.

In the TestSuite, the debug option "Suppress custom error pages" sometimes didn't work.

The task pane will check every 30 seconds if any task for the user has been updated. If so, the task pane will refresh.

If the search results contained items with <, > or & in the title, they would be displayed as &lt;, &gt; and &amp;.

When the cms manager has been configured to use Windows integrated security (logonhandler set to SixSecurity.LDAP), content validation and previewing an item did fail, which resulted in being unable to save item(s). This has been fixed.

As a result, when a browsestartpage was configured for a specific hostheader, this configuration setting was lost when saving other changes.

The AIM external reference monitoring background component LinkSpider could hang on file:// references and terminated itself when errors occurred during spidering.

DataEditor actions within the cms manager do now also support a button lay-out of the "Close" button only (in stead of the default Save-Cancel buttons. To switch to this button lay-out, just add the action parameter "ButtonLayout" and set its value to "Close".

When the (connectionstrings within) Smartsite.Data.config file had been encrypted and the cms manager had been configured to use the logonhandler SixSecurity.LDAP (Active Directory integration for the cms manager), any login failed with the error message "One of the database elements does not have a connectionstring element".

This has been fixed, the Smartsite.Data.config will now be decrypted when it's loaded.

The default formatting in the webtoolkit calendar macro did not apply the given dayformat to the first weekday. You had to set the format parameters for that.

You can now represent querystring values in the URL path, thus generate even friendlier URLs in your SXML applications. Example: http://domain/search?q=test&page=1 can now be written as http://domain/search/test/1.

The cache file macro added some duplicate response headers, such as content-disposition and content-length. As a result, some browsers didn't/couldn't download the file.

Specifying two default host headers for a single channel is not a valid configuration. Previously the site would start with either one as the default host header. From now on, the site will no longer start.

The error only occurred when a single folder without any child items was selected.

The error message was: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_ContentVersions_Contents".

When UAC enabled, COM code may write to a virtual registry instead of the physical registry. This will cause unpredictable behavior of the setup, possibly corrupting the installation of Smartsite. Therefore, when running the Smartsite Publication Setup, a warning will appear if UAC is enabled.

The login url for forms authentication (web.config) can now be overruled per channel, by setting the CMS field 'LoginUrl'

Due to a bug (unfortunately introduced within release 1.2), the Outscaling Synchronizer always reported "Illegal Url" when trying to synchronize a file to another server.

Smartlets can now trigger events in order to communicate state to their environment. Both other Smartlets and standard SXML and client code can be used to bind to these events. Search for "Smartlet Events" in the documentation for more information.

The 1.3 database update script will rename the LogEntries.Level column to LogEntries.LogLevel ("Level" is not a valid column name within Oracle).

The Smartsite.Diagnostics.Logging assembly and the LogMonitor executable have been adjusted as well, to reflect this change.

This means, that the LogMonitor which comes with 1.3 can not be used to open the database log of an 1.2 site and vice-versa.

When previewing Smartlets in the TestSuite, some methods, like GetOrigin(), did not work correctly.

When activating the 'Suppress Custom Errors' debug option in the TestSuite, the call stack will now be displayed when errors occur.

When a content item was attached to a repository item, updating the item from the updated repository item could cause data loss in fields shown with the webEditor, when on secondary (not initially displayed) tabs.

A new viper has been added: Channel.IsVisible() can be used to test whether an item will be visible in a given channel, taking all the rules of the channel (item state, publication date range, subtrees) into account.

Saving thesaurus relations on a non-physical field failed, when the same thesaurus was used on multiple contenttype fields (within the same contenttype) and the thesaurus relations have been made sortable. This has been fixed.

This means the viper call will remain unresolved, unless a default is specified.

Depends on compatibility setting "compatJsonReturnsNulls".

When using linefeeds in html attributes outputed by pagetranslation collection members, the linefeeds would be escaped internally during the XML reading process, causing errors when executing the vipers.

When an error parameter contained the viper this.error.throw(), it would re-trigger itself and cause double execution.

Over multiple calls to the same translations, savebuffers declared in the translation would be preserved. This can lead in unpredictable behavior and has been fixed. However, the fix is potentially breaking, so a new compatibility setting,

'compatClearSaveBuffersOnInstructionSourceChange', has been added to revert to the behavior before 1.3.

From iXperion 1.3 the SecurityZone of the logic field in ContentType AWP is increased to HighRisk.

Site.Config.GetValue, .GetSection, .GetEncryptedValue and .GetEncryptedSection

Use se:for macro to iterate through JSON values.

When specifying collection parameters as xml attributes, using commas in values used to be a problem. You can now specify one of the following characters: ';', '|', '/', '\', '~', '#'. To force the use of the correct delimiter character, enclose the entire attribute value using the chosen delimiter.

For instance: save="|a=this.result(datatable, default=datatable.createempty())|b=this.getparameter(resulttype)|"

Douglas Crockford's JSON.parse() method has now been integrated into SCF: jQuery.scf.json.parse(). See JSON.org for details.

Under circumstances, loading a previous version while using webEditor controls in secondary tabs in Edit Item, could cause data loss.

The SetCurrentPage() viper can be used to programmatically set the current page in a paging macro.

Using Initialized(), you can differentiate between the fact that there are no records to display or the totalcount has not been set. The GetTotalCount() viper returns 0 in both cases.

In some cases, code in 'error' parameters was not executed properly.

Sys.GetTypeName() had no awareness of DataTable, Xml etc.... Use SXML.GetTypeName() instead

The Exists() viper method was added to the ContentType group.

The TestSuite interfacing with the publication runtime has been optimized, resulting in better render performance.

You can now set the appSettings value 'SilentSessionAccess' to 'true' to make previewing items with sessions a lot easier. When this setting is used, no errors will be raised you can simply use a default value in session.get().

The Smartlet class in client-side Scf now has a name() method, that works like the name() Viper method.

Running Ajax calls from a Smartlet were automatically aborted when starting a new Ajax call. This is undesirable. The Smartlet developer can decide when to interrupt running calls or render the UI inaccessible to prevent the user from re-sending an ajax call when waiting for a previous one to return.

You can now use the InputData parameter to display custom tag clouds. Just pass a DataTable with the columns Nr, Name and UsageCount to the Tags macro.

When using CombineCssClasses(), the result could contain doubles

You can now apply CSS skins to Smartlets by using the boxskin named parameter or by setting the SmartletConfig_defaultSkin page buffer. Search for "Styling and Skinning Smartlets" in the documentation.

You can now configure your site to accept forms-based logon suppression, for applications outside Smartsite iXperion to access secure pages.

Automatic includes aggregation can now be suppressed by selecting 'Include non-minified Javascript and CSS if available' in the TestSuite debug options, or by adding the querystring variable hid=scf;minify=0 to a page url.

Scf now comes with jQuery 1.4.2.

The paging macro now has firstresult() and lastresult() methods that return the index of the first and the last result on the current page respectively.

When setting the AjaxError property, the actual exception's message was displayed on the client, instead of the value of the AjaxError property.

When you have a preview session open (TestSuite, Manager preview), the viper method ItemData.Field() and the ItemData macro will now use the session's data instead of going to the database.

A new overload is available to allow for a fallback scope that should be used instead of the given one, if the translation passed is not available there.

A new viper method, translation.caller(), was added. It provides a way to look up the call chain and see which item is calling your translation.

Now that Datatable.Compute returns null instead of DBNull, you can use the default parameter of the viper method to handle cases where the compute method return null as a result.

Pressing F12 while editing text in the TestSuite will directly bring you to the item under the cursor. It understands numbers, translations (first looking for scoped ones) and codes, friendly names and titles.

Generates a compact string for the location (number or friendly code for CMS items, url for files).

The smartlet.number() viper always returns the item number of the Smartlet itself. It is comparable to translation.number(), but will also work in Ajax scenarios where translation.number() is not applicable.

When a non-existing value was set twice in the same roundtrip, it was not persisted.

The method returns the user id if a user is logged in. You can use the default parameter to have the method return an alternative value if no user is authenticated.

Preparser now takes more context into consideration.

Smartsite Faceted Search allows usage of unicode characters.

XmlDatatable macro now sets its result type to DataTable if the result type is undefined and a single buffer name is used in the Save parameter.

This method can be used to try to determine whether a string was base64 encoded.

This method retrieves the default value of a Smartlet property.

Using the unsaferead attribute.

Starting with Smartsite iXperion 1.3 UDFs fn_HexStrToVarBinary and fn_ResolveNumericEntities are introduced in order to support unicode characters (nvarchar). These functions are prerequisites for Faceted Search.

The Locator object Smartlet.Page() pointed to, was mutable.

Pressing Shift-F12 will make the TestSuite look for incoming references to the selection in the editor, the currently selected item in the tree, or the item on the current Url. It uses the AIM spidering state to get the references, just like the References tab in the Manager.

In the options dialog, the address entered as TestServer Address is now checked against the local machine.

Due to a bugfix, intellisense showed duplicate overloads on placeholder vipers.

Until 1.3, code within regions shared local buffer scope, even over multiple SXML sources. This meant that buffers that were set in translations called from within a region, the locally defined buffers in those translations would be available to all code within the enclosing region.

This has been changed in 1.3, because regions should only limit the scope of locally defined buffers, not change the scope of buffers in other SXML sources.

To revert to the pre-1.3 behavior, add a value to the appSettings section in the Smartsite.config:

<add key="compatRegionOverrulesLocalBufferScope" value="true"/>

Use the surroundSelectionTag method instead. This has the added benefit of being able to span multiple block elements correctly.

When editing floating point values in the CMS, listbox and dropdownlist controls sometimes did not select values as stored in the database.

You can now use string.quote() for both double and single quoting.

When deleting or setting multiple items to inactive or archived, relation constraints were not tested correctly, resulting in the action to fail, even when only relations between the items themselves were found.

The HTTP Response SubStatusCode could not be set from SXML. Some actions require a substatus code, such as '403.4 SSL Required'

When called in requests on a non-default hostheader, url.setitemnumber() would reset the url to use the default hostheader of the current channel.

In the TestSuite, the call signature of translations in edit mode can now be changed without the need to save first.

When a raw parameter was executed while already in raw parameter execution, the 'this' scope could go wrong.

When a macro had a condition parameter that did not match, the 'this' scope in vipers immediately after the macro closing tag could be wrong.

When explicitly setting the locale in a page, Smartlets would not be aware of this when in Ajax callback mode.

Using the abortPrevious (boolean) property, you can make sure previous requests to the same Smartlet are aborted before sending the new ajax request to the server.

The For, While, DoWhile macros now have a this.break() viper method for exiting the looping condition.

Because the content disposition filename was not placed between quotes, the filename was truncated at the first whitespace.

Because the external references in the inline html are now resolved before the html is sent to the pdfprocessor, the pdfdocument can now be used to render pdf documents in a restricted environment where not all external references are publically accessible.

When using the SqlQuery macro on an Oracle database with a single statement (containing named parameters) and the params collection contains superfluous parameters, the query would fail with the message "Illegal variable name/number".

This has been fixed.

The default busy indicator shown when jQuery().scf.busy() was used, could not be styled easily, because the HTML used by it was appended to the body element. Instead, it is now added to the parent of the element the indicator is shown on.

_disableEscaping settings 2 and 3 are handled as 0, meaning that all ampersand characters are escaped to &amp;

This fix means a functional change: if your site already uses an HtmlEdit control and you've created specific textfilters to work around this bug, these filters should now be changed back to the default Smartsite iXperion filters.

This is useful for adding query parameters using the url.addparameter viper.

SEO Priority problems that occurred when the regional settings of the server hosting your site is set to Dutch:

• Copy/paste of an item for which SEO Priority has been set to "Medium Priority" (=0.5) failed with the error message "Error converting data type varchar to real".
• The SEO Priority field wasn't rendered properly within RAW channel, which results in Import/Outscaling misinterpreting the SEO Priority value.

This problem has been fixed within iXperion 1.3 build 2 and 1.2 build 6.

The recommended work-around for earlier releases is to set the regional settings on the server hosting your site to "English (United States)".

The unnecesssary cache could lead to unnecessary memory consumption.

Under circumstances, an error parameter would not trap an exception in a macro.

This could cause a script error during the installation of Faceted Search.

The 1.3 update script does now check if the appropriate collation is set on the column ResourceValue and the column ResourceKey doesn't have a specific collation set.

To fix this issue in existing installations change the following code

request.query(q)

to

request.query(q,true)

in the sml_FacetedSearch() smartlet and Open Search Example in the Examples folder.

To get the Open Search Example to work, you will also need to change every instance of

{buffer.get(searchterms)}

to

{string.xmlencode($searchterms)}

in that item.

The XmlDecode will now only be done if the Encode property was set to true when creating the Xml Document, for instance using the XmlProcessor macro.

The update script will restore this http handler.

When any ContentType does not contain all required fields in its ContentTypeFields set, iXperion will not properly start. This was fixed in update to 1.2 scripts but the logic was missing in the 1.3 build 1 script.

For Subscribers of an Outscaling implementation, field SEOPriority was not added to the PhysicalFields table.

Previously, the TestSuite always used feature 3 (=SiteInstance) which could lead to concurrency problems (usually feature 3 only allows 1 concurrent login).

When the table SubtreeHierarchy has been configured for manual synchronization, the list of subtrees created when synchronizing the datasource was (sometimes) incomplete. To fix this problem, the meta xml for this table has been adjusted, as well as Outscaling to always use the (default) meta xml for manual synchronization.

The error status passed over the querystring is now used in Smartsite Error Pages, to set the HTTP status accordingly.

When there are more than 100 items (or registry setting MaxRecordsPerQuery items, which defaults to 100) with the same activation date, Outscaling fails to synchronize the 100+ items and will enter an endless loop of sending the first 100 items over and over again.

This was due to a bug in the mechanism of determining which items to send when the MaxRecordsPerQuery (default 100) number has been reached.

When you encounter this problem in a previous version, the workaround would be to increase the MaxRecordsPerQuery value (registry setting for the Outscaling background component) to a number which is higher than the number of items with the same activationdate. After changing this value, you would need to restart the site.

Only the first encountered contenttype-field not listed within the xml was removed. When you had e.g. 4 contenttype-fields within the contenttype being updated which are not listed within the contenttype xml, you needed to import this xml 4 times to remove all these 4 fields.

To be more specific, when the option "Replace item-number in URL's with item-code" (Advanced settings page) has been selected, the export wizard will now also replace item-numbers with item-codes for contenttype fields using (SixSmartUI.)LinkInput as EditProgId. This includes the Url field for items of contenttype Reference.

The TestSuite now notifies the user that it is displaying a website that is not rendered by the TestSuite by giving the url textbox a different background color.

The schema supplied by W3C did not work as is and needed a small modification to work with IntelliSense.

The new scf behaviour "aHrefTargetBehaviour" will make links decorated with the class "target_blank" open in a new window.

For items marked as XHTML Strict or "Webrichtlijnen" compatible, the webEditor allows the user to add this class by checking the "Open in new window" checkbox.

The Session.Id() viper method did not resolve on first request, nor in embeds.

The UPPER clause in queries is used because Oracle is case-sensitive. This is usually no problem, most tables queried have a limited set of records.

However, the eventqueue tables (osEventQueue and osEventQueueStatus) sometimes do have a lot of records in them in which case using an UPPER clause has a negative impact on the performance. For SQL Server, since it is case-insensitive, the UPPER clause is not needed, so it is has been removed.

Previously, for some errors to be shown, you had to load the /smartsite.net document because the / document was showing a different error. Now both paths show the same error.

When a fatal error occured in PubSetup, the entire utility closed after the error message. However, this behavior is not desired because often more information is printed in the setup status, which then would be lost. Now, after a fatal error, the window will still be visible.

When previewing rendertemplate-local system translations, the global version would always be shown.

Generally speaking, for the best performance, enable the compiler for small xslt's and large xml's and disable the compiler for large xslt's and small xml's. The compiler is on by default.

Within the cms manager it is only allowed to add or remove a contenttypefield on a contenttype group.

However, the import contenttype implementation did only add/remove the contenttypefield on the target contenttype.

This has been fixed. When a contenttypefield must be added, it will be added to the (main) contenttype the targeted contenttype is derived from (if applicable) and to all its derived contenttypes.

Removing a contenttypefield during contenttype-import will now only be allowed if the target contenttype is not a derived contenttype. If that's the case, the contenttypefield will also be removed from the derived contenttypes.

Under circumstances, code could get executed despite the fact that an exception had been raised and caught in an error parameter.

When using the clipboard copy/paste tool in edit item or in DataEditors, the 'Paste' action visually selected or deselected checkboxes, but the underlying value was not updated, resulting in possible data loss. Also, all RadioButtonList data was skipped during copy/paste

The dataeditor meta xml file for UserRoles for both the standard and professional editions did contain self-closing caption tags, which caused the controls to be rendered on the wrong tab.

When a registry action like RegSvr32 or RegAsm fails for any reason, the CMS Setup will show such occured errors at the end of the setup.

The Sendmail macro now supports unicode characters in mail addresses in the To, Bcc and Cc fields.

Fixed this bug by removing Schema CTFP of field Answers and adding SchemaSetId for this field of ContentType POL.

An extra check was added to the CMS to prevent conversion from non-empty folders to normal items by exposing the 'Folder' checkbox in Edit Item, and thus bypassing the 'Convert To Normal Item' action.

Now a subtotal has been added for those reports where the number of displayed rows is less than the number of rows in the database.

When images are embedded inside an email, the receiver of that mail no longer needs to download the images from an external server but the images are shown immediately because they are included in the email. Images that are not embedded in mails are often blocked by mail clients due to privacy concerns.

To fix this issue in an existing site, edit the translation CacheTopicList() in the Forum smartlet folder and add the line

{aim.events.bindtocontentchange(smartlet.page())}

below the line

{aim.cachekey.add(url.getitemnumber(smartlet.page()))}

In previous versions, datatable.findone always returned -1 when no row was found. For ease of use, datatable.findone now returns the default value when no row is found and a default value is specified.

During validation, SetSiteSecurity failed to validate read access if it encountered a file that was locked by another process. It now skips files locked by another process during validation.

This was actually a storagehandler loading error, which could occur for other tables as well.

The SimpleLookupStorage storagehandler tried to determine the identity field, which failed if the identity had been removed from the table for which the storagehandler is being initialized. This has been fixed.

The protocol version which should be used on the LDAP connection can now be set using the ProtocolVersion setting, e.g.:

<Smartsite.ActiveDirectoryConfiguration>
	<settings>
		<add name="SmartsiteAccessGroup" value="SmartsiteAccessGroup" />
		<add name="ManagerAccessGroup" value="ManagerAccessGroup" />
		<add name="StoreFullyQualifiedLoginName" value="False" />
		<add name="SearchBase" value="DC=domain,DC=organization" />
		<add name="DatabaseId" value="manager" />
		<add name="ProtocolVersion" value="3" />
	</settings>
	<membershipMappings>
		<add name="mm1" domain="mydomain" providerName="ADMembershipProvider" />
	</membershipMappings>
</Smartsite.ActiveDirectoryConfiguration>

The xsl template site file "../system/XSL Templates/AIMReferencesRealtimeResult.xsl", which is used to generate the AIM realtime results, has been changed to skip creating a javascript link for Local File references.

The Contenttype and Fieldname dropdown selection lists, which depends on each other and the Search Group dropdown, didn't display the correct selection.

The cms manager did use a move file statement, which will not use ACL security inheritance from the folder. As a result, the uploaded file couldn't be displayed ("Access denied").

The cms manager now uses a copy statement on the file(s), which will inherit the appropriate ACL security rights from the (target) folder. After the file has been copied, it is deleted from the temp folder.

The code has been modified that a clear error is now raised, stating that the browse start page of a specific channel is not valid.

The LinkInput webcontrol, which for example is used on the Url field of an Reference item, could be considered as a combination of the FileInput and ItemInput webcontrols. These two controls use the ctfp's ctrl:Path and ctrl:StartNode respectively to preselect the start folder (folder on disc/folder within the cms).

These starting positions could be configured for the LinkInput control as well, however you would needed to use two obscure ctfp's, cust:_fileSelectionRoot and cust:_itemSelectionRoot respectively. Now the LinkInput control also supports the ctrl:Path and ctrl:StartNode ctfp's.

Due to the Activation event being raised twice, SMI was registering twice as many item activations and the repository workflow was sending mails twice.

Previously, the internal Outscaling events were just removed from the osEventQueue, so you didn't have feedback if and when such events were executed.

Sites that use deeply nested translations could crash with a StackOverflowException if in the deeply nested translations an exception occurred that was only handled at the top level. This problem occurred mostly when Smartsite was running in a 64 bit process.

The viper methods smartlet.events.receivevalue() and scf.events.receivevalue() now support the 'default' parameter. If no default value is passed, an exception is thrown.

Trying to set CMS access on a selection containing only items or applying changes to an empty selection would result in a database error.

This Viper method can be used to push byte arrays into the binary data-formatted DataTable format.

After canceling 'Add Topic' it will still be possible to add a topic again.

It is not allowed to add a topic with an empty title.

Manual fix for update scenarios:

In item GUID-DBC85B989B0847F59F76B9C0F9672591 find this line in the Body:

<se:buffer name="buttons" condition="smartlet.get(mode)=='list' AND smartlet.testaccess(ForumPostActive)">

And replace that with:

<se:buffer name="buttons" condition="(smartlet.get(mode)==list || smartlet.get(mode)==cancel) AND smartlet.testaccess(ForumPostActive)">

In item GUID-DBC85B989B0847F59F76B9C0F9672591 find these lines in the Body:

<se:case value="save">
	<se:if expression="smartlet.testaccess(ForumPostActive)">
		{smartlet.set(renderTopic,translation.localscope.savetopic())}
		{translation.localscope.showtopic(smartlet.get(renderTopic))}
		{translation.localscope.forumposts()}
	</se:if>
</se:case>

And replace them with:

<se:case value="save">
	<se:if expression="smartlet.testaccess(ForumPostActive)">
		<se:if expression="!string.isempty(smartlet.get(title))">
			<se:then>
				{smartlet.set(renderTopic,translation.localscope.savetopic())}
				{translation.localscope.showtopic(smartlet.get(renderTopic))}
				{translation.localscope.forumposts()}
			</se:then>
			<se:else>
				<h2>{locale.translate("Add topic")}</h2>
				{locale.translate("Title can not be empty.")}
				{translation.localscope.topicform()}
			</se:else>
		</se:if>
	</se:if>
</se:case>

The Calendar macro had an error in the default result format string (used when no resultformat property was set)

When selecting 'upload' from a File dialog in the CMS, the folder shown as selected in the file dialog tree had to be clicked in order to select it as the folder to upload to.

When choosing the Validate Only option in SetSiteSecurity, the number of rules that are tested does not match the number of rules when setting and validating the rules.

The se:webservice macro didn't function properly when you tried to connect to a webservice over https.

This has been fixed, just specify the appropriate https address.

The DOCTYPE header was not set when selection doctype="xhtmlbasic10" in a rendertemplate.

Within the smartsite.security.config configuration file, you can now include a passworldwallet node, which can be used to store username/password combinations in a centralized, secured location (see example below):

    <passwordwallet>
    	<account id="import" username="importuser" password="12345" />
    	<account id="example" username="overheid" password="12345" />
    </passwordwallet>

The Config Editor and the Config Protect tools will automatically encrypt this node.

With the vipers security.passwordwallet.getusername(id) and security.passwordwallet.getpassword(id) you can retrieve an username/password combination whereever you need it within sxml.

Due to faulty security checks, Add Item could fail for users despite having access to the child contenttype of the selected item.

Favorites that are opened or mailed do not use the correct date when a fixed period like "yesterday" or "last month" is used.

SMI 2.0 setup failed to install site files if a previous version (SMI 1.5) was already installed.

PublicationUpdate.exe abruptly failed when a read-only file was to be altered or deleted. Now PublicationUpdate.exe will automatically unset read-only attribute of .config files while - if applicable - asking the user to manually unset read-only attribute of other site files.

The graphical setup tool (PublicationUpdate.exe) does not parse the database password correctly. As a result, exclamation mark (!) is not allowed in the password. A login failed error will be shown, aborting the rest of the setup.

Database view vwLogEntries is introduced in order to simplify usage of table LogEntries.

Starting from 1.3 build 3 only CTFP SearchGroups "STANDARD" will be overwritten if and only if there are no other values for CTFP SearchGroups.

Item with code REPOSITORY_MAILMESSAGE was of ContentType CAP, in some cases leading to exception "Smartsite.InteropServicesClient: SXML Syntax error: opening and closing tags do not match". This item now is of ContentType AWP which should solve this bug.

When using the excludefileextensions parameter (or no parameter at all to exclude file extensions, in which case the excludefileextensions parameter will use its default value), the syncfilelinks macro didn't detect any differences between the specified folder on disc and the cms folder item. Therefore, no import xml was generated.

Workaround: use FileExclusionExpressions parameter to specify one or more regular expressions to exclude certain file extensions, e.g.

<se:parameter name="fileexclusionexpressions">
   <se:collection>
      <se:member>^.*\.(db|zip|dll|exe|config)$</se:member>
   </se:collection>
</se:parameter>

The This.GetXml() and This.GetInnerXml() methods were added to XmlProcessor, to facilitate working with Xml Fragments

When a Search Group is defined in table tsSearchGroups without having any SearchGroups CTFP linked to it, the stored procedure handling Faceted Search (pr_tsFacetedSearch) will result to an exeption. Unfortunately this exception even occurs when invoking pr_RebuildViews since this procedure invokes pr_tsFacetedSearch.

For debugging purposes, the /verbose parameter has been added to SmiServer. This parameter can be used on the commandline to debug problems with SMI.

The <se:chart> macro did not use the current Sxml locale that can be set using the <se:locale> macro. Instead it was always using the system locale.

Due to this bug, a week was sometimes starting on sunday and sometimes on the day of the FirstDayOfWeek setting.

Now Smi displays both the channel's title and the channel's code in the report "Visitors per channel".

The Smi setup did not set the right content access level for the item with the code SMI_CLIENTLOGIC. It was only accessible to administrators while it should be publically accessible.

If the Smi client is not supported by SmiServer, a useful error message is displayed now.

The exclude list available in previous Smi releases has been extended with an include list, the ability to group several criteria into an OR or AND criterium and the ability to negate criteria.

You can now specify a per site include and exclude filter for custom events in the Smartsite.ManagementInformation.config file. See http://docs.ixperion.smartsite.nl/doc/customevents.html for an example of the filter.

You can now specify a password for each site hosted in SmiServer. The sites configured in Smartsite.ManagementInformation.config must have the same password to be able to send hits and generate reports.

You can now add restrictions to who can view which site's Smi reports based on the usergroup by specifying the usergroup for each site in the Smartsite.ManagementInformation.config file.

Fields for which no SearchGroup ctfp has been set were also shown in the field-select dropdown.

When adding a (new) physical field weight for a specific search group, the Faceted Search QueryBuilder did take this additional field into account immediately by expanding the main search query with an additional search query against this field.

However, after adding a new physical field weight, this field isn't available on the Search Group's view until running the stored procedure pr_tsFacetedSearch.

The QueryBuilder has been adjusted and now uses an additional JOIN with vwSchemaTableColumns to skip physical field weights which do not have a corresponding column within the Search Group's view. The list of available fields for each Search Group will also be cached now.

In PublicationUpdate.exe it is possible to skip files upgrade (site files, binaries, config changes, etc) in order to directly skip to add-on-modules update and/or database scripts. Note that this feature does not take into account add-on-module-specific site files, binaries, config changes, etc.

If neither SQL*Plus (for Oracle) nor SQLCMD (for SQL Server) are properly installed on the server running PublicationUpdate.exe, a warning will appear in its graphical interface stating that database scripts will not run. The user either should properly install SQL*Plus or SQLCMD or manually run the database scripts on the database server to continue installing or updating.

The smtpServer configuration setting for the email trace listener (if present) within the Smartsite.Logging.config is also updated when changing the SMTP Server Address setting within the Config Editor.

When using an Outscaling scenario with multiple cms server instances (separate databases), DataEditor events were assigned to cms server instances, even when there are not a subscriber of the current server. The events would never be sent, though, but it led to a flooded eventqueue.

The rename site option was too strict and only changed the site-name within the (web)service urls if the site-name part matched with the old site-name. Now, if the site-name part doesn't match it will also be replaced with the new site-name.

The rename site option now also allows you to specify the same site-name to adjust the (web)service urls with this site-name.

This could cause unnecessary memory consumption and instability.

When installing Faceted Search, these are the rules to determine the initial parent:

1. First try the BrowseStartPage of channel DEF (since this is the default browsable channel)

2. If it does not exist: try BrowseStartPage of all browsable channels if and only if there is only one BrowseStartPage

3. If no browsable channels found or more than one BrowseStartPage is encountered, use the Site Root

SQL Server's stored procedure pr_FriendlyNames items with very long titles while its parents and grand-parents have identical long titles resulted into a SQL Server truncation exception. This is fixed in pr_FriendlyNames version 1.9.

To determine the language in which Smi reports are now shown, Smi now first checks the locale of the user. If no locale has been set for the user it checks the locale of the channel. If no locale has been set for the channel, it uses en-US. Once a locale has been set, it is stored in personalization and used the next time you use Smi.

The FS box type for Smartlets rendered an H2 tag for each box. This may cause problems in the semantic structure of your documents, especially when complying to Web Guidelines. For this reason, the H2 element has been removed and replaced with a DIV element with a 'box-caption' CSS class.

In previous versions of Faceted Search, entries of some tables (like ContentTypes) could not be easily deleted due to missing cascading behavior of some foreign keys of tables introduced by Faceted Search. By running the 1.3 build 3 script of Faceted Search, these cascading behaviors will be added to the appropriate foreign keys.

Due to textfilter CTFP configuration, the Skin_Basic item in the Faceted Search Smartlet ClientData folder cannot be edited normally. When editing, you have to move the macros in the Logic field, add 'save' parameters and use the buffers in the CSS field, to prevent SXML data corruption.

The layout of the publication update tool (UpdatePublication_xxx.exe) has been optimized for 1024x768 screen resolutions. Furthermore, in this tool a link is provided to a page on the Smartsite Community Site for more information/explanations of this tool.

The new feature of pushing "six" log messages to the "cms" logging (as configured within Smartsite.Logging.config) did fail due to changes within Smartsite.Logging.config (default namespace and schema specification has been added).

The cms engine, when reading settings from Smartsite.Logging.config, now checks if there's a default namespace in place, and if so uses this namespace accordingly.

The Synchronize Datasource dialog did display built-in datasources, however, only when there was at least one custom (manually added) datasource. This has been fixed, when there are only built-in datasources the dialog doesn't report above message anymore and the built-in datasources are displayed.

Notice that you can use the action parameter "ShowBuiltinDatasources" (defaults to True) to switch off displaying built-in datasources.

In order to be able to edit/delete multiple records at once, multi-selection in user action is enabled on user action Outscaling Datasources.

Smi sites that are defined in Smartsite.ManagementInformation.config now have an extra attribute "enabled" that allows you to disable a site.

The Faceted Search "configuration tables" (tsSearchGroups, tsFieldFilters, tsContenttypeFieldWeights) have been added as built-in datasources, so you don't need to configure Outscaling datasources for them manually anymore.

The Transform macro did not support the setting AllowDtd anymore, because of the use of the native Xml type. The property now has been deprecated and you must use an XmlProcessor macro with the AllowDtd setting as input for Transform, if you wish to transform documents with a DTD.

Although it is possible to create an Outscaling Scheduled Event which synchronizes the complete list of ItemComments on a regular basis (e.g. nightly), or maybe even using timestamps to only synchronize new and changed records, it should be possible to synchronize new or changed ItemComments records real-time.

The mechanism for real-time synchronization is to add a specific so-called DataEditor event to the Outscaling Event Queue whenever a record which must be synchronized is added or changed. However, the ItemComments module didn't add such events.

The ItemComments module has been adjusted and will now add these Outscaling events. It uses the stored procedure pr_AddOutscalingEvent to execute this task. (Notice that 1.1 doesn't have this stored procedure; you need to add it and its dependencies manually.)

ItemComments will not be treated as built-in Datasource by Outscaling, so don't forget to add the appropriate Outscaling Datasource(s). Also, make sure that the smartsite.config contains the correct instance id within the PublicationInstanceId application setting, otherwise the events will be created with the wrong instance id. Finally, you need to configure SmartNumbering on the table swtItemComments.

For performance' sake a non-clustered database index is created on column Timestamp of table LogEntries.

The EditProgID of field Author generally used to be DropDownList. In order to avoid incorrect choice of author (e.g. if an author does not exist anymore) the EditProgID is changed to DropDownCombo.

De Empty site now contains extra settings in de forms node of the authentication section in the Web.Config.

<forms loginUrl="/Login" name="Smartsite" timeout="525600" slidingExpiration="true" />

When you select 'remember me' during login, the cookie expiry of the login cookie is set to to one year (this timeout value is in minutes).

The default cookie expiration in .Net 2.0 and later is 30 minutes.

The FS box (CreateSmartletBox() translation) now renders a DIV instead of a H2 element for its captions.

On systems with old hardware and/or low bandwidth, data loss could occur when opening the ContentType properties dialog and pressing 'Save' too soon.

When an item has been synchronized (update mode) to a remote server (or when it has been imported manually on any server), the ampersand encoding was sometimes incorrect. Due to this problem, XML and SXML examples were not displayed correctly.

The Importer has been changed and no textfilters will be applied when an xml file is imported.

When the Smartsite configuration files were encrypted by the ConfigEditor or the ConfigProtect tool, SetSiteSecurity did not read the correct configuration settings.

After mapping URL parameters to the current request, the request.location() viper returned a corrupted value, where it should always return the (read only) original.

When the SXML processor encoutered an xml declaration tag within a CDATA block, it would fail.

Locations passed to FeedReader would not be xml-decoded, leaving &amp; in the url.

When creating and manipulating Xml documents, an Xml document may contain multiple xmlns declarations that are superfluous in their context. The XmlProcessor now has a 'RemoveDuplicateNamespaces' property to remove them.

Commas were not escaped in querystring parameter values

Making it symmetrical with other ContentAccess functionality.

This behaviour can be overridden with the CompatibilitySetting "UseCurrentRoleToDetermineContentAccess".

To update your current site change system translation "GUID-BA82D08453C74A65A37E1DDCFE02BBDC":

replace

<se:rowformat expression="this.field(code)==''LOGIN'' AND !user.isanonymous()"><a title="Log off {user.fullname()}" href="/Login?undologon=1">Log off</a></se:rowformat>

with

<se:rowformat expression="this.field(code)=='LOGIN' AND !user.isanonymous()"><a title="Log off {user.fullname()}" href="{url.addparameters(LOGIN, true, 'action=undo','ReturnUrl='+ url.setabsolute(request.location()))}">Log off</a></se:rowformat>
<se:rowformat expression="this.field(code)=='LOGIN' AND user.isanonymous()"><a title="Log in" href="{url.addparameters(LOGIN, true, 'ReturnTo=ReturnTo', 'ReturnUrl='+ url.setabsolute(request.location()))}">Log in</a></se:rowformat>

Viper methods such as Url.AddParameter(), that returned modified versions of locators, also changed the input locators. This behavior can now be avoided by setting the Smartsite.config runtime\releaseSettings\immutableLocators value to "true". Search for 'releaseSettings' for more information.

Due to a policy change on the servers of W3.org, the .Net Framework (and thus also Smartsite) is no longer able to download the xhtml dtd's. The most common dtd's are now embedded in Smartsite to work around this limitation of the W3.org servers.

Search groups can be assigned a stoplist which can be managed in the Smartsite manager. However, this feature did not work properly until 1.3 build 3. Furthermore, a default stoplist EmptySix_Stoplist will be created, prefilled with the system stop words. Note that this feature applies to SQL Server 2008 only!

Due to a fix in 1.3, an issue was introduced in specific scenarios where SXML code is executed inside Sql Params.

When using the FS box style, the paging buttons at the bottom of the facet boxes were not shown in IE7/compat mode.

The changes made in ClientData\Skin_Basic:

.ix-faceted-search.basic  .is_moreless .more, .ix-faceted-search.basic  .less {
  /* text-indent: 9999px; */
     line-height:3000;
     overflow: hidden;
     height: 10px;
     display: inline-block;
     width: 50px;
     font-size: 0.8em;
     float: none;
}

This viper should be used within SXML when a record is added to a certain table and this record must be synchronized to other subscribed cms server instance(s).

The viper internally uses the in 1.2 introduced stored procedure pr_AddOutscalingEvent, which will add a record to the osEventQueue Outscaling table. Notice that the record will only be synchronized if the specified table is a built-in datasource or when a specific datasource has been configured for this table.

Usage example:

    {database.addoutscalingevent(swtEvents, $newkey)]

To ensure the searchterm_XXX facets always use the CMS database, apply the following changes to the sml_FacetedSearch_Facet() smartlet.

Old code:

<!--// read query xml -->
{buffer.set(xml, translation.localscope.readqueryxml(smartlet.get(queryxml)))}
{buffer.set(dbconnection, xml.querynodevalue($xml, '/smartsite.facetedsearch/configuration/masterquery/@connection',default='') )}
	
<se:if expression="convert.toint(smartlet.get(facet)) GTE 0" rem="set facet name">
  {smartlet.set(facet, xml.querynodevalue($xml,"/smartsite.facetedsearch/facets/facet[@enabled='true']["+convert.toint(smartlet.get(facet))+"]/@name", default=''))}
</se:if>

Replace with:

<!--// read query xml -->
{buffer.set(xml, translation.localscope.readqueryxml(smartlet.get(queryxml)))}

<se:if expression="convert.toint(smartlet.get(facet)) GTE 0" rem="set facet name">
  {smartlet.set(facet, xml.querynodevalue($xml,"/smartsite.facetedsearch/facets/facet[@enabled='true']["+convert.toint(smartlet.get(facet))+"]/@name", default=''))}
</se:if>

<se:if expression="!string.startswith(smartlet.get(facet),'searchterm_')" rem="do not used dbconnection for searchterm_xxx facets" >
  <se:then>
    {buffer.set(dbconnection, xml.querynodevalue($xml, '/smartsite.facetedsearch/configuration/masterquery/@connection',default='') )}
  </se:then>
  <se:else>
    {buffer.set(dbconnection, '')}
  </se:else>
</se:if>

A bugfix was done to fix an Uri escaping bug that was caused by a change in the Friendly Name mapper.

Due to a programming error, the viper always returned an error.

See Work Item 8224.

The calendar macro (Web Toolkit) needed the buffer 'id' when using the default resultformat. It will now use the value of the Id parameter as the html id in the outer table element.

Some Sxml DataTables were created internally without a DataTable Name. This name is required for some operations. All DataTables are now created with a name.

The Dutch and English Locale IDs were incorrent defined within the meta xml file TsSearchGroups.xml ("1033:=Dutch;1043:=English" instead of "1043:=Dutch;1033:=English").

The dataeditor meta xml file for this action have been adjusted and now uses a new view (vwNeutralLocalizationCultures) which contains the correct Locale ID's for all the (neutral) localizations that have been enabled within Configure Localization.

Fixed in 1.3 build 3.

However, when using the header

<meta http-equiv="X-UA-Compatible" content="IE=8" />

to force IE8 rendering, this bug would not have shown.

Manual fix (in upgrade scenarios):

In item GUID-DBC85B989B0847F59F76B9C0F9672591 find this code in the Body:

<se:smartletbox caption="{smartlet.namedarg(boxcaption, default=itemdata.name())}" buttons="{buffer.get(buttons,default='')}">

and replace that line with:

<se:smartletbox caption="{smartlet.namedarg(boxcaption, default=itemdata.name())}" buttons="{buffer.get(buttons,default='')}&amp;nbsp;">

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. Search for 'releaseSettings' for more information.

This happened when multiple search terms had been specified and one of the search terms matches with (part of) one of the field names used within the where statement, and/or when one of the search terms matches (part of) "searchterm".

FileLink items can now reference files on disk with querystring parameters which can be useful for images with image processor parameters.

The feature "Move character to the right" has been disabled. Ctrl+t can now be used to open a new tab in the browser or toggle the tree in the TestSuite.

Although you should use the within 1.2 introduced HtmlBody property, for backwards compatibility the sendmail macro will now use the Body parameter as alternative for HtmlBody when BodyIsHtml has been set to 1 and HtmlBody hasn't been set.

When declaring string input for Xml properties, Xml namespaces declared in the context will now be respected.

Xml properties on macros can now be decorated with an attribute to allow xml fragments to be used.

The ImageServer was not able to handle http requests where only a part of the response was requested by using the http content range. As a result, images for which the browsers requested only part of the image were crippled.

The releaseSettings section holds opt-in settings that allow new sites to use improved publication server behavior whilst guaranteeing full compatibility in existing sites. Search for 'releaseSettings' for more information.

For Repository to function fully, CTFP ItemValidation must be set on the Repository ContentType Nr field.

When the TestSuite could not start a webserver at the given host/port, it would show an error dialog but then crashed because of a bug.

Due to a culture-related bug, the getweek() viper did not always return 7 records

As a default, if SQL Server 2008 is encountered with compatibility level less than 100, the compatibility level will be increased to 100 by the Faceted Search setup.

It is possible - yet highly unrecommended - to override this feature. In this case some Faceted Search features will not be enabled.

In order to be able to delete multiple records at once, multi-selection in user action is enabled on user action View LogEntries.

Smi now stops writing log messages after 10 connection failure log messages.

If friendly name enforcement is enabled, HTTP requests without a friendly url to an item that has a friendly url, are redirected to the url with the friendly name by sending the browser an HTTP 301 Moved Permanently reply.

The ConfigEditor will now fail to load the site in which the error occurred but will continue loading other sites.

When a value in a secondary dependson relation in a repository item changed, the publication item would not be updated correctly.

The membership providers did use the vwUsers database view to map the user, which excludes disabled and expired/inactive accounts. Therefore, the account couldn't be found and Smartsite tried to create a new account.

The membership providers now use the AllUsers table directly and execute an additional check to see whether or not the account has been disabled or set expired/inactive. If that's the case, an appropriate exception is thrown.

The Html.PrettyPrint() method could fail when passing HTML with entities.

The Active Directory & LDAP Membership Providers now both contain additional configuration settings to limit the number of groups queried, to boost the performance even further.

These settings include: ObtainPrimaryGroup, ObtainParentGroupsForPrimaryGroup and MaxParentGroupRecursionDepth.

See the article Active Directory Role- and Membership Providers for more information.

Because the returned data was of a different type during preview, preview was often broken.

The fix for WI 8351 (image not correctly loaded when content ranges are used by the browser) caused a regression where the image server no longer worked with IIS6. The fix for WI 8351 has been made undone for IIS6.

Url parameters failed to reset its internal state, resulting in corrupted urls.

Friendly name enforcement has been modified to work only on http get requests and no longer on http post requests because the redirected http post requests lost their post data during the redirect.

The characters "!", "*", "'", "(" and ")" were not encoded in Url Parameters.

It is possible to multiselect entries of view log entries in order to delete them in one action.

After running Publication Setup 1.3 build 5 database scripts, this feature will be introduced in existing Smartsite databases.

Due to a change within 1.3 build 3 (and still the case in build 4), the retry mechanism of Outscaling didn't function properly anymore.

This has been fixed, however in the meantime (before the next build becomes avaialble and will be installed) it is strongly recommended to follow the steps described in this article.

Since iXperion 1.2 Outscaling uses the concept of built-in datasources. With the registry setting UseBuiltInDatasources (defaults to 1=True) on the Outscaling background component, you could (when needed) switch off the usage of built-in datasources.

However, this setting was read and set after initializing Outscaling, whereas the settting should have been read and set before the initialization takes place. Therefore, setting the registry option UseBuiltInDatasources to 0 (=False) didn't have any effect. This has been fixed.

This was due to the fact that the double quotation marks were not removed from the literal search string passed to the sql query macro.

When an Active Directory / LDAP groupname did contain a comma, the membership providers were unable to recurse the group membership for that group. This was caused by the fact that the Common Name was used to retrieve group membership for a particular group and the Common Name wasn't parsed correctly from the distinguishedName.

But using the Common Name isn't a very good idea in the first place (it doesn't need to be unique), so the membership providers now uses the distinguishedName (which is unique for every object) to retrieve a group and its members.

In rare occassions, the Active Directory Membership Provider wasn't able to retrieve all the groups the user is a member of. As it turned out, this only occurred when the Active Directory contains multiple accounts having the same Common Name. In that case, sometimes the group membership of the wrong account was retrieved.

The Active Directory Membership Provider now uses the user's SAMAccountName to resolve group membership, which does return all groups for the correct user.

Both membership providers now support the additional setting UpdatePrimaryGroup (defaults to true), which can be used to switch off updating the primary group of users after logging in (needed when using "mixed mode" security).

See Active Directory Role- and Membership Providers for more information.