Previewing a new item within the cms manager resulted in the exception "the given key was not present in dictionary", due to the fact that the contenttype was not resolved correctly. This has been fixed.

When you use the Export Files Wizard within the cms manager, with the options "include linked data" and "create zip file" selected, the temp directory shared_files is not always deleted after creating the zip file.

This happens when the shared_files directory contains files which are marked as read-only.

To resolve this issue, the Exporter now removes the read-only flag of the copied files.

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.

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.

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 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).

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.

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.

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).

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 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.

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

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.

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.

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 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.