Used to be a string.

New Vipers have been added for manipulating datatables. Some old viper methods have been deprecated, i.e. they have been replaced with new methods but the old methods still work and are backwards compatible.

The image processor preserves image metadata when applying transformations and using spice and the se:metadata macro it is now possible to store additional metadata into images

When saving items, an AIM request is done to collect references to other resources. During this process, the SendMail macro should not actually send mail messages however.

The error "The given path's format is not supported" could occur in the Virtual Path Provider, especially when starting a Site in the TestSuite, using localhost.

The queue component was unable to determine the time it should run next, so it only ran on startup.

Performance of the JSON string parser has been improved.

The UI regarding saving edit sessions in the TestSuite has been improved.

The webservice macro now has two extra parameters: username and password.

When these parameters has been provided, the webservice macro automatically establishes a secure connection to the specified Url, using basic authentication.

The webservice macro now exposes a timeout parameter.

Search for 'Configuring Multiple Active Directory domains' to set up multiple AD domains.

The Active Directory Provider would not remove a user from a group when AD membership from that group was removed.

Instead of saving images in the selected folder of the cms, a directory on disk was created. The addin now checks for the channel.link viper explicitly so it will use the selected cms folder.

Uninstalling performance counters can now be done with the perfcounters.exe application.

The ImageServer wizard now links to images directly in the publication.

The last logon and the password failure count were not updated.

Fixes a bug where trying to copy text to the clipboard causes a "Requested Clipboard operation did not succeed" exception. The exception occurred frequently when using the SXML editor in a virtual machine.

When you used the LiteralMethodNode parameter in a webservice macro, the call failed if you did not also provide the MethodName parameter. However, the MethodName parameter shouldn't be needed when you provide the LiteralMethodNode parameter, this parameter (should) contains all the necessary information.

When an exception is raised during the start of the iXperion WCF Services, the exception was not handled properly, causing a crash of the w3wp procress when iXperion is hosted in IIS. The bug has been fixed and all WCF services startup exceptions are handled.

The black control groups have been replaced by a new tab control.

A Viper expression returning null in a groupby attribute caused an Object reference not set error.

The VPP would fail with a Read Access failure.

Some advanced options did not have a Dutch translation yet.

Depending on the content being filtered, the text filter would lock up the server indefinitely.

The Importer always executed ampersand unescaping, regardless of the contenttype field configuration. This has been fixed, now ampersand unescaping is only executed on fields which do have a textfilter ctfp.

Sometimes it is necessary to use escaped CDATA sections within SXML. When exporting/importing an item containing such escaped CDATA sections, these were converted to unescaped CDATA sections. To resolve this issue, the Exporter and Importer now both use different escaping sequences for unescaped CDATA sections, making sure that originally escaped CDATA sections will be kept intact.

The incorrect error "RenderTemplate used in Raw channel may not have XSLT" was raised when you add a rendertemplate containing one or more mappings to the RAW channel. The error was raised from the RenderTemplate contenttypehandler, because it didn't handle an empty itemNumbers string well.

Itemdata was loaded from the wrong view leading to content being available on channels where it should not be available.

The Importer code has been enhanced with several options, culminating in the "bulk import" option, which has been added to the Import XML File(s) dialog. This option is intended to be used for large import xml files (containing e.g. >100 items).

When using the bulk import option, the following applies:

- Within the import wizard itself, schema validation and import file analysis is skipped (takes a lot of time for large files).

- ContentChange.Activation events generated during import are consumed by the Importer and at the end of the import process, the publication engine is signalled to clear its memory and disk caches.

- Detailled import summary information will not be sent to the progress dialog (which would be potentially hundreds/thousands lines of html).

Using the new IHTMLTxtRange interface implementation the SXML editor supports HTML operations such as createTextRange and provides text range manipulation using standard HTML methods.

The item that was shown in the output was shown instead of the selected item and sometimes the wrong browser was started.

When the login macro redirected to the destination page, querystring parameters could be mangled.

When calling request.transfer(), the old channel state would still be present in the request.

New Viper methods have been added to read the host header configuration.

The old ConnectionBuilder tools has been rewritten for the .Net Framework.

CmsProxy is a somewhat friendly wrapper around the cms webservice allowing a developer to manipulate content from within the Publication Server.

Validate Operational Status now warns the user that a site is not site when trying to validate the operational status of a site

The XmlFileTraceListener did not use a CDATA section to enclose the Message element from a LogEntry (any category) when writing a xml fragment to the log file. This resulted in non well-formed xml log files when the Message contains e.g. the characters '<' or '>'. This would happen if SQL category within the Information logtype has been enabled with maxlevel set to 10, in which case executed SQL queries will be written to the log. The template which is used to create LogEntry elements now uses a CDATA section to enclose the Message element.

The passed image data was not handled correctly, resulting in the exception "cannot convert to byte array" when previewing an image within the CMS manager.

Depending on the order in which licenses were selected, the activator would sometimes return the error "Invalid Selection". The activator now keeps track of which site is selected correctly.

You can now activate generic licenses by creating a subfolder with a descriptive name in %ProgramFiles%\Smartsite Software\Licenses\ and copying the license file to the newly created subfolder.

Together with the LocalId macro property, the Scope viper identifier can be used to point to macros that are currently in scope (the same source field).

When Smartsite.Srm tries to login into a specific feature and this call fails (with a specific exception), it will automatically try to connect to the fallback licensehost (if specified).

New SMI Vipers have been added that allows the developer to register events in SMI.

The Placeholder macro no longer requires an Id. The LocalId parameter has been implemented to get source-scoped rendering. A placeholder with LocalId set, will render when the SXML-parser moves to another SXML source. For instance, a translation can safely use a locally scoped placeholder without risking conflicts with other placeholder Ids.

Using LocalId, placeholders can now be used with the current field without having a globally unique Id.

Since Smartsite will need to know the Hasp Key ID of your local Hasp License manager when you want to request a license modification, the Smartsite.Activator will write this Hasp Key ID to the Smartsite.Licensing.config file when you first activate a product license.

Then, all you have to do when requesting a license update/modification is send the Smartsite.Licensing.config to Smartsite, and we have all the information necessary to create an update/modification.

The read-only memory data parsing and handling has been improved to be able to handle the lack of certain nodes.

The "Invalid call context for translation vipers" error could occur when no preview logic was provided.

When a request resturns status 301 or 302 (Moved), a new request to the specified redirect location can now be issued automatically.

Now, the method will do as it says, just trim at the beginning and at the end of the string.

The Viper method this.grouprownumber() now returns the correct number of rows when used inside the <se:groupformat /> element.

The CMS site will no longer start up if the ExternalCachePath setting is made empty.

The CheckSiteFeature returned false for a licensed feature if the trial version of the same feature has been expired.

Normally, the item being rendered determines the scope of a local translation. The LocalScope indentifier can be used to specify that the caller's scope should be used for getting to local translations, instead of the item being rendered.

Using LocalScope thus means that a translation can call other translations in its own scope. The Smartlet architecture uses this to ensure copy-deployment of a Smartlet-folder.

GlobalScope can be used to point to the global version of a translation in spite of the fact that a local version exists.

Previously, the Image Processor would always limit the output size for an image to a maximum of 3000 x 200 pixels. This restriction has been removed.

You can still set a constraint for the image width and/or height in the ImageProcessor.config.

When using the se:image macro, the target image was always transformed by the imageprocessor. Now this behavior is only enabled when the processallimages setting of the imageprocessor config is true or when at least one image command has been specified.

When copying a global translation and specifying an empty title prefix (which will result in a copy of the translation with the same name) the error "translation already exists" is raised. But the copy of the translation will be saved in a busy state, and there's nothing against having two (global) translations with the same name, as long as one of them is in a not-active state. So, the check for duplicate translations should be executed upon activation of this copy, which has been implemented by this fix.

This makes it possible to create/deploy licenses for virtual machines (e.g. VMware ESX server).

Previously the parsing of double and datetime string values used the current culture. String parsing now uses the invariant culture for double and datetime types in order to make parsing indepent of local culture settings.

You can now bypass existing cache in the cache macro using the BypassExistingCache property.

To make se:dir and se:xlinks location more symetrical, you can now force xlinks to provide a location field into its result. Use the displayfields property to do so.

Named and unnamed parameters could not be combined in translation calls when the translation had arguments specified in the name - translationname(arg1, arg2)

SignalSmartsite can now automatically detect the WCF settings required to connect to a running Smartsite instance. Manual configuration might still be needed for the more complex configurations.

If the AppDomain unloads because the site is closed, the thread aborts with a ThreadAbortedException.

In this case, the exception is expected and therefore no message should be written to the eventlog.

Now, the ThreadAbortException is catched separately and no message will be written to the eventlog.

When the Smartsite.Licensing.config file contains v2c information for product/license updates, the Smartsite.Activator console application will now remove them when activating a provisional license. The activation can only be executed on another machine and the updates will not be valid for this activated product/license, since they are bound to a specific (unique) hasp key id.

The error occurred because the image control was trying to render the parent.

The image data was displayed as string content, because the http contenttype was not set correctly.

This example, should not give a result.

<se:for from="15" to="10">{this.index()}</se:for>

When using Xlinks to filter inaccessible items from a list of items generated by a different macro and that list happened to be empty for whatever reason, Xlinks would return a list of children of the current page as if no inputdata was passed.

Xlinks has been fixed to return the empty datatable directly.

Select zero rows from a datatable tables resulted in a datatable having zero columns. The columns are now created in the datatable, even when there are no rows.

When copying a folder containing e.g. one or more global translations and without specifying a title prefix, the copy action failed on creating a duplicate global translation (two translations with the same name/code). The copy action was aborted without granting access permissions on already created folders. Therefor, the created items were not visible within the cms manager. Now, the access permissions on already created folders will always be granted, whether or not an exception occurs during the copy action.

TestSuite now runs as a 32 bit application on 64 bit platforms.

In the TestSuite, opening an item in an external browser did not always open the expected item in the expected browser.

When editing an item in the TestSuite, opening a group did not always show all the fields.

The RSS macro now uses vwActive_XXX instead of vwActive, thereby respecting the channel security.

The error "object reference not set to an instance of an object" is raised when previewing a new (not yet saved) image (an item with contenttype image that is) within the cms manager. However, this would only occur if the rendertemplate for the contenttype image contains the session.enable viper. This viper didn't take into account that the ItemInfo object could be null, which is the case when previewing a new item.

The se:code macro automatically adds a number of basic Smartsite iXperion assemblies to the referenced assemblies. However, no full path was specified, resulting in the "metadata file [...] could not be found" exceptions.

The post-processing of items within the Importer could be aborted unexpectedly when within the item data an external url with an ".html" extension was encountered.

AIM registration failed for a soft link to a local file.

Make sure that the parent field of all items on the first level are set to a common value that doesn't exist elsewhere in the data set (usually 0 will work). Set the RootNode parameter to this value and IncludeRoot to false.

The Importer now takes the contenttypefieldproperty Nullable into account, and reports a warning for each field which is missing within the import xml (or has an empty value) and for which the Nullable ctfp has been set to 0.

In the Logic field of a content item, you can now use <se:itemdata /> to render the body field.

It is no longer necessary to mention the Body field (<se:itemdata field="Body" />), it will automatically be selected.

The rules now are:

- If <se:itemdata /> is used in a render templates it will automatically select the Logic field if present and non-empty. Otherwise it will render the Body field.

- If <se:itemdata /> is used within the Logic-filed of a content item, it will render the appropriate Body field of the same content item.

Of course, the can still use the field parameter to render a specific contenttype field.

The syntax below did not work correctly.

<se:xhtmlpage doctype="XHtml10Strict" id="rt">

<html>

{page.rt.getdoctype()} -> XHtml10Strict

{page.rt.setdoctype(XHtml10Transitional)}

{page.rt.getdoctype()} -> XHtml10Transitional

</html>

</se:xhtmlpage>

Setting the default for trim to both removes two redundant linefeeds from the output.

<se:xhtmlpage>

<html>

..

</html>

</se:xhtmlpage>

You can now set specific XHML page properties using extension Vipers such as SetDocTypeHeader(), SetOmitXmlDeclaration() and SetXmlVersion().

SetOmitXmlDeclaration() and GetOmitXmlDeclaration() Viper methods added.

A field within an useraction which uses a checkbox as edit control was copied twice when copying the useraction to the clipboard. When pasting an useraction from the clipboard, fields which uses a checkbox were always set to 1, regardless of the value within the pasted xml. Both issues have been resolved.

When using the default security configuration, this makes it possible use the extension vipers form with page logic. For example, to force rendering of a page as XHTML Transitional in a render template that uses Strict as its default doctype, put this viper in the page logic: {page.setdoctype(XHtml10Transitional)}

Vipers were not resolved in attributes of the colformat element. As a result, you can now use following statement: <se:colformat expression="this.groupnr() &gt;= 3"> ... </se:colformat>

The exception "This row already belongs to another table" could occur using this method.

After some time, the DataEditor could stop working, showing an error 'Security Information Invalid [...]'.

The viper datatable.simpleformat was sending values in a culture specific way to the output instead of using the invariant culture.

This new Viper method removes the given range of records from a datatable.

Items that have a parent item with a short url used to have a full friendly url. You can now specify whether the parent's short url is to be the "virtual root", using the UseVirtualRoot setting in the FriendlyNames configuration settings of the Smartsite.config.

When a switch macro did not have any expression and used the case expressions instead, the fallthrough case (se:case without expression) would never be returned.

Existing syntax for creating a json with a single property 'm':

<se:json localid="myjson">{m:2}</se:json>

Alternative syntax:

<se:json localid="myjson" source="{m:2}" />

Creasting an empty Json:

<se:json localid="myjson"></se:json>

Create an empty json using the source parameter:

<se:json localid="myjson" source="" />

The viper methods string.format and string.format size were culture dependant in previous versions of Smartsite. Now they are culture independant like all other viper methods (except for the viper methods in the locale class). The viper method locale.formatstring is a culture dependant equivalent for the old string.format method.

To distinguish between adding or setting a json object and an sxml type, the .add() and .set() methods now only allow a string representation of a json object. The overloads accepting int, float and boolean have been deprecated.

To set or add any SXML type in a json property use the AddValue or SetValue methods.

The underlying name of the .NET method was shown to SXML developers when an overload of a method with the given parameters was not found. The specified SXML name for the method is now shown, including the parameter types for which no overload is found.

Parameters given to the locale.culture.getstring and locale.culture.translate viper methods were not localized to the culture given to the method.

The selection now only changes when selecting the node label.

For use on the client, ampersands in values from a json object need to be escaped. The new GetEncoded and GetEncodedValue vipers handle the encoding for a more concise syntax. When serializing a json that will be included in the XHTML/Ajax response data, use the GetEncoded and GetEncodedValue vipers. otherwise, use the Get and GetValue vipers.

Smartsite would crash on startup when the database has a view in two different schemas.

Although the ImageProcessor and the Pdf Generator http modules are initialized during site start-up, additional instances of these modules may be instantiated and initialized during the life-cycle of your site.

When that happens, the site could become unresponsive for several seconds due to the fact of a time-consuming license check.

This has been fixed, the two modules mentioned now use a different license check mechanism, which only takes a few milliseconds to perform.

When non-placeholder viper statements were encountered in the placeholder execution stage, they could lead to a parser exception when syntactically incorrect, despite the fact that they would be marked as non-executable code.

Embeds could potentially corrupt render state for Sxml following the embed, thereby resulting in unexpected output.

Edit item tab gets closed when saving the item fails, resulting in possible loss of the data typed in the item.

Deleting an item with children resulted in an error message. The items were deleted anyway.

The this.step() viper has been added to the se:for macro for returning the step size.

The TestSuite used to validate all the fields except the title field. Now it only validates fields with a SchemaSetId or SecurityZone ctfp.

Smartsite crashed when Smartsite.Logging.config was locked or invalid. The crash has been fixed and an entry is written to the eventlog.

Some macros, such as the Region macro, have a default property that has delayed execution (RawData attribute). In this case, the handling of parameters blocks in derived macros at runtime could go wrong.

When redirecting, the TestSuite would not always update the Address field with the new Url.

When the parser encounters Viper methods in existing viper classes, but with incorrect syntax, an SxmlSyntaxErrorException should be raised, but this did not happen with nested methods (class.subclass.methodname()).

Internet Explorer doesn't post the value attribute of submit buttons. To fix this, Smartsite iXperion will check posted values for a specifcally formed comment containing the desired value. The comment is to be inserted after the caption of the button, using the Html.Form.MSIEButtonValue viper.

Publication description Because Smartsite iXperion can currently only be run as a 32 bit process on 64 bit OS'es, the ConfigEditor now also runs as a 32 bit process.

Whenever an error occurs within the StateSyncService, which is used to synchronize state events between cms and publication engine, this error is not propagated back to the cms engine (Outscaling in this case). This was due to the fact that the StateSyncService did not implement a FaultContract mechanism.

When duplicating a contenttype within the cms manager, Outscaling sends a "contenttype.copy" event to the StateSyncService of the publication engine. However, this type of event was not recognized and an exception was thrown. Therefore, when first duplicating a contenttype and then adding a new item of this contenttype, you were not able to (pre-)view that item. This has been fixed, the event subtypes "copy" and "propertieschanged" has been added.

When a non-existing Viper method was encountered that pointed to a valid Viper class, a syntax error should be raised. Instead, the viper method would be ignored.

When logging is configured to use an XmlFileTraceListener, messages and contextdata is written as CDATA elements to the log file. Usually, there will be whitespace characters (carriage-return and line-feed) enclosing the message and/or contextdata within the CDATA, and the LogMonitor should remove this whitespace characters. This has been implemented.

The SqlQuery macro has been extended to support the GetIdentity viper that allows you to get the identity of the last inserted record.

The TestSuite now has a debug setting to track unresolved vipers, independent of the channel property UnresolvedViperHandling.

The Request.IsPostback() method was added to quickly see whether a post is done from the same page.

This viper was introduced to be able to check content access more in line with the way the shared macro parameter "access" works. It tests if the current user has the required access level on a given item.

SignalSmartsite used to perform all its renders as the Guest user. SignalSmartsite can now use any user account for rendering items.

TestSuite did not make the value of the Code field uppercase. Item codes are now always in uppercase.

When saving an item update in which creating a new future version fails (for whatever reason), there will be no future version anymore, which causes the workflow engine to return an "object variable or with block variable not set" error within the next save attempt of the same item.

The function to create a new version has been updated in such a way that when creating a new future version fails, the previous version is restored as future version. Also, within the workflow engine, an additional check is implemented to prevent the "object variable or with block variable not set" error from happening.

This was caused by the fact that the references scan used the wrong linktype for resource files.

A culture dependant type conversion was performed in the viper datatable.setvalue and in lookup list declarations. This type conversion has been made culture independant.

If the TestSuite was used locally with an address already in use on the local machine, it would not produce an error message but instead would end up in a state with no site started. TestSuite will now show an error message and exit.

Site is now properly disposed when the TestSuite restarts resulting in Hasp sessions being properly closed.

This option helps developing Ajax-enabled GUIs.

Configured schemas no longer need to match the filename in casing. The check is no longer case sensitive.

Due to an issue in the TestSuite, it was possible to use lowercase characters in the Code field of content items.

This would cause problems with AIM when adding items within the newly converted folder.

When an item is saved, the item's references are scanned synchronously. The result is loaded into an XmlDom object.

However, when the reference collection returned is actual an error page (which usually will include a reference to the xhtml schema on w3.org), loading of this result into an XmlDom object takes a long time.

The reference collection returned will now be checked, prior to loading it into an XmlDom object.

The SearchEngineSitemap macro returned a validation error if the parameter "recurse" was not defined on the "excludefiles" element.

Support added for SqlServer datattype "Timestamp".

HttpHeaders for binaries from the database were not always sent when using disk cache.

Smartsite was looking in the wrong location on disk for the xml files.

The ampersands between querystring parameters were accidentally escaped internally.

This viper has not (yet) been released and should therfore not be included in the documentation or intellisense.

On some servers/configurations any call to Outscaling's external webservice fails. When using Fiddler to see the actual response, it turns out there's a problem creating SixTools.General:

"Unable to cast COM object of type 'SixTools.GeneralClass' to interface type 'SixTools._General'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{8F2E594C-CA12-4396-A2B1-69B751E742FF}' failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY))."

On some systems, this behaviour can be reproduced within a test aspx page which tries to create SixTools.General and then call the CreateNewGUID() method.

Switching to Asp Compat mode internally within the http handler solves the problem.

The Hasp session for the cms manager wasn't terminated when an AppDomain recycle occurs. Although the session automatically terminates after a timeout of 12 hours or when executing iisreset, the site shutdown code has been adjusted to explicitly close the hasp session.

When editing a channel configuration item within the cms manager and the publication engine receives the ContentChange.Activation event for this change, an AppDomain recycle is initiated. However, sometimes the hasp session for feature 3 (Site instance) isn't terminated when the AppDomain recycles.

This may lead to the fact that the Site is unable to (re-)start, because the limit on the number of allowed logins to feature 3 has been exceeded.

To resolve this issue, now the hasp session is terminated explicitly before initiating the AppDomain recycle.

Note that the CmsUpdate macro is not officially supported and may change or be dropped in a future release.

The CMS Setup installs a new version of the Hasp License Manager: version 12.47.

This version solves the stability issues reported with earlier versions. Therefore, make sure the version of the License Manager is 12.47 or higher.

To inspect the Hasp version number, browse to the License Manager (http://localhost:1947) and select About.

The loginmodule, due to a bug, tries to retrieve the password from the current membership provider, which in this case equals the Active Directory Membership provider.

This provider does not support the retrieval of passwords and throws an NotSupported exception.

A fix already introduced in iXperion version 1.1 has been backported to 1.02 (build 5), so the loginmodule can also be used in combination with Active Directory.