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

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.

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.

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.

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

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.

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.

Image transformations that could previously only be performed on images downloaded by a browser, can now also be performed in SXML. This allows for scenario's where a user uploads an image (e.g. an avatar), the image is resized in SXML and the binary result is stored in the database.

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.

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

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 unnecesssary cache could lead to unnecessary memory consumption.

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

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.

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.

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.

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.

On an Sxml level, there are no functional differences unless are directly requesting the full type name of the returned value. If you are using the result in other viper methods, there are no differences.

This could cause unnecessary memory consumption and instability.

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.

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

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.

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.

The debug feature "RaiseErrorOnSxmlError" has been added that allows you to raise an error if a macro or viper statement raises an error, regardless of the error parameter in the macro or viper statement.

The file paths that were url decoded originated from many different places like e.g. the FileSystem.GetAbsolutePath viper, Request.SaveFile viper and many other places.

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

See Work Item 8224.

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.

This output of the viper debug.write is now culture invariant. The compatibility setting "compatDebugWriteCultureInvariant" has been introduced to revert to the old behaviour.

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.

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.

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.

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.

With forms authentication, a user who had previously logged on with the 'Remember me' checkbox set, could no longer navigate to any page (not even unrestricted) in the site after his/her account was removed or deactivated.

The security option HashPasswords, to store MD5-hashed passwords in the database, is now supported in the front-end.

See the article Protecting user accounts using hashed passwords for more information.

When this option has been enabled, the primary keys on the selected target server instance and the local server instance (or vice-versa when pulling is used for the selected datasource) are compared.

Records with a primary key that do exist on the target server instance and not on the local server instance will be removed on the target server instance (and vice-versa for a datasource configured to use pulling).

This option has been added to the (manual) Synchronize Datasource cms manager action, as well as the Configure Scheduled Events cms manager action. Notice you can use this option only one-way. When you have configured two datasources for a particular table, one for pushing data and one for pulling data, you should only enable the compare primary keys option on one of them.

The url textbox in the TestSuite was sometimes shown in white even though it should have been light yellow because scripting was disabled.

The SyncFileLinks macro uses the FileLink (FLK) contenttype to check whether or not a cms content item already exists for a specific file on disc.

This is too strict, any contenttype within the REF contenttype group should be considered.

This way, you can use an alternative contenttype (as long as it's part of the REF contenttype group) for items which are created using the SyncFileLinks macro and a subsequent webservice call to the asynchronous importer. All you have to do is apply xslt on the generated import xml file and switch the contenttype code.

Within the cms manager, it is allowed to set multiple items to inactive/archived (using e.g. the recursive option within Set Item State) when there are AIM hardlinks between these set of items.

However, when this set of items is synchronized to other Outscaling cms subscriber(s), the items which have an AIM hardlink relation to other items would fail. This has been fixed.

(This scenario also applies when setting items to status deleted.)

The column CompositeKey has been added to the table swtUserItemFeedback. This way, Outscaling will be able to synchronize records for this table between multiple (cms) server instances. Notice you have to create an Outscaling datasource for this table when it is required to synchronize records from this table. (Related to work item 8384.)

The security option HashPasswords, to store MD5-hashed passwords in the database, is now supported in the front-end (work item 8416).

To easily enable this feature, switch to Advanced Mode and select "Hashed" for the Password Format within the Config Editor. The passwordFormat attribute on the Sql Membership provider will be set to Hashed and the cms manager registry option HashPasswords will be switched on as well. Furthermore, the Config Editor will, when necessary, offer the option to update the existing passwords within the database to MD5-hashed passwords.

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.

AIM scanning has been optimized

AIM scanning can now be tweaked directly by setting the CMS/AIM/ScanIntervalMS setting to a number of milliseconds to pause in between individual AIM requests in the AIM background thread. See http://docs.ixperion.smartsite.nl/doc/iXperion/Installation_and_Configuration/iXperion-CMS-Server/Registry_parameters.html

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

Smartsite iXperion now performs better when CMS updates are propagated and lead to state changes in the publication server.

Previously, multiple instance of a single CmsItem could in the cache for different channels. Caching CmsItems only once for all channels allows the CmsItem cache to contain instances of more different item numbers at the same time.

The Skip parameter can be used to suppress either dynamic, static AIM scanning, or both (default). Search for 'AIM rendertemplate' in the documentaion for more information

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.

Due to the login failure on the Interop service, content validation and previewing items failed as well. It was therefore impossible to add/change items using the Active state.

This has been fixed, single sign-on and Interop service login now also functions properly when using the LDAP Membership Provider.

You can delete file attachments by setting the attribute "deleteaftersend" in the member collection of the parameter "attachments" of the sendmail macro to "onsucces". An example is included in the macro documentation: http://docs.ixperion.smartsite.nl/doc/SXML/SXML_Reference/Macros/SendMail_Macro.html.

The Recent Edits window now shows all items edited by the current user and allows users with admin rights to show edits by any user (via Options dialog\CMS\recent)

AIM would create more than one reference to urls with bookmarks found in HTML content.

• psaContentAccessPub enables the publication access tab
• psaContentAccessCMS enables the manager access tab
• psaContentAccessCustom enables the custom access tab
• psaAdminRights enables all tabs.

Opening the dialog without any of these privileges raises an error.

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.

www-form-urlencoded is the only encoding supported by EmbedUri for CustomPostData.

The Config Editor did execute Friendly Name validations not strict enough.

For example, if your site contained an cms item (of contenttype CMS Folder) with the Friendly Name "Images" (which is part of the empty-six site) and your www folder contained an "images" folder as well, the Config Editor did report a warning: "Friendly name 'Images' (item x) equals a subdirectory of the www."

This validation is more strict now, it will only check Friendly Names which have the Short Url bit set.

Outscaling, when synchronizing a file reference, did use the osFilesystemSyncstate table to check the modification date of previously sent files. If the recorded date of the file is up-to-date compared to the current date of the file, no further checking was performed and the file was skipped.

However, in the meantime the file could have been deleted on the remote server. The check (file) references mechanism has been adjusted and will now always check if the file exists on the remote server.

List access means that a user can see the items below a folder. The old description claimed that the user would be able to edit the items below the folder.

Translations can now have typed parameters and return values, and can have outgoing parameters, that can be set by the translation as extra return values. See the section about Translations in the conceptual documentation.

The EncodeUrlParameterSpaceAsDash value can be used to represent spaces in URL Parameters as dashes. By default, spaces will be represented by '$2D'. This beautifies URL parameters further.

In order for Personalization to show the correct avatar, the ShowForm() translation in the sml_MyProfile Smartlet is updated.

To update existing sites, please look for the ShowForm() translation in the 'My Profile Smartlet' folder, and update the part where the avatar image is shown:

      <label title="You can add a personal image to your profile.">Profile picture</label>
          
      {buffer.set(hasAv, personalization.exists('', 'Avatar'))}
      {buffer.set(img, url.addparameter(smartlet.getresource('/configuration/Avatar'), u, personalization.username()))}
      {sys.iif($hasAv, buffer.set(img, url.commands.add($img, 'img', mxh, 100)))}
      <img alt="Picture for profile" width="100" 
       class="{string.concat('Avatar', sys.iif($hasAv, ' Enlargeable', ''))}" src="{buffer.get(img)}"  />

To fix this bug in existing implementations:

• Edit each instance of the ixs_FromatFacetResult() translation
• Find the buffer "val"
• Make sure that it is xml-encoded once, using {string.xmlencode()} with the options "LessThan,GreaterThan,Ampersand,DoubleAmpersand"

Smartlets can now be executed as parts of viper expressions, like in an if macro, or using string.eval(), sys.eval(), etc...

When a Smartlet property has 'write' callbackaccess, an exception would be raised whenever reading from it, even after writing to it first. This rule has been loosened now: after writing, you can read from the property. This avoids having to work with temporary buffers.

You can use the 'evaluationscope' parameter to pass a scope to translations for sys.eval() execution.

New installations are automatically translated. For existing installations, the following changes need to be made:

• Import the latest Localization strings for Faceted Search, or add strings manually with the following resource keys:
  • IXS_PERIOD_DAY
  • IXS_PERIOD_WEEK
  • IXS_PERIOD_MONTH
  • IXS_PERIOD_QUARTER
  • IXS_PERIOD_YEAR
  • IXS_PERIOD_5YEARS
• In the translation ReadQueryXml() append the string

  ,{locale.getculture()}

  to the keydependencies property of both se:cache macro calls
• In each Query Definition Xml item that contains the Period facet change the query to

  SELECT {this.facetselectfields()} FROM (
  	SELECT COUNT(*) AS Count, p.Days AS Days, p.Caption AS Caption FROM (
  		{this.searchquery()}
  	) nvt
  	JOIN (
  		SELECT 1 AS Days, '{locale.getstring(IXS_PERIOD_DAY)}' AS Caption UNION ALL
  		SELECT 7, '{locale.getstring(IXS_PERIOD_WEEK)}' UNION ALL
  		SELECT 31, '{locale.getstring(IXS_PERIOD_MONTH)}' UNION ALL
  		SELECT 92, '{locale.getstring(IXS_PERIOD_QUARTER)}' UNION ALL
  		SELECT 365, '{locale.getstring(IXS_PERIOD_YEAR)}' UNION ALL
  		SELECT 1826, '{locale.getstring(IXS_PERIOD_5YEARS)}'
  	) p ON p.Days >= DATEDIFF(d,ISNULL(nvt.ActivationDate,'1900/01/01'),GETDATE())
  	GROUP BY p.Caption, p.Days
  ) vt
  

The Scf Include Aggregator is now capable of adding the last modified date of the global include list it merges, to avoid users having to remove their client cache (or press CTRL-F5) when anything in CSS or Javascript items changes.

The timestamp ensures that, whenever the user navigates to a new page (or presses F5), the latest version - if changed- is retrieved from the server and used immediately used during the rendering.

This eliminates annoying client errors that could occur when the version of a css or script file on de client cache was outdated.

To implement this in an existing site, copy the Scf item GetGlobalIncludeItems(type) from the Empty site, together with the ELBA elements CSS() en Javascript().

The Include Aggregator now combines disk resources in the /scf/jquery/behavior/ subfolders with jQuery plugins in /scf/jquery/plugins/aggregated/. Files in those folders under the web root will be merged and minified automatically into one CSS and one Javascript include.

The Include Aggregator will be inserted or modified after running Publication Setup.

When multiple host-headers has been configured for the manager (internal and external addresses) the address to be used for single-sign on, css links and "open in new window" is now determined dynamically, based on the address/url used for the accessing the manager itself.

Translations can now be given a custom translation scope using the named argument 'evaluationscope' and the TranslationContext macro. Search for 'Contextual Translation Scoping' for documentation.

The use of parameter encoding in URL paths, as opposed to using querystring variables, is now supported for folders. Search for 'MVC' in the documentation.

This option was a left-over from Smartsite 5 and was never implemented within iXperion. Therefore, the export wizard does not display this option anymore.

The webtoolkit assembly, used within Poll and Rating, has been adjusted and now automatically adds the appropriate Outscaling event(s) whenever a record is added/updated.

Notice that synchronizing Poll and Rating related records is opt-in, so you need to create the appropriate Outscaling Datasource(s) if you want to synchronize these records.

See the article Outscaling Web Toolkit related data for more informaton.

To fix this problem in existing installations:

• Open each implementation of the ixs_FormatSearchResult translation and
  • Surround values that may contain xml entities with the following code:

    {string.xmlencode(string.xmldecode(string.xmldecode( <value> , 'LessThan,GreaterThan,Ampersand'),
     'LessThan,GreaterThan,Ampersand'), 'LessThan,GreaterThan,Ampersand,DoubleAmpersand')}

  • Update any existing {string.xmlencode(string.xmldecode())} viper combination to the syntax above.

Simply add the parameter status=1 to the collection of fields.

The status parameter does not work when updating an existing item.

Cache management in Smartsite iXperion is heavily optimized

The Form-based login page in the empty site now uses MVC-style urls, without querystrings. This is done by setting the 'Use Url Parameters' flag in the FriendlyNameType settings of the LOGIN item. For more information, also for configuring it in existing sites, please visit http://docs.ixperion.smartsite.nl/doc/iXperion/Installation_and_Configuration/Security/Authentication_in_Smartsite_iXperion/Using-MVC-style-urls-in-the-Form-based-login-process.html

Some builtin users like Network Service and Performance Monitor Users can have different names in non English versions of Windows which caused SetSiteSecurity to fail.

The Channel.State.Get() now supports setting a default parameter to return if the specified key does not exist.

The Outscaling background component determines the built-in datasource upon startup. When you want to change a built-in datasource to manual, you need to add an Outscaling datasource for this table/view and set its synchronization mode to manual.

Outscaling didn't pick up this change immediately, you needed to restart the background component so it would refresh its built-in datasources list.

To signal the Outscaling Background Component to refresh its internal state after adding/changing an Outscaling datasource, the dataeditor meta xml file osDatasources.xml has been changed.

You could also apply these changes yourselves to an existing site.

Just add the following code to the onaftersave and onafterdelete logic script sections:

Site.dataCache.invalidateGroup "Outscaling"

Site.ApplicationPlatform.events.addEvent "DataEditor", "Outscaling", "Refresh"

When using image macro and several other CTFPs, AIM Rendering will not function properly unless CTFP ctrl:ItemURLFormat is set to %nr%. This update does exactly that.

When logging on fails, Smartsite now produces a single error mesage: Invalid credentials. Previously, the user could see that the username was found but the password was incorrect, due to different error messages.

To update the login page in existing sites, open it and look for the string 'login.alert(this.error.message())'. Replace it with the string 'login.alert("Invalid credentials")'

The result of this fix is that generated links to the browse start page on the default channel are now / instead of /Pub/Home if the browse start page has a short url. This makes the link more SEO friendly.

Cms updates of translations and Smartlets now have significantly less impact on the Publication Server, due to an optimization of state synchronization procedures.

This would result in extra occurences of "amp;" in the target item.

The client-include-related Viper methods are now grouped into a new namespace: Scf.Includes. Also, a new method, Scf.Includes.AddFolder(), is added, which allows for automatic inclusion of all Javascript and CSS includes in a given folder.

When running Smartlets with a specified evaluationscope (for instance using a preset), Smartsite will try to include all (non-global) CSS and Javascript includes found in a folder named 'ClientData', directly under the given evaluationscope.

The maximum amount of characters for users' passwords is increased to 32 characters in order to be able to store MD5 hashes.

After running Publication Setup, this field will automatically be increased only if applicable; the field length will never be decreased.

Translation state synchronization on CMS updates is now much more efficient.

The SCF Include Aggregator now optionally takes the last modified date from a querystring value 't', in order to be able to set the file cache lastmodified date. See work item 8267 for more information.

Smartlet properties now resolve their default values dynamically. Since this is a functional change, a new compatibility setting, DynamicallyResolveSmartletPropertyDefaults, was added to enforce backwards compatibility. Set the "compatStaticallyResolveSmartletPropertyDefaults" setting to "true" in the appSettings section of the smartsite.config if you experience the new behavior as unwanted. More information in http://docs.ixperion.smartsite.nl/Compatibility-Notes-for-14.html

The url mapping has been improved and the capacity of the iteminfo cache has been increased fivefold to reduce the number of sqlqueries on the database. The performance of the Sitemap macro itself has also been improved.

Errors could occur when passing inputdata to a collection, because values were internally stored as strings, for instance when passing dates.

The CMS Setup utility allows installation of new CMS Servers in a custom location. Notice: this only works with a completely new installation.

ContentType SmartletPreset (SMP) will be added to an exisiting Smartsite database after running Publication Setup to 1.4 database update scripts.

Publication Setup will update AIM RenderTemplate (item code 'RT_AIM'). If the content of this item does not match the original content, a warning will appear advicing to check this item.

The dataeditor meta xml file AllUsers.xml has been adjusted and this file will be updated when running the Update Publication for existing sites.

The checkbox mentioned could be used to easily switch an user to become a visitor and vice-versa, however it did cause unclear behaviour and could cause problems within Outscaling scenarios.

If you want to switch an user to become a visitor, you should now just disable the user and create a (new) visitor. Notice that the loginname must be unique, so you should either use a different loginname for the visitor or change the loginname of the disabled user account.

This was due to a bug within the Usergroups_Outscaling meta xml file, which was missing a field definition for the AllUsers field.

This release includes version 2.2 of pr_tsFacetedSearch, making the preparation of Facted Search more robust.

Option PREPLAZY can repair a broken FullText index and is able to detect language changes, rebuilding the FullText index.

Explicit checks are performed prior to creating both the FullText index and clustered index on the indexed view.

The TestSuite can now synchronize the tree automatically whenever activating an editor tab.

When searching for content using the 'Jump to' action, the 'Find next' button sometimes did not work.

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

During AIM scanning on reciprocal content relations, content kept being marked as 'to be scanned', causing unnecessary activity in the AIM background process.

CTFP SchemaSetId must be removed on fields containing CTFP TextFilter with value 'includes'. Typically, ContentTypes like CSS and JavaScript have CTFP TextFilter set on 'includes'.

Publication Setup to 1.4 will remove the particular CTFP.

A SchemaSetId implies well-formed XML, however unencoded JavaScript is not well-formed and can contain characters like && and >. If SchemaSetId is set anyway, validation errors will occur in the manager.

Under circumstances, the cache folder in the site root was accidently deleted by Smartsite which caused all access rights to be deleted as well which caused malfunctioning of the disk cache.

A log off button has been added to the CMS Manager toolbar. Using this button, you can sign out immediately. This is especially useful in IE8, since Microsoft decided that all browsers should share the credential cache (unless the -nomerge command line argument is set).

AIM raw data scanning sometimes executed vipers that could not be executed without a rendering context, causing the AIM scan for that item being aborted.

The SxmlEditor was not used in the TestSuite when no SchemaSetId was set.

The TestSuite search/quick jump/F12 tree selection feature has been enhanced.

Embed and EmbedUri now have a new viper method to get the body of an X(HT)ML document: DocumentBodyNode()

The XmlProcessor now has a viper method, evaluate() to evaluate XPath expressions directly. Also, a static method, xml.evaluate(), is added.

Like EmbedUri (for external, HTTP-based requests), Embed (internal rendering in same site) now supports CustomRequestBody, so you can now internally render pages with custom post data, like application/json.

New settings are avaliable for showing tree lines and plus/minus.

You can now retrieve the number of (unnamed) arguments to a translation, using Translation.ArgCount()

The CMS AIM scan component was too greedy. It did not take the 'source' attribute of references found in the XML result of the AIM channel into account, when adding outgoing relations to an item.

When checking/unchecking the 'Add to Global Include' checkbox, the cache of the SCF global include was not invalidated.

When adding AIM references at runtime, components did not pass the correct AIM source item to the AIM proces. The source should be the rendering item unless the AIM source option 'Autonomous' is used (valid in translations). In the latter situation, the translation itself is the source item.

The resource handler included within iXperion (Smartsite.AspNet.Bridge.ResourceHandler) didn't ignore query parameters properly.

As a result, a request for e.g. res/tree/wp.gif?hid=img;crh=260;crw=260;w=155;h=90 gave a null-reference exception.

The AIM system panel addin now allows loading items with AIM state 'disabled' and 'error' into the treeview.

Smartlet errors occurring during property initialization while in Ajax callbacks would not be passed to the client correctly.

When no externally managed usergroups are configured, logging in with a valid LDAP account failed with a low level error.

Because of problems serializing (and de-serializing) the types Binary, DataTable, and Array (including all the ListOf~ types), these types can no longer be given ClientAccess. CallbackAccess is restricted to None and Write.

If the property is set from a preset, Write will be upgraded to ReadWrite.

The Faceted Search option 'noresultorder' has been added to the Faceted Search smartlet.

To add this option to a existing installation, follow these instructions:

Add the condition attribute to the following statement in the main smartlet (sml_FacetedSearch):

<se:buffer condition="translation.localscope.smartletoption(get,smartlet.get(options),noresultorder,default=0)==0"
 name="resultOrderSection" rem="Build result ordering block">

Also add noresultorder=1 to the list op supported values for the options parameter:

<se:member name="options" callbackaccess="read" clientaccess="read"
 rem="Supported values: (...),noresultorder=1,helpitem=123"></se:member>

If pressed, this could lead to corrupted comments.

Publication setup of iXperion 1.4 build 2 introduces SmartInstant 2.0 as a Add-On module.

The Asynchronous Importer (running in a separate thread) did perform some internal checks (e.g. parent, filename) before starting a job.

If one of those checks failed, the thread was aborted and only a log message was written to the Smartsite log.

Now, if a check fails a proper error is raised and, when enabled, this error is used as import job result (status=-1 and the error description will be written to the log field of the import job). Also the returnUrl, if specified, will be called when one of these internal checks fails.

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.

When you have created an Outscaling Datasource using the same code/name as an existing built-in datasource, the Synchronize Datasource action (e.g. using an scheduled event) didn't always take the correct datasource configuration into account.

This was due to the fact that Outscaling first evaluated its built-in datasources, before querying the osDatasources table to find the datasource configuration. This has been switched, manually configured datasources will now always take precendence over built-in datasources.

In the AIM references macro, you can now specify multiple channels for items to be rendered on subsequently.

Smartsite iXperion now has full Virtual Directory support. Any Virtual Directory configured in IIS will automatically be mapped in the Smartsite iXperion file system handling, and the config editor Set Site Security takes them into account. Search for 'Virtual Directories' in the documentation.

UTF-8 encoded url's are handled as if they are ISO-8859-1 encoded.

To fix this issue in an existing instance of Faceted Search:

• Edit the JavaScript item "/ClientData/Faceted Search Script"
• Change the call "unescape(v[1])" to "decodeURIComponent(v[1])" in line 26.

In case stored procedures that return recordsets were executed but the 'Statement returns recordset' checkbox was unchecked, a type mismatch error was raised.

To add the editor and presets to an existing installation copy the following items from a freshly installed empty site with Faceted Search (paths are relative to the Faceted Search Smartlet root folder):

• Configuration/Editors/Editor
• Configuration/Presets and all children

Its namespace changed from Smartsite.Core to Smartsite.Base. This was change was made specifically to have Json available to the XForms renderdevices.

The TestSuite is now better suited for cooperative team development. Just like the Smartsite Manager, it now supports item locking to protect users from overwriting each other's content.

Search for 'item locking' in the documentation for more information.

An unsafe data error was sometimes raised when properties were set from non-client origins

When a translation is referenced and not found, the error message is now clearer: it states whether the translation was out of scope or non-existing.

The AtalaSoft component always placed an AppMarker in the Jpeg which caused the problem.

The AIM background thread now silently recovers from a fatal error.

When AIM was used on reciprocal contentrelations, the AIM scanning thread would always be active because the queue of 'AIM dirty' items would not be emptied correctly.

Publication Setup will optimize CTFP Translation.Name for existing Smartsite databases.

The AIM rendering process did not bypass normal rendering of Smartlet items the way it did for other translations, wit the risk of irrelevant AIM relations to be registered.

Clearing the item cache for an item did depend on the ContentChange.Activation event, which was send asynchronously by the Outscaling background component.

That was (also) the reason the AIM reference collection was sometimes incomplete, because the publication engine didn't receive the ContentChange.Activation event yet before it was asked to resolve the AIM references.

Now, the cms manager sends the ContentChange.Activation event synchronously to the publication engine and Outscaling skips this event.

When using &lt; or &gt; in queries inside the XmlProcessor actions collection, an Xml exception could be raised.

The StorageProgID CTFP is removed from the Translation Name field, because the logic contained in this Storage Handler doesn't match the complex rules for translation resolving in iXperion, and the benefit of the handler was minimal, while the performance impact was large.

In order to prevent disclosure of too much information after a failed login attemp due to invalid credentials, do not expose the true error message. A hacker could enumerate valid user names. Instead, just leave a message like 'Login failed'.

In each Login page replace

<se:login error="{login.alert(this.error.message())}"> 

with

<se:login error="{login.alert('Login failed')}"> 

or even

<se:login error="{login.alert(locale.getstring(LOGON_FAILED))}"> 

The XmlProcessor macro actions collection now has an extra attribute: condition. Using this attibute, you can conditionally execute individual actions in the collection, based on the result of a Viper expression.

The System Panel action now contains a few more options, for instance for checking content with invalid AIM references. Also, the External References action (previously in the View menu) was moved to the system panel and both System Info actions (CMS/PUB) can now be found here.

The scan for Translation intellisense metadata (rem parameters) in translation.arg() calls has been improved.

The translation.name() viper method can now be used in preview logic of translations.

The benefit of this is that you can now use this dynamic syntax in the preview logic:

{string.eval(translation.name()+"()")}

The request.location() viper could return an url pointing to the default hostheader on channels with multiple hostheaders, when browsing on a non-default hostheader.

When calling smartlet.link(), Smartlet property values were not UrlEncoded, with the risk of resulting in corrupted urls.

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.

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.

The view vwUserProfileProperties did not function properly in the Personalization module when using Active Directory.

Pubication Setup to 1.4 will alter this particular view after running the Personalization database scripts.

The greywait.gif image, used in the Smartsite Item 'Shared Smartlet Style', was missing. This image will be added to the Smartsite instance after running Publication Setup.

Translations and Smartlets now have a new default value for their Logic (=Preview Data) field, which is a call to string.eval(). This new value ensures that the preview logic doesn't have to be modified when the translation name changes, for instance when a copy is made.

Please note that existing translation logic is not updated by the publication update.

The call to add to the translation Preview Data is:

{string.eval(translation.name() + "()")}

When saving items from the TestSuite, error messages due to business rules in the Workflow Engine would not be shown to the user.

Querystring parameters were accidently Xml encoded by the Enforce friendly url feature.

Releasesettings documentation can be found here: http://docs.ixperion.smartsite.nl/doc/releaseSettings.html

<releaseSettings>
	<add key="immutableLocators" value="true" />
	<add key="placeHolderSortNullValues" value="true" />
	<add key="syntaxErrorOnDoubleMacroIds" value="true" />
	<add key="EncodeUrlParameterSpaceAsDash" value="true" />
</releaseSettings>

Includes can be configured using the Page-scope buffer "smlConfig_EditorPreviewCSS". This is a comma-separated list of Locators.

The Import Site Configuration option didn't have any implementation and the Export Site Configuration option wasn't very useful.

The Set Site Url option used to execute the save dialog immediately after changing the site's urls. When cancelling this save dialog, the site urls weren't restored to their original values.

However, the Set Site Url option should just change the site urls and not execute the save dialog. So, this has been changed. You now need to click the Save button to persist the changes.

The Set Site Url option also didn't allow you to specify the same (base-)address to be able to fix misconfigured service addresses. This has been changed. When the specified site url is the same, now you just get an informational message and the option to continue.

Finally, the Restore Services option didn't take the site's serveraddress into account when restoring the service's addresses. This has been fixed as well.

You can now create a datalabel without a shape by using <se:datalabel shape="none" />

The PUB setup now uses the existing endpointBehavior element to add its configuration to instead of adding an additional element.

The FileLinkCopyJob now stores the LastWriteTime of the file in the database. It uses the new CTFP 'FileLinkLastWriteField' on the Content Type field 'Url' to denote where the LastWriteTime should be stored.

After running the 1.4 build 2 Publiction Setup's database scripts, ContentType FLK field URL will be added CTFP 'FileLinkLastWriteField'. The value of this CTFP will be set to 'CTSpecificDate1' or 'CTSpecificDate2' if the prior field is already in use. In case both fields are in use, a warning will appear stating that this CTFP must be set manually.

SetSiteSecurity failed to load the installed websites because was looking two level up from its current directory which failed if it was located in disk's root folder or one level deeper.

If no SmartletEditorAccess assignments exist in the database, the GUESTS group will recieve UseSmartletAndPreset access on all existing smartlets.

As from release 1.4 build 2 an overview of locked items (Item Locks) is introduced in the Configure Security section. In this overview locked items can be unlocked. This feature is useful especially when items are locked through TestSuite.

After running Publication Setup (both site files as database scripts) this feature will be introduced in an existing Smartsite instance.

When a cache macro contained code in which an error occurred that was trapped at a higher level than the cache macro itself (using an error parameter), it would incorrectly store cache.

Parameters 'default', 'error' and 'rem' can now be retrieved as well.

This could happen when the activation date of a set of items uses a date-time resolution higher than whole seconds (e.g. "2011-03-18 09:30:11.456") and the milliseconds part is below 500.

This is e.g. the case when using the emptysix database creation scripts.

The synchronization process of Outscaling constantly updates the LastActivationDate that's being used, but the resolution of this datetime is in whole seconds (due to the fact it's VB6 code). So, using the above example, the LastActivationDate becomes "2011-03-18 09:30:11.000".

Then, when comparing the activationdate of items with this LastActivationDate, every item which only differs <500 ms in datetime will still be returned from the query which determines which items to send. This can go on over and over again, until an item gets an activationdate which differs >500 ms compared to the LastActivationDate.

To fix this problem, the queries used by Outscaling to determine which items to send has been changed and now uses a datediff construction to filter out items having an activationdate which only differs less than 500 ms compared to the LastActivationDate.

The Empty Site now has a better, integrated W3 Item Validator that is available as soon as you log in as CMS user. For implementing on your own site, see http://ixperion.smartsite.nl/Community/Blogs/Marc_van_Neerven/How_to_check_private_sites_directly_using_the_W3C_Validator.html

The viper methods placeholder.addaggregatedjavascriptinclude() en placeholder.addaggregatedcssinclude() are now available.

A local sysem translation (ELBA element) can never be overridable, so an added rule makes sure the checkbox is disabled.

The context menu 'Browse' in the CMS Control Panel icon in the Windows Nofification Area did not point to the TestServerAddress

Line breaks in Viper expressions within XML/HTML attributes inside formatting elements would cause exceptions, due to missing decoding.

Line breaks in Viper expressions within XML/HTML attributes inside case elements (switch) and then/else elements (if) would cause exceptions, due to missing decoding.

State synchronization from the CMS for bulk updates has been improved.

Apart from BrowseStartPage, aim relations are now added for LoginUrl and SubTrees

You will immediately notice this change, when you select Open in new Window in the Smartsite Manager. The Url will automatically be translated into a Friendly Url.

For more information refer to Enforcing Friendly Urls.

The details tab in the Manager showed the wrong link to the BrowseStartPage of a channel.

The WebService macro now adds the given Url to the AIM relations and skips the execution phase during AIM requests.

AIM references to BrowseStartPage, SubTrees and LoginUrl are now registered.

The ClientIncludes RenderTemplate was modified, because it contained a deprecated viper call.

The View Details tab now shows extra properties for 'Add to Global Include' settings

The CSS to be loaded is determined by the render template for the current item in the manager's Active Channel (selectable in the Options dialog). If the item isn't available in the Active Channel, no CSS is loaded.

Information for Channel LoginUrl, SubTrees and Locale is now shown in the Details tab.

Errors caused by wrong dll versions that caused the site to not start properly disappeared and a NullReferenceException that happened further down the road was shown instead, thus obfuscating the underlying problem.

Smartsite used to generate urls like /nl/artikel.net?id=2 for browse start pages on non default channels. Smartsite now generates th url /nl for browse start pages on non default channels.

Any character that is affected by the JavaScript function escape() would increase the calculated length.

This includes the space and many interpunction characters.

The automatic sizing of editor controls can now be tweaked using registry and contenttype configuration. Search for 'ControlAutoSizing' in the documentation

The channel mapping display in view details has been improved and groups publication channels and system channels separately. Also, you can set the parameter "ShowSystemChannels" in View Details to "no" or "false" to hide system channels from the user.

When restarting the site from the TestSuite, an outdated dialog was shown in which you could not choose to save the current session locally.

Due to a flaw in the AttributeStartupCache logic, starting the site sometimes failed with an exception as a result.

A new viper is introduced to account for the fact that resolving clientscript enabled state is done by writing a session cookie on the client (at Scf initialization): in the first request of a new session, the state is in fact unknown, because the cookie cannot yet be retrieved. The new viper has this tristate logic built in. It returns 'Unknown', 'On' or 'Off'. The existing Scf.script.enabled() viper now supports passing a default value, so you can determine what to return when the state is 'Unknown'.

When 'Clear memory cache' in Reload Site (F6 in the TestSuite) is called, the channel state is now cleared. Channel state can be set using the viper methods in the channel class.

The option to listen to all channel hostheaders is only enabled when running as Publication Server, to protect you from errors during startup.

Results would be cached until a manual cache flush or reload site.

Loading this list lazily gives a startup performance improvement.

The icon of the underlying contenttype (specified in the CMS folder) is now shown.

The "Visualize SXML" debug feature in the TestSuite has been improved and now makes it easier to trace SXML code that produced HTML output.

The cachefile macro now throws an exception when trying to add cachekey dependencies if transfer is not set to "false", in which case the cache key can not be manipulated.

The ActiveChannel setting (in Tools/Options) now silently follows item selection done in View Details and Add/Edit Item. This makes sure the ActiveChannel setting is always a channel in which the selected item renders.

The channel selector for the edit/add item Preview tab now automatically restarts the preview on menu selection.

Depending on the current workflow an error dialog would be displayed after the normal warning that the chosen friendly name already exists in the database.

The dialog shows a message if the selected field's security zone doesn't allow smartlets.

In order to allow a table with foreign key relations to Contents.Nr and ContentTypes.Nr, the CTFP 'CrossTableName' is set to 'ContentTypesChannels' for field 'ContentTypes', ContentType 'CH'. This CTFP will be added into existing Smartsite databases by running the Publication Setup.

This is a change in the creation scripts only. Existing sites are not affected.

You can now use Sql Native Client drivers in your CMS connectionstrings.

When a selected page is ot available in the current channel, the TestSuite will now automatically switch to the first browsable channel the item will render on, if the option 'Synchronize active channel' is checked.

An exception was thrown when the resource could not be found.

If a default parameter is specified, Smartlet.GetResource will now return the default value. Otherwise an exception is thrown, like before.

Smartsite logic in the empty site and the add-on modules doesn't use the CSS class 'CoolForm' on forms anymore. Instead, the 'Scf' CSS class is used. This class has practically no styling and is only used to add Scf behavior to the form element (see /scf/jquery/behavior/classes/scf.form.js)

You can now configure the HTTP header X-Generated-By by setting the AppSetting "GeneratedByHttpHeader" to a custom value. If you set an empty string to the AppSetting, the HTTP header is not sent to the browser.

The Smartsite Profile Provider didn't add the necessary Outscaling events to the database.

This has been fixed, now the Smartsite Profile Provider adds the appropriate Outscaling events whenever a profile is created/updated.

Notice that synchronizing profiles and profile properties is opt-in, so it is required to create Outscaling Datasources for the underlying tables (UserProfiles and UserProfileProperties respectively).

Also, do not forget to remove the identities from the tables and to configure SmartNumbering.

The debug setting RaiseErrorOnSxmlError (smartsite.config) now has its counterpart in the debug menu of the Testsuite. Find handled SXML errors by simply toggling the 'Ignore SXML error handling' item in the debug/errors menu.

When choosing the remove option on the Active Directory Configuration node (for a particular site) within the Config Editor, the logonHandler registry setting "SixSecurity.LDAP" wasn't removed.

This means the cms will still be using Active Directory security, which is usually not the expected outcome when removing the Active Directory Configuration node. This has been fixed. This registry setting is removed as well.

When using non-standard hostheaders for channel-content, these hostheaders will now be respected by the Smartsite Manager.

The References macro can now be used without any references to channels (channel, channels properties), because it defaults to a list of all browsable channels. Note that the macro automatically selects the first channel on which an item can be rendered from the list, so there isn't a big performance penalty.

Old Scf files are now removed during the Pub setup, since they have been replaced by files with different names (duallist.js -> Scf.Form.DualListBehavior.js; confirm.js -> Scf.Form.AutoConfirm.js)

When adding AIM relations within a cache macro, the cache would not always be invalidated when changes were made to the related items.

Now that the pdf generator adds the querystring to the cache key signature, you can cache multiple versions of the pdf of the same item.

When using cache macros around sitemaps and xlinks macros, the cache would not always be invalidated when a relevant CMS change occurred.

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.

The type conversion within sqlquery parameters sometimes failed, especially with binary data.

These viper methods could lose state when passing Locators with Url Parameters.

Whenever lists of channels are shown, these are now sorted. The default channel will always be shown first. The rest of the list is shown in alphabetical order.

The default channel is now retrieved from the running Pub Server, instead of the legacy registry setting under UrlMunging.

An overload was added to the Response.Status() method, for suppressing IIS custom errors when setting the response status. In IIS7 integrated pipeline mode, setting the

suppressIISCustomErrors parameter to true is needed to let IIS skip further customerrors handling.

Some log messages now have loglevels that indicate that the log messages are less critical.

For each file which is included in the generated xml file, the SyncFileLinks macro now optionally writes generic file properties to the xml as well. This includes the following file properties: lastwritetime, creationtime, file size (in bytes) and the extension.

To enable this feature, set the WriteFileProperties parameter to true.

Using a se:transform macro as post-processing step on the generated xml file, you can then map these additional elements to e.g. adddate and/or moddate of an item. This way, it is possible to e.g. preserve the modification date of the file within the item itself.

Some fixes were made in the saving logic of the My Profile Smartlet. Specifically, the following code changes were made to the ShowForm() translation in the 'My Profile' Smartlet:

Old:

  {personalization.set('', NewsletterFrequency, convert.toint(request.form(lstNewsLetter)))}

New:

    <se:if expression="!user.isanonymous()">
              {personalization.set('', NewsletterFrequency, convert.toint(request.form(lstNewsLetter)))}
    </se:if>

Old:

  <se:if expression="string.length(w) GT 0" error="">

New:

  <se:if expression="string.length($w) GT 0" error="">

The LoginUrl setting of the default channel in EmptySix is now set to the code of the Login Page in that channel.

In 64-bit Smartsite iXperion installations, a change is required to the web.config:

Instead of the following:

<assemblies>
<clear/>
</assemblies>

... a number of assemblies have to be added after the <clear /> statement:

<assemblies>
<clear/>
<add assembly="Smartsite.Base" />
<add assembly="Smartsite.Runtime" />
<add assembly="Smartsite.AspNet.Bridge" />
<add assembly="Smartsite.Security" />
<add assembly="Smartsite.Web" />
<add assembly="Smartsite.Tools" />
<add assembly="Smartsite.Data" />
<add assembly="Smartsite.Scf" />
</assemblies>

Note that apart from the iXperion assemblies, you might have to add other assemblies as well, depending on your configuration.

In iXperion 1.4, the URL parameters feature, used to store querystring variables inside the path segment of a friendly URL, is only available if the release setting 'immutableLocators' is set. See http://docs.ixperion.smartsite.nl/Compatibility-Notes-for-14.html and http://docs.ixperion.smartsite.nl/doc/SXML/Knowledge_Base/Why-immutable-locators-are-essential.html

When deleting the children of a folder item and then converting the folder to a "normal" item, sometimes this last change (convert to "normal" item) failed to synchronize with the error message "Item can not have children because it's not a folder".

This was due to the fact that deleting items logic was executed after synchronizing added and changed items. This has been changed, now first deleting items logic is executed, followed by synchronizing added and changed items.

The list of deleted items did not contain items deleted by disabled users.

In Smartsite.config the defaultRedirect attribute of node customErrors in node runtime was set to ERROR_PAGE. This may result in an incorrect error page since ERROR_PAGE is not always used as the page's friendly name. Instead, this attribute will be set to /?id=ERROR_PAGE.

After running Publication Setup to 1.4, Smartsite.config will be automatically updated.

When using the Configuration Encryption feature included within the Config Editor (or using the ConfigProtect tool), sensitive information included within the web.config, such as username/password information for the Active Directory membership provider, is not encrypted.

There's a good reason for that. The Configuration Encryption feature uses a Smartsite iXperion specific technique and if it was to be applied on the web.config, ASP.NET wouldn't be able to read (sections of) the web.config file anymore.

However, ASP.NET has its own feature to encrypt sensitive information within the web.config, which is Protected Configuration.

The article Encrypting configuration information within the web.config describes this procedure.

FileLink items now return an Http 404 error when the file does not exist.

The preview tab was not visible in the manager when an item was added to a CMS Folder or any other content type that was not mapped to any channel on which the new item's content type is browsable.

Due to a bug, the built-in list of default schema set id's was always shown and not the actual list of available schema set id's. This has been fixed.

Handling large files can result in various issues, all due to size limits / restrictions. This is usually not a bug, but a configuration issue.

Examples:

- When trying to upload a large file within the cms manager, the upload may fail due to exceeding the maximum request length.

- When Outscaling tries to synchronize a large file, this may fail due to exceeding the maximum request length or exceeding the maximum attachment size.

- When the FileLinkCopy scheduled job tries to write the binary data of a file to the database, it fails due to exceeding the maxfilesize setting.

The following articles provide more information to prevent this kind of issues:

Handling large files

FileLinkCopy scheduled job

Including files within the indexed views

New Smartsite iXperion implementations will contain a Dutch translation of the user action 'Edit Item (read-only)'.

For existing implementations, edit the _default.xml file in de System/Locales folder and add this code to it:

<object name="menu_options">
	<string name="Edit Item (read-only)">Item Bewerken (alleen lezen)</string>
</object>

In prior releases of Smartsite iXperion, when upgrading the pre-released module formally named 'TestSearch' to the latest version of Faceted Search, the update script will result into unwanted situation in SmartNumber implementations.

Thus, the previous update script would only rename tables such as TsSearchGroups to TsSearchGroups_DROP_ME without taking any SmartNumber issues into consideration, leaving the SmartNumber trigger on the DROP_ME table.

Now, the renaming of each TextSearch table, will implicitly remove all SmartNumber settings of that particular table (of course only when a SmartNumber is set).

Please note that newly created tables must be configured for SmartNumbers manually.

Ogone has changed the way that payment orders are to be signed. The new version can be used with both the old and the new way to calculate signatures.

Within some validators parameter queries are used. When using an Oracle database, the parameters passed to the command object did have the wrong type. This has been fixed.

When using the UseTabbedPreview CTFP explicitly, the Channel selection button turned to disabled.

This is a requirement for Webrichtlijnen. Simply mark the column containing the page content as "ContentKolom" in the Grid Row Chooser and it will be rendered first in the html. CSS is used to place the column at the right position visually.

See here for instructions to add this behaviour to an existing SmartInstant 2.0 site.

It is possible to create an EmptySix Database using the Database Creation Scipts with SmartNumbering.

Module Faceted Search contains several configuration and documentation items which need te be restricted from Guests and Visitors in order to disclose too much information wich could be abused.

It is highly recommended to review security settings on existing Smartsite implementations of Faceted Search.

In order to avoid disclosure of too much technical information which could be misused, all documentation items of the DigiD and Ogone modules have been made restricted for Guests and Visitors.

It is highly recommended to do so for existing Smartsite implementations with DigiD and/or Ogone module.

New setups of the Personalization module will have all configuration and documentation items security set in order to avoid abuse.

It is highly recommended to review existing Personalization implementations on security settings.

As of Smartsite iXperion 1.4 build 2, the Active Directory membership provider supports a number of advanced settings: ObtainPrimaryGroup, ObtainParentGroupsForPrimaryGroup, MaxParentGroupRecursionDepth and UpdatePrimaryGroup.

(For more information, see the article Active Directory Role- and Membership Providers.)

These advanced settings are now also available within the Config Editor. Notice however, that you need to switch to "Advanced Mode" (View menu) to be able to view/configure these settings.

Note: when one of these advanced settings equals its default value and the setting is not already present within the web.config, it will not be added.

Now that the image server adds querystring parameters to the cache key, you can add logic to your item to show a different image based on querystring parameters and still use the image server on those images.

When using the SQL Native Client ("SQLNCLI10.1" or "SQLNCLI.1") as provider within the ConnectionString Cms manager registry setting, the Config Editor did reset it to "SQLOLEDB.1" when saving any changes for a specific site.

To fix this problem, the SQL Native Client support within the Config Editor has been improved.

Also, the Cms Database (ConnectionString within the manager registry configuration) is now always displayed seperately. This way, the connection string for the cms manager can be configured independently and it may differ from the connection string(s) used within Smartsite.Data.config, in terms of the provider used and other advanced connection string settings.

A threading issue with the Cache macro and DataTables was resolved

Database script to 1.4 build 3 will add primary key PK_SubTreeHierarchy on both columns, if not added yet.

Due to a fix of a Chrome 10 related bug in the previous version/build, some import wizards didn't jump automatically to the next screen anymore, whereas the Next button has been disabled (by design) to do so manually.

As a result, it was no longer possible to import Word Documents and/or HTML Files using this wizards.

This has been fixed.

Outscaling didn't check whether or not the target server instance was enabled when executing scheduled events. This has been fixed.

The manual Cms manager action Import ContentTypes (part of Manage ContentTypes) did have some issues when importing a contenttype into a group with a different set of logical fieldnames.

It also wasn't consistent compared to Manage ContentTypes (it was e.g. possible to add a contenttype field on a derived contenttype using Import ContentType, whereas using Manage ContentTypes this is only possible on contenttype group level).

The Import ContentTypes functionality has been changed to solve these problems. See the article Import ContentType changes for more information.

• The call to the pay_callback() translation is missing a closing bracket at the end.
• The payment module is to be called as <se:payment ... />.

In previous versions of iXperion, it was possible (with some minor limitations) to use multi-domaining for the publication engine.

As of iXperion 1.4 build 3, multi-domaining is now also available for the cms manager engine. To make this possible, some configuration changes were needed, most notable the fact that each membership provider should now use its own configuration section. An additional advantage of this change is, that now every membership provider can use its own group definitions as well.

The name of the configuration section to be used for a particular provider must be provided using the settingsSectionName attribute on the membership provider element.

For more information, see the article Multi-domaining support revisited.

When saving items, the AIM scanning process could used cached versions of the items on the Publication Server to load the references from, resulting in the persisted AIM references in the CMS to run behind. This could lead to situations where referential integrity was lost.

Due to changes in threading model and synchronous state updating in 1.4, the outscaling background component could be triggered too soon. This could then lead to resources not being outscaled correctly.

Because the document was not cleaned up before validation takes place, the document contained some invalid Html which caused an error.

When using the Smartsite CMS DataEditor action, the Native Sql Client (Provider=SQLNCLI10.1...) was not detected autoamtically.

The Smi dashboard now only displays primary content in the list of most popular pages, making the list more informative.

In rare cases, when using pulling mechanism, items were pulled back from target server instance to the originator server instance due to the fact that the originator instance id was updated a (fraction) second later than the activation date was set. This has been fixed.

The error page for the url http://www.example.com/pub/xxx.html was created by IIS while the error page for the url http://www.example.com/pub.net?id=xxx was created by Smartsite. Now both urls are handled by the Smartsite custom error page, which allows you to use channel specific error handling.

Because of this, the item named Script in folder Faceted Search Smartlet/Clientdata has been updated.

Sometimes the Hostheader information from the pub server is unavailable in the CMS, causing Smartlet Editor and Library to fail

When a non-existing attibute was removed using the RemoveAttribute() method in the XmlProcessor macro, Smartsite could run into an endless loop.

When previewing a Smartlet, the viper call smartlet.name() in the Preview Logic resolved to the base Smartlet name in the Smartlet folder, when multiple Smartlets were stored in the same folder.

When using the Config Editor, additional Oracle connection string properties (any property which is not specifically "recognized" by the Config Editor) did get lost when saving any changes for a specific site.

This was due to the fact that a new connection string was build (from "scratch") based on the settings within the Config Editor.

To fix this problem, now the original connection string is always used as template to create a new connection string based on the settings within the Config Editor.

Notice that the same problem, before this fix, could have occurred for SQL server connection strings as well.

Smi reports were sent to the user that is configured in the Scheduled Task for the Smi Reports instead of the user that actually created the report.

The "previous" and "first" buttons on the first page of results and the "next" and "last" buttons on the last page would look as if they were disabled, but they would actually still work, breaking the search results.

The implementation of channel-specific LoginUrl processing used non thread-safe logic. The implementation has been rewritten to avoid this.

When the Friendly Urls feature is not installed or not used in a channel, the channel-specific LoginUrl handling could result in errors.

Windows sometimes changes the temporary folder of a user to a subfolder of the original temp folder with a numeric postfix, like temp\1, temp\2 etc. SetSiteSecurity now recognizes these subfolders and sets the ACL's on these folders as well.

The Join macro can now also sort descending by adding " DESC" after the column name and can sort on multiple columns, seperated by a comma.

The CMS EditControls LinkInput, FileInput and SelectInput now support the MaxLength CTFP

If you modify a thesaurus by using the Edit Thesaurus action, a content change event is now raised on the thesaurus item. This event allows you to e.g. expire an Sxml cache block by binding to the thesaurus item.

Box-shadow and border-radius directives were removed from the includes. These styles are now added through a JavaScript include.

Style rules can be added to a page through JavaScript using the following snipet:

(function($){
	$(document).ready(function(){
		$("<style type='text/css'>.class {color: #000000;}</style>").appendTo("head");
	});
})(jQuery);

Text-shadow directives were removed from the includes. These styles are now added through a JavaScript include.

Style rules can be added to a page through JavaScript using the following snipet:

(function($){
	$(document).ready(function(){
		$("<style type='text/css'>.class {color: #000000;}</style>").appendTo("head");
	});
})(jQuery);

This bug will be fixed in existing SmartInstant implementations by running the update script of the SmartInstant module.

The copyright meta tag now displays the author field of the current item as the copyright holder.

SMARTINSTANT UPGRADE (notice, some points can already been updated by the update script)

======================================================================

1. To update existing sites manually, update the links in the rowformat property in sml_Weblog() that use the smartlet.link() viper to use channel.link() instead:

<a href="{channel.link(this.field(nr))}"> ... </a>

2. Query parameter 'layout' has been removed from CSS includes.

De layout parameter for CSS includes is no longer needed. The include item itself can determine the current design using the channel.state.get() viper.

This had been implemented in the layout item and other items in the Desisgn\stylesheets folder.

3. SmartInstant grid_css() translation has been updated.

There now is a different set of includes for screen, print and pdf.

Update to:

<se:region whitespace="remove">

<se:placeholder.cssinclude />

<se:placeholder.css />

<!--// customized jquery-ui - CSS2.1 compliant, stripped from unneeded stuff -->

<se:placeholder.addcssinclude url="/scf/jquery/smoothness/sms-jquery-ui.css" media="screen"/>

<se:if expression="!url.commands.exists(request.location(), 'pdf')" whitespace="simpleformat" trim="right">

<se:then rem="render for screen and print">

<link rel="stylesheet" href="{cms.getdescendantbytitle($'page:channeldesign','Design/Special stylesheets/print.css',Off)}" media="print" />

<!--[if lt IE 7]>

<link rel="stylesheet" href="{cms.getdescendantbytitle($'page:channeldesign','Design/Special stylesheets/IE6.css',Off)}" type="text/css" />

<![endif]-->

<se:placeholder.addcssinclude url="{url.setparameter(MERGE_CSS_ITEMS, ts, scf.includes.global.modifieddate('CSS', default=datetime.minvalue()))}" media="screen" priority="-50" />

</se:then>

<se:else rem="render for pdf">

<link rel="stylesheet" href="{cms.getdescendantbytitle($'page:channeldesign','Design/Special stylesheets/print.css',Off)}" />

</se:else>

</se:if>

</se:region>

4. Suggested/Not Required: New local translation StockColor simplifies sharing of color definition between several includes.

The Design/Stylesheets folder, within a Smartinstant design, now includes a translation named StockColor(name). To initialize the stock color, invoke the translation, without parameters, from the Logic field.

You can then use {stockcolor(name)} to apply a stock color value.

5. SmartInstant's smartlet 'Create Account' did not work by default

To make smartlet 'Create Account' function properly, move item 'Security Extension Assembly' (GUID-C37163170E7C4966A31C88A30FFBC031) to a folder which is registered as a folder for virtual assemblies.

In case of new implementations: SI_VIRTUALASSEMBLIES.

6. No action required.

7. Faceted search: type="text" added to searchterm text input.

The content of translation ixs_RenderFormControls() has been updated.

The searchterm input now includes an additional attribute type="text" to comply with the Webrichtlijnen validation.

Update <input name="{string.concat($id,_searchterm)}" value="{string.encodeattribute(translation.arg(searchterm),false)}" />

to: <input name="{string.concat($id,_searchterm)}" type="text" value="{string.encodeattribute(translation.arg(searchterm),false)}" />.

8. Rating smartlet would render inline style attributes.

For compliance with webRichtlijnen, these directives have been moved to a style sheet in the head section.

Update sml_Rating() to:

{license.checkfeature(Web20Toolkit)}

<se:smartlet rem="Show Rating component with Progressive Enhancement">

<se:parameters>

<se:parameter name="properties">

<se:collection>

<se:member name="title" type="string" editable="true" rem="Title to show">Rate this page</se:member>

<se:member name="scale" type="integer" editable="true" clientaccess="read" callbackaccess="read" rem="Scale to use (3 to 10)">5</se:member>

<se:member name="value" type="integer" clientaccess="readwrite" callbackaccess="readwrite">0</se:member>

<se:member name="average" type="float" clientaccess="read" callbackaccess="write">0</se:member>

<se:member name="voted" type="boolean" clientaccess="read" callbackaccess="write">false</se:member>

<se:member name="subkey" type="string" callbackaccess="read" editable="true"></se:member>

<se:member name="imageWidth" type="integer" clientaccess="read" callbackaccess="read">16</se:member>

<se:member name="allowAnonymous" type="boolean" editable="true" callbackaccess="read">false</se:member>

<se:member name="getHighestRated" type="integer" editable="true">0</se:member>

<se:member name="getHighestRatedFor" type="integer" editable="true">0</se:member>

<se:member name="ratingItem" type="integer" editable="true" clientaccess="read" callbackaccess="read">0</se:member>

</se:collection>

</se:parameter>

<se:parameter name="displayname">

{locale.getstring(RATING_RATING)}

</se:parameter>

<se:parameter name="xml" whitespace="remove">

{sys.iif(smartlet.get(scale) LT 3 || smartlet.get(scale) GT 10, sys.throwexception(InvalidArgument, "Scale can be between 3 and 10."))}

<se:if expression="smartlet.get(ratingItem) == 0">{smartlet.set(ratingItem,url.getitemnumber(smartlet.page()))}</se:if>

<se:if expression="smartlet.get(allowAnonymous)">

<se:then>{buffer.set(userid,security.user.guestuserid())}</se:then>

<se:else>{buffer.set(userid,user.userid())}</se:else>

</se:if>

<se:if expression="smartlet.isajaxcallback()">

<se:then>

{smartlet.set(voted, true)}

{useritemfeedback.setuserfeedback(smartlet.get(ratingItem),$userid,rating,smartlet.get(subkey),(100*smartlet.get(value))/smartlet.get(scale))}

{response.setcookie(smartlet.id(smartlet.get(ratingItem)),1,datetime.addyears(datetime.now(),1))}

{smartlet.set(average, translation.localscope.getrating(smartlet.get(ratingItem),smartlet.get(subkey)) * smartlet.get(scale)/100.0)}

</se:then>

<se:else>

<se:if expression="smartlet.get(getHighestRated) != 0">

<se:then>

<se:smartletbox trim="both" caption="{locale.translate(smartlet.get(title))}">

<se:if expression="smartlet.get(getHighestRatedFor) == 0">

<se:then>{buffer.set(highest,useritemfeedback.gethighestrated('rating',smartlet.get(subkey),smartlet.get(getHighestRated)))}</se:then>

<se:else>{buffer.set(highest,useritemfeedback.gethighestrated('rating',smartlet.get(subkey),smartlet.get(getHighestRatedFor),smartlet.get(getHighestRated)))}</se:else>

</se:if>

<se:format

inputdata="highest">

<se:rowformat><li><a href="{channel.link(this.field(nr))}">{this.field(title)}</a> ({math.round(this.field(rating),1)})</li></se:rowformat>

<se:resultformat><ul>{this.result()}</ul></se:resultformat>

</se:format>

</se:smartletbox>

</se:then>

<se:else>

{smartlet.set(subkey,smartlet.get(subkey, default=smartlet.id()))}

<se:if expression="smartlet.get(value) == 0">

<se:then>

<se:if expression="smartlet.get(allowAnonymous)">

<se:then>

{buffer.set(voted,request.getcookie(smartlet.id(smartlet.get(ratingItem)),default=false))}

</se:then>

<se:else>

<se:if expression="!user.isanonymous()">

<se:then>

{buffer.set(voted,useritemfeedback.hasusergivenfeedback(smartlet.get(ratingItem),user.userid(),"rating",smartlet.get(subkey)))}

<se:if expression="buffer.get(voted)">

{smartlet.set(value, useritemfeedback.getuserfeedback(smartlet.get(ratingItem),user.userid(),"rating",smartlet.get(subkey)))}

</se:if>

</se:then>

<se:else>{buffer.set(voted, true)}</se:else>

</se:if>

</se:else>

</se:if>

{smartlet.set(voted, $voted)}

</se:then>

<se:else>

<!-- // vote -->

{useritemfeedback.setuserfeedback(smartlet.get(ratingItem),$userid,rating,smartlet.get(subkey),(100*smartlet.get(value))/smartlet.get(scale))}

{response.setcookie(smartlet.id(smartlet.get(ratingItem)),1,datetime.addyears(datetime.now(),1))}

{smartlet.set(voted, true)}

</se:else>

</se:if>

{smartlet.set(average,translation.localscope.getrating(smartlet.get(ratingItem),smartlet.get(subkey)) * smartlet.get(scale)/100.0)}

<se:smartletbox trim="both" caption="{locale.translate(smartlet.get(title))}">

<se:if expression="smartlet.get(voted) || (user.isanonymous() AND !smartlet.get(allowAnonymous))" trim="both">

<se:then>

<se:switch expression="true">

<se:case expression="!smartlet.get(allowAnonymous) AND !user.isanonymous()" break="false">

{smartlet.set(value, translation.localscope.getrating(smartlet.get(ratingItem),smartlet.get(subkey),user.userid()) * smartlet.get(scale)/100)}

</se:case>

<se:case expression="smartlet.get(value)!=0">

{buffer.set(postedfeedback,locale.translate("You rated this page with a {0} out of {1}.",smartlet.get(value),smartlet.get(scale)))}

</se:case>

<se:case expression="(user.isanonymous() AND !smartlet.get(allowAnonymous))">

{buffer.set(postedfeedback,locale.translate("You are not allowed to rate this page."))}

</se:case>

<se:case>

{buffer.set(postedfeedback,locale.translate("You already rated this page."))}

</se:case>

</se:switch>

<se:if expression="smartlet.get(value) == 0">{smartlet.set(value,smartlet.get(scale))}</se:if>

<se:placeholder.addcss whitespace="preserve">

#{smartlet.id()} span.smlAboveAverage {

width: {math.round(smartlet.get(imageWidth) * smartlet.get(scale))}px;

}

#{smartlet.id()} span.smlBelowAverage {

width: {math.round(smartlet.get(imageWidth) * smartlet.get(average))}px;

}

</se:placeholder.addcss>

<span class="smlAboveAverage" title="{locale.translate('Average rating: {0}', math.round(smartlet.get(average),1))}">

<span class="smlBelowAverage"><se:for whitespace="remove"

from="1" to="{smartlet.get(value)}">

<img alt="" src="{smartlet.getresource('/clientdata/images/selectStar.png')}" class="smlrating" />

</se:for><se:for whitespace="remove"

from="{sys.eval(smartlet.get(value) + 1)}" to="{smartlet.get(scale)}">

<img alt="" src="{smartlet.getresource('/clientdata/images/unselectStar.png')}" class="smlrating" />

</se:for></span>

</span>

<div>{buffer.get(postedfeedback,default="")}</div>

</se:then>

<se:else>

<form method="post" action="{smartlet.page()}">

<div class="fieldset">

<se:for from="1" to="{smartlet.get(scale)}" trim="both">

<button type="submit" name="{smartlet.id(value)}" class="smlRating smlRatingNS" value="{this.index()}"><span class="hide">{this.index()}</span><!--[msiebutton]{this.index()}--></button>

</se:for>

</div>

</form>

</se:else>

</se:if>

</se:smartletbox>

</se:else>

</se:if>

</se:else>

</se:if>

</se:parameter>

</se:parameters>

</se:smartlet>

9. The ItemComments Smartlet was not Web Guidelines compliant

The ItemComments Smartlet had some non-compliant HTML.

To update an existing implementation (Notice; this could already been updated by the upgrade scripts), open the sml_ItemComments() item, and search for:

<se:if expression="smartlet.testaccess(forumpost)">
<se:then><h3>{locale.translate("Comments have been closed for this item.")}</h3></se:then>
<se:else><h5>{locale.translate("You are not allowed to post here.")}</h5></se:else>
</se:if>

... and change it to:

<se:if expression="smartlet.testaccess(forumpost)">
<se:then><div class="smlNotification">{locale.translate("Comments have been closed for this item.")}</div></se:then>
<se:else><div class="smlNotification">{locale.translate("You are not allowed to post here.")}</div></se:else>
</se:if>
<div>
<input type="submit" class="buttonSubmitHide"/>
</div>

Now, open the ClientData/Css Item, and add the following code at the bottom:

{smartlet.nameselector("input.buttonSubmitHide")} {
	display:none;
}

10. The Flickr smartlet produced non-compliant HTML

The HTML did not conform to Web Guidelines.

SmartInstant installations and updates will have the changes necessary.

To update existing sites, download the updated Flickr Smartlet (3.0) from the iXperion Market: http://market.smartsite.nl/Community/Sml/The_Smartlets/Competition-Flickr-Smartlet/Competition-Flickr-Smartlet-Downloads.html.

11.The Event Calendar output was not Web Guidelines compliant

Web Guideline prescribe that table elements are decorated using the 'scope' attribute.

To implement the changes in an existing Web Toolkit install, open the BuildCalendar() translation, and:

- add scope="row" to each th element under the tr with class 'smlPanelHeader'

- add scope="col" to each th element under the tr with class 'DayNames'

- add scope="col" to each td element

12. Twitter Smartlet display not XHTML compliant

Text retrieved by the Twitter Smartlet was not escaped for XHTML display.

SmartInstant sites created using the 1.4 setup will automatically be updated.

To implement the changes manually, make the following changes to the Format() translation:

{translation.localscope.expand(scope.format.field(text))}</span>
==>
{translation.localscope.expand(string.xmlencode(scope.format.field(text), Ampersand))}</span>

... and ...

<em>{scope.format.field(source)}</em>
==>
<em>{string.xmlencode(string.xmldecode(scope.format.field(source)), 'Ampersand,DoubleAmpersand')}</em>
 
13. SmartInstant search box no longer uses query paramers to pass the search term.
In SmartInstant, the search box in the upper right corner uses the query string to pass the searchterm to the search engine.
This approach is not recommended by the The web guidelines (Webrichtlijnen).
To forward the search term using a form post instead of the query string, apply the following changes to an existing SmartInstant site:
 

In the Manager, jump to item preset_Header_Search() and edit the translation CustomFunction() in the same folder.
Replace method="get" by method="post".
Edit item sml_FacetedSearch().
Replace the following code block below code block, present in the smartlet item:
<se:case expression="!smartlet.hasclientvalues() AND request.query.exists(q)">
{smartlet.set(searchterm,request.query(q,true))}
</se:case>
==>
<se:case expression="!smartlet.hasclientvalues() AND request.query.exists(q)">
{smartlet.set(searchterm,request.query(q,true))}
</se:case>
<!--// to allow back button, convert http post to http get using post persistance -->
<se:case expression="!smartlet.hasclientvalues() AND (request.form.exists(q) OR request.form.persistance.istransferred())">
	{request.form.persistance.transfer('AbortOriginalPosting,useCookie')}
	{smartlet.set(searchterm,request.form(q,true))}
</se:case>
<!--// load query from cookie if not ajax callback or form post-->
<se:case expression="!smartlet.hasclientvalues() AND request.getcookie($cookiename,default='')!=''">
	{smartlet.set(action, '')}
	{buffer.set(queryspecs, convert.frombase64(request.getcookie($cookiename,default=''),default='',error='') )}
</se:case>

Forms posts often cause 'Web page has expired' errors when using the browser back button.
To avoid this, add the response.setmaxage() viper directly above the line thats adds the jQuery include:
{response.setmaxage(0, rem="suppress 'web page has expired' errors when using form post")}
{placeholder.addjavascriptinclude('/Scf/jQuery/jquery-ui.js',false, 90)}
 

 
14. The BuienRadar Smartlet form did not have any submit button
This was not Web Guidelines compliant.
For installation in an existing site, download the update from the iXperion Market: http://bit.ly/nRNHoL
 
15.Webrichtlijnen: non-compliant CSS removed from SmartInstant 2.0 design 3 includes
Text-shadow directives were removed from the includes. These styles are now added through a JavaScript include.
Style rules can be added to a page through JavaScript using the following snipet:
(function($){
$(document).ready(function(){
$("<style type='text/css'>.class {color: #000000;}</style>").appendTo("head");
});
})(jQuery);
Notice; Don't forget to check your own site design for the use of text-shadow directives.
 
16.Webrichtlijnen: non-compliant CSS removed from SmartInstant 2.0 design 2 includes
Box-shadow and border-radius directives were removed from the includes. These styles are now added through a JavaScript include.
Style rules can be added to a page through JavaScript using the following snipet:
(function($){
$(document).ready(function(){
$("<style type='text/css'>.class {color: #000000;}</style>").appendTo("head");
});
})(jQuery);
Notice; Don't forget to check your own site design for the use of Box-shadow and border-radius directives.
 
17. Item GUID-BADCC174A9D04A139BF0D27D7206CD79 (Format(dataTable, avatar, max)) replace this line:
<a class="tweet_foot" href="http://twitter.com" title="Powered by Twitter">Twitter</a> 

with
<p><a class="tweet_foot" href="http://twitter.com" title="Powered by Twitter">Twitter</a></p>

 
18. Item GUID-06834F1E33C84698BC5DC74735A60AC6 did not contain a submit button within the form tag. Alter this item: 
<form action="{smartlet.page()}" method="post" class="{smartlet.name()}">
<se:smartletbox caption="{buffer.get(caption)}" innerclass="tweets" buttons="{buffer.get(buttons, default='')}">
{buffer.set(txt, sys.iif(!string.isempty($error), $error, $data))}
{sys.iif(scf.script.enabledstate()!='On', html.tag(noscript, $txt), $txt)}
<div class="clear"></div>
</se:smartletbox>
<p><input type="submit" class="buttonSubmitHide"/></p>
</form>

 
Also, in CSS item GUID-384105FFAD4C473AA7B7FC79C838A4C3 add this:
.buttonSubmitHide {
display: none;
}

19. CSS 2.1 item GUID-0795736A95EA459393B743E05E61B5C3 remove block "li:even".
 
20. CSS 2.1 item SMARTLET_SHARED_STYLE "cursor: hand;" should be "cursor: pointer;"
 
21. CSS 2.1 item GUID-49A7DA762EF24A4E880176EE67BFF09E (layout_designspecific.css) replace:
.imagetoplist .thumbnail{
-moz-border-radius: 5px;
-webkit-border-radius: 5px;
border-radius: 5px;
}

with
/* .imagetoplist .thumbnail{
-moz-border-radius: 5px;
-webkit-border-radius: 5px;
border-radius: 5px;
}
*/

 
22. Alter #header in GUID-000D3B8345E54DC68717560D1A8E18E9 (1429) to;
#header{
position: absolute;
top: 0px;
left: 0;
padding: 0;
background-image: url({itemdata.field(header, request.query(layout,default=$design),default=itemdata.field(header,$design))});
background-repeat: repeat-x;
background-position: left top;
}

 
23. Add to rss item GUID-4C24BD0C5DAA467AB8E6CF4B190BD1D5: 
 
<p><input type="submit" class="buttonSubmitHide"/></p>:
 
<se:smartletbox buttons="{buffer.get(buttons)}" caption="{buffer.get(caption)}" formattribs="{html.attributes(method,post,action,channel.link(itemdata.number()))}">
<se:if expression="!scope.smartletbox.usebox()">
<div class="{smartlet.name(btns)}"><span class="{smartlet.name(btns)}">{buffer.get(caption)}</span><div class="{smartlet.name(btns2)}">{buffer.get(buttons)}</div></div>
</se:if>
{buffer.get(html)}
<p><input type="submit" class="buttonSubmitHide"/></p> 
</se:smartletbox>

 
Also, in CSS item GUID-81D5A35C04C44A70915FE15B7B718CB8 add this:
.buttonSubmitHide {
display: none;
}

 
24. Tag h5 should be h3 in item GUID-7FDC558ECE324A34ADFE9B820262A841:
<se:if expression="buffer.get(locked)">
<se:then><h3>{locale.translate("This topic has been locked.")}</h3></se:then>
<se:else><h3>{locale.translate("You are not allowed to post here.")}</h3></se:else>
</se:if>

 
25. Alter the block in GUID-7FDC558ECE324A34ADFE9B820262A841:
<se:else>
<se:if expression="buffer.get(locked)">
<se:then><h3>{locale.translate("This topic has been locked.")}</h3></se:then>
<se:else><h3>{locale.translate("You are not allowed to post here.")}</h3><p><label></label><input type="submit" class="buttonSubmitHide"/></p></se:else>
</se:if>
</se:else>

Also, in CSS item GUID-81D5A35C04C44A70915FE15B7B718CB8 add this:
.buttonSubmitHide {
display: none;
}

 
26. css item "Skin-DarkBlue" replace:
.{smartlet.name()}.darkblue textarea")} {
width: 98%;
height: 100px;
}
 
.{smartlet.name()}.darkblue input.text")} {
width: 98%;
}

 
with:
.{smartlet.name()}.darkblue textarea {
width: 98%;
height: 100px;
}
 
.{smartlet.name()}.darkblue input.text {
width: 98%;
}

 
also, replace:
/* posts */
.{smartlet.name()}.darkblue div.smlCommentSource")} {
background-image:none;
background-color:#798C98;
color: #FFFFFF;
}
.{smartlet.name()}.darkblue span.smlCommentSource")} {
font-weight: bold;
font-size: 0.8em;
}
.{smartlet.name()}.darkblue span.smlStatus")} {
font-size: x-small;
font-style:italic;
}
 
.{smartlet.name()}.darkblue span.smlButtons")} {
font-size: x-small;
}
.{smartlet.name()}.darkblue div.smlCommentBody a")} {
text-decoration: underline;
}
 
.{smartlet.name()}.darkblue div.smlCommentBody a:hover")} {
text-decoration: none;
}
.{smartlet.name()}.darkblue div.smlCommentBody")} {
background-color: transparent;
background-image: none;
border: 2px solid #798C98;
border-top:0px;
}
.{smartlet.name()}.darkblue span.smlButtons button")} {
background-color: transparent;
color: white;
border: 0;
font-size: x-small;
}
.{smartlet.name()}.darkblue div.smlInactive div.smlCommentBody")} {
border: 2px solid #ff6600;
border-top:0px;
background-color: #ffaa88;
}
 
.{smartlet.name()}.darkblue div.smlPreview > div.smlCommentBody")} {
border: 2px solid #aaeeaa;
border-top:0px;
background-color: #aaffaa;
}
.{smartlet.name()}.darkblue div.smlEditHistory")} {
color:#DDDDDD;
font-size: 80%;
}
.{smartlet.name()}.darkblue span.smlWarning")} {
color: red;
white-space: nowrap;
}
.{smartlet.name()}.darkblue div.fieldset")} {
border-top: 1px dashed;
border-bottom: 1px dashed;
}
.{smartlet.name()}.darkblue a.smlTogShow")} {
background-image: url(/res/plusicon.gif);
background-repeat: no-repeat;
}
.{smartlet.name()}.darkblue a.smlTogHide")} {
background-image: url(/res/minusicon.gif);
background-repeat: no-repeat;
}

 
with
/* posts */
.{smartlet.name()}.darkblue div.smlCommentSource {
background-image:none;
background-color:#798C98;
color: #FFFFFF;
}
.{smartlet.name()}.darkblue span.smlCommentSource {
font-weight: bold;
font-size: 0.8em;
}
.{smartlet.name()}.darkblue span.smlStatus {
font-size: x-small;
font-style:italic;
}
 
.{smartlet.name()}.darkblue span.smlButtons {
font-size: x-small;
}
.{smartlet.name()}.darkblue div.smlCommentBody a {
text-decoration: underline;
}
 
.{smartlet.name()}.darkblue div.smlCommentBody a:hover {
text-decoration: none;
}
.{smartlet.name()}.darkblue div.smlCommentBody {
background-color: transparent;
background-image: none;
border: 2px solid #798C98;
border-top:0px;
}
.{smartlet.name()}.darkblue span.smlButtons button {
background-color: transparent;
color: white;
border: 0;
font-size: x-small;
}
.{smartlet.name()}.darkblue div.smlInactive div.smlCommentBody {
border: 2px solid #ff6600;
border-top:0px;
background-color: #ffaa88;
}
 
.{smartlet.name()}.darkblue div.smlPreview > div.smlCommentBody {
border: 2px solid #aaeeaa;
border-top:0px;
background-color: #aaffaa;
}
.{smartlet.name()}.darkblue div.smlEditHistory {
color:#DDDDDD;
font-size: 80%;
}
.{smartlet.name()}.darkblue span.smlWarning {
color: red;
white-space: nowrap;
}
.{smartlet.name()}.darkblue div.fieldset {
border-top: 1px dashed;
border-bottom: 1px dashed;
}
.{smartlet.name()}.darkblue a.smlTogShow {
background-image: url(/res/plusicon.gif);
background-repeat: no-repeat;
}
.{smartlet.name()}.darkblue a.smlTogHide {
background-image: url(/res/minusicon.gif);
background-repeat: no-repeat;
}
 
CSS item GUID-FC0784018A0B49408FB0D638B19E5672 replace:
.{smartlet.name()}.primair textarea")} {
width: 98%;
height: 100px;
}
 
.{smartlet.name()}.primair input.text")} {
width: 98%;
}
 
with
.{smartlet.name()}.primair textarea {
width: 98%;
height: 100px;
}
 
.{smartlet.name()}.primair input.text {
width: 98%;
}

 
and replace:
/* posts */
.{smartlet.name()}.primair div.smlCommentSource")} {
background-image:none;
background-color:#525747;
color: #FFFFFF;
}
.{smartlet.name()}.primair span.smlCommentSource")} {
font-weight: bold;
font-size: 0.8em;
}
.{smartlet.name()}.primair span.smlStatus")} {
font-size: x-small;
font-style:italic;
}
 
.{smartlet.name()}.primair span.smlButtons")} {
font-size: x-small;
}
.{smartlet.name()}.primair div.smlCommentBody a")} {
text-decoration: underline;
}
 
.{smartlet.name()}.primair div.smlCommentBody a:hover")} {
text-decoration: none;
}
.{smartlet.name()}.primair div.smlCommentBody")} {
background-color: transparent;
background-image: none;
border: 2px solid #525747;
border-top:0px;
}
.{smartlet.name()}.primair span.smlButtons button")} {
background-color: transparent;
color: white;
border: 0;
font-size: x-small;
}
.{smartlet.name()}.primair div.smlInactive div.smlCommentBody")} {
border: 2px solid #ff6600;
border-top:0px;
background-color: #ffaa88;
}
 
.{smartlet.name()}.primair div.smlPreview > div.smlCommentBody")} {
border: 2px solid #aaeeaa;
border-top:0px;
background-color: #aaffaa;
}
.{smartlet.name()}.primair div.smlEditHistory")} {
color:#DDDDDD;
font-size: 80%;
}
.{smartlet.name()}.primair span.smlWarning")} {
color: red;
white-space: nowrap;
}
.{smartlet.name()}.primair div.fieldset")} {
border-top: 1px dashed;
border-bottom: 1px dashed;
}
.{smartlet.name()}.primair a.smlTogShow")} {
background-image: url(/res/plusicon.gif);
background-repeat: no-repeat;
}
.{smartlet.name()}.primair a.smlTogHide")} {
background-image: url(/res/minusicon.gif);
background-repeat: no-repeat;
}

 
with:
/* posts */
.{smartlet.name()}.primair div.smlCommentSource {
background-image:none;
background-color:#525747;
color: #FFFFFF;
}
.{smartlet.name()}.primair span.smlCommentSource {
font-weight: bold;
font-size: 0.8em;
}
.{smartlet.name()}.primair span.smlStatus {
font-size: x-small;
font-style:italic;
}
 
.{smartlet.name()}.primair span.smlButtons {
font-size: x-small;
}
.{smartlet.name()}.primair div.smlCommentBody a {
text-decoration: underline;
}
 
.{smartlet.name()}.primair div.smlCommentBody a:hover {
text-decoration: none;
}
.{smartlet.name()}.primair div.smlCommentBody {
background-color: transparent;
background-image: none;
border: 2px solid #525747;
border-top:0px;
}
.{smartlet.name()}.primair span.smlButtons button {
background-color: transparent;
color: white;
border: 0;
font-size: x-small;
}
.{smartlet.name()}.primair div.smlInactive div.smlCommentBody {
border: 2px solid #ff6600;
border-top:0px;
background-color: #ffaa88;
}
 
.{smartlet.name()}.primair div.smlPreview > div.smlCommentBody {
border: 2px solid #aaeeaa;
border-top:0px;
background-color: #aaffaa;
}
.{smartlet.name()}.primair div.smlEditHistory {
color:#DDDDDD;
font-size: 80%;
}
.{smartlet.name()}.primair span.smlWarning {
color: red;
white-space: nowrap;
}
.{smartlet.name()}.primair div.fieldset {
border-top: 1px dashed;
border-bottom: 1px dashed;
}
.{smartlet.name()}.primair a.smlTogShow {
background-image: url(/res/plusicon.gif);
background-repeat: no-repeat;
}
.{smartlet.name()}.primair a.smlTogHide {
background-image: url(/res/minusicon.gif);
background-repeat: no-repeat;
}

 
CSS item GUID-0DC6BD53564A4783A6ADBEFA0578E637 replace:
.{smartlet.name()}.nature textarea")} {
width: 98%;
height: 100px;
}
 
.{smartlet.name()}.nature input.text")} {
width: 98%;
}
 
with:
 
.{smartlet.name()}.nature textarea {
width: 98%;
height: 100px;
}
 
.{smartlet.name()}.nature input.text {
width: 98%;
}
 
And replace:
 
/* posts */
.{smartlet.name()}.nature div.smlCommentSource")} {
background-image:none;
background-color:#73654C;
color: #FFFFFF;
}
.{smartlet.name()}.nature span.smlCommentSource")} {
font-weight: bold;
font-size: 0.8em;
}
.{smartlet.name()}.nature span.smlStatus")} {
font-size: x-small;
font-style:italic;
}
 
.{smartlet.name()}.nature span.smlButtons")} {
font-size: x-small;
}
.{smartlet.name()}.nature div.smlCommentBody a")} {
text-decoration: underline;
}
 
.{smartlet.name()}.nature div.smlCommentBody a:hover")} {
text-decoration: none;
}
.{smartlet.name()}.nature div.smlCommentBody")} {
background-color: transparent;
background-image: none;
border: 2px solid #73654C;
border-top:0px;
}
.{smartlet.name()}.nature span.smlButtons button")} {
background-color: transparent;
color: white;
border: 0;
font-size: x-small;
}
.{smartlet.name()}.nature div.smlInactive div.smlCommentBody")} {
border: 2px solid #ff6600;
border-top:0px;
background-color: #ffaa88;
}
 
.{smartlet.name()}.nature div.smlPreview > div.smlCommentBody")} {
border: 2px solid #aaeeaa;
border-top:0px;
background-color: #aaffaa;
}
.{smartlet.name()}.nature div.smlEditHistory")} {
color:#666666;
font-size: 80%;
}
.{smartlet.name()}.nature span.smlWarning")} {
color: red;
white-space: nowrap;
}
.{smartlet.name()}.nature div.fieldset")} {
border-top: 1px dashed;
border-bottom: 1px dashed;
}
.{smartlet.name()}.nature a.smlTogShow")} {
background-image: url(/res/plusicon.gif);
background-repeat: no-repeat;
}
.{smartlet.name()}.nature a.smlTogHide")} {
background-image: url(/res/minusicon.gif);
background-repeat: no-repeat;
}

 
with:
 
/* posts */
.{smartlet.name()}.nature div.smlCommentSource {
background-image:none;
background-color:#73654C;
color: #FFFFFF;
}
.{smartlet.name()}.nature span.smlCommentSource {
font-weight: bold;
font-size: 0.8em;
}
.{smartlet.name()}.nature span.smlStatus {
font-size: x-small;
font-style:italic;
}
 
.{smartlet.name()}.nature span.smlButtons {
font-size: x-small;
}
.{smartlet.name()}.nature div.smlCommentBody a {
text-decoration: underline;
}
 
.{smartlet.name()}.nature div.smlCommentBody a:hover {
text-decoration: none;
}
.{smartlet.name()}.nature div.smlCommentBody {
background-color: transparent;
background-image: none;
border: 2px solid #73654C;
border-top:0px;
}
.{smartlet.name()}.nature span.smlButtons button {
background-color: transparent;
color: white;
border: 0;
font-size: x-small;
}
.{smartlet.name()}.nature div.smlInactive div.smlCommentBody {
border: 2px solid #ff6600;
border-top:0px;
background-color: #ffaa88;
}
 
.{smartlet.name()}.nature div.smlPreview > div.smlCommentBody {
border: 2px solid #aaeeaa;
border-top:0px;
background-color: #aaffaa;
}
.{smartlet.name()}.nature div.smlEditHistory {
color:#666666;
font-size: 80%;
}
.{smartlet.name()}.nature span.smlWarning {
color: red;
white-space: nowrap;
}
.{smartlet.name()}.nature div.fieldset {
border-top: 1px dashed;
border-bottom: 1px dashed;
}
.{smartlet.name()}.nature a.smlTogShow {
background-image: url(/res/plusicon.gif);
background-repeat: no-repeat;
}
.{smartlet.name()}.nature a.smlTogHide {
background-image: url(/res/minusicon.gif);
background-repeat: no-repeat;
}

 
27. Item GUID-02400AB5355F4E408B344117C8D07400 replace:
<label for="{smartlet.id(editorNote)}" style="display: {sys.iif(smartlet.get(editComment)==0,none,inline)}">Note</label>
<input type="text" class="text" id="{smartlet.id(editorNote)}" name="{smartlet.id(editorNote)}" value="{smartlet.get(editorNote,default='')}" style="display: {sys.iif(smartlet.get(editComment)==0,none,inline)}"/>

with:
<label for="{smartlet.id(editorNote)}" class="{sys.iif(smartlet.get(editComment)==0,buttonSubmitHide,visible)}">Note</label>
<input type="text" id="{smartlet.id(editorNote)}" class="text {sys.iif(smartlet.get(editComment)==0,buttonSubmitHide,visible)}" name="{smartlet.id(editorNote)}" value="{smartlet.get(editorNote,default='')}" />

 
In item GUID-4397D83E16704FF9AA01AB3D04717CA3 replace;
<label for="{smartlet.id(editorNote)}" class="{sys.iif(smartlet.get(editComment)==0,hide,inline)}">{locale.translate(Note)}</label>
<input type="text" id="{smartlet.id(editorNote)}" class="text {sys.iif(smartlet.get(editComment)==0,buttonSubmitHide,visible)}" name="{smartlet.id(editorNote)}" value="{smartlet.get(editorNote,default='')}" />

with:
<label for="{smartlet.id(editorNote)}" class="{sys.iif(smartlet.get(editComment)==0,buttonSubmitHide,visible)}">{locale.translate(Note)}</label>
<input type="text" id="{smartlet.id(editorNote)}" class="text {sys.iif(smartlet.get(editComment)==0,buttonSubmitHide,visible)}" name="{smartlet.id(editorNote)}" value="{smartlet.get(editorNote,default='')}" />

 
One could also add the .buttonSubmitHide directive to the css.
 
28. In item GUID-177CCDBC84C74F0E9B5127172AAC9850 remove:
@import '{html.location(FRAMEWORK_CSS)}';

 
29. In item SI_FS_CSS remove:
@import '{html.location(FRAMEWORK_CSS)}';

 
30. In item SI_FS_SKIN replace:
.ui-menu-item {
text-align: left;
white-space: no-wrap;
}

 
with:
.ui-menu-item {
text-align: left;
white-space: nowrap;
}

 
31. SmartInstant 2.0 grid rows can now render their most important column first.
This is a requirement for Webrichtlijnen. Simply mark the column containing the page content as "ContentKolom" in the Grid Row Chooser and it will be rendered first in the html. 
CSS is used to place the column at the right position visually.
To add this behaviour to an existing SmartInstant 2.0 site, add a field ContentColumn to all content types in the Grid Row group. 
Set ctrl:visible to false, because it will be updated by the Grid Row Chooser. 
Update item GridRowLogic() to:
{buffer.set(rowid, translation.caller())}
{buffer.set(attributes, string.format('class="{0}"',html.combinecssclasses(html.combinecssclasses(gridrow, sys.iif(itemdata.field(equalheight,$rowid),'si_equalheight'),itemdata.field(class,$rowid)))))}
{buffer.set(rowcode, string.tolower(cms.getitemcode($rowid)))}
 
{buffer.set(rowidtext, string.tolower(itemdata.field(id,$rowid)))}
<se:if expression="(buffer.exists(rowidtext)) AND (string.length($rowidtext) != 0)">
{buffer.set(attributes, $attributes + string.format(' id="{0}"', $rowidtext))}
</se:if>
 
<se:if expression="!(itemdata.rawfield('gridspan1',$rowid,Off)==16 AND itemdata.rawfield('column1',$rowid,Off)=='')">
{buffer.set(maincol, itemdata.field(ContentColumn,$rowid,Off, default=0))}
<se:if expression="$maincol GT 1 AND $maincol LT 9">
{buffer.set(mainspan, itemdata.field(string.concat(gridspan,$maincol),$rowid,Off))}
</se:if>
<se:if expression="buffer.get(mainspan, default=0) != 0">
<se:then>
{buffer.set(pushoffset, 0)}
<se:for from="1" to="{sys.eval(buffer.get(maincol) - 1)}">
{buffer.set(pushoffset, $pushoffset + itemdata.field(string.concat(gridspan,this.index()),$rowid,Off))}
</se:for>
<se:buffer name="mainresult">
<div class="{html.combinecssclasses(string.concat('grid_', $mainspan), string.concat('push_', $pushoffset))}">
{itemdata.field(string.concat('column',$maincol),$rowid,Off)}
</div>
</se:buffer>
<se:for from="1" to="{sys.eval(buffer.get(maincol) - 1)}" save="beforeresult">
{buffer.set(index, this.index())}
{buffer.set(gridspan, itemdata.field(string.concat(gridspan,$index),$rowid,Off))}
{buffer.set(lastgrid, sys.iif($index+1 == $maincol AND itemdata.rawfield(string.concat(gridspan,math.min(8,$maincol+1)),$rowid,Off)==0,'lastgrid',''))}
<se:if expression="$gridspan GT 0">
<se:then>
<div class="{html.combinecssclasses(string.concat('grid_', $gridspan), string.concat('pull_', $mainspan), $lastgrid)}">
{itemdata.field(string.concat('column',$index),$rowid,Off)}
</div>
</se:then>
<se:else>{this.parent.break()}</se:else>
</se:if>
</se:for>
<se:for from="{sys.eval(buffer.get(maincol) + 1)}" to="8" save="afterresult">
{buffer.set(index, this.index())}
{buffer.set(gridspan, itemdata.field(string.concat(gridspan,$index),$rowid,Off))}
{buffer.set(lastgrid, sys.iif(itemdata.rawfield(string.concat(gridspan,math.min(8,$index+1)),$rowid,Off)==0||$index==8,'lastgrid',''))}
<se:if expression="$gridspan GT 0">
<se:then>
<div class="{html.combinecssclasses(string.concat('grid_', $gridspan), $lastgrid)}">
{itemdata.field(string.concat('column',$index),$rowid,Off)}
</div>
</se:then>
<se:else>{this.parent.break()}</se:else>
</se:if>
</se:for>
 
{buffer.set(result, $mainresult + $beforeresult + $afterresult)}
</se:then>
<se:else>
<se:for from="1" to="8" save="result">
{buffer.set(index, this.index())}
{buffer.set(gridspan, itemdata.field(string.concat(gridspan,$index),$rowid,Off))}
{buffer.set(lastgrid, sys.iif(itemdata.rawfield(string.concat(gridspan,math.min(8,$index+1)),$rowid,Off)==0||$index==8,'lastgrid',''))}
<se:if expression="$gridspan GT 0">
<se:then>
<div class="{html.combinecssclasses(string.concat('grid_', $gridspan), $lastgrid)}">
{itemdata.field(string.concat('column',$index),$rowid,Off)}
</div>
</se:then>
<se:else>{this.parent.break()}</se:else>
</se:if>
</se:for>
</se:else>
</se:if>
{buffer.set(result,$result + html.div("",'class="cleargrid"'))}
{translation.setresult(html.div($result, $attributes))}
</se:if>
 
 
 
and update item GRIDROW_COLUMN_CHOOSER to:
 
<![CDATA[
<style type="text/css">
#grm_row{
width: 100%;
height: 100px;
border: 1px solid #808080;
position: relative;
background-color: #f4f4f4;
}
#gridmanager{
width: 100%;
position: relative;
}
#grmelding{
position: absolute;
top: 0;
left: 0;
width: 100%;
height: 100px;
padding: 7px;
border: 1px solid #000000;
background-color: #ff0000;
color: #ffffff;
text-align: center;
display: none;
}
#grmelding span{
display: block;
padding-bottom: 10px;
}
#grmelding .closemelding{
display: inline-block;
border: 1px solid #000000;
background-color: #808080;
color: #ffffff;
font-weight: bold;
line-height: 1em;
padding: 3px 5px;
text-align: center;
text-decoration: none;
}
#grm_row table{
width: 100%;
height: 100%;
}
#grm_row table td{
border: 2px solid #EEEEEE;
padding: 0px;
background-color: #ffffff;
}
.grm_col{
display: block;
height: 92px;
width: 6.25%;
background-color: #f1f6f9;
background-image: url(/scf/gfx/box/boxmanagerback.jpg);
background-position: bottom;
background-repeat: repeat-x;
position: absolute;
top: 3px;
left: 0;
border: 1px solid #000000;
font-size: 0.8em;
}
.grm_colpad{
padding: 20px 2px;
overflow: hidden;
}
a.colb{
display: inline-block;
border: 1px solid #000000;
background-color: #808080;
color: #ffffff;
font-weight: bold;
line-height: 1.2em;
width: 1.4em;
font-family: Verdana, Geneva, Arial, Helvetica, sans-serif;
text-align: center;
text-decoration: none;
position: absolute;
bottom: 2px;
left: 2px;
}
a.colb.colplus{
left: 17px;
}
a.colb.coldel{
left: auto;
bottom: auto;
right: 2px;
top: 2px;
}
.colname, .maincol{
display: block;
font-weight: bold;
}
#add_column{
margin-top: 5px;
}
.colb:hover{
background-color: #259fd1;
}
.grm_col:hover{
background-image: none;
cursor: pointer;
}
tr.hidden {
display:none;
}
</style>
<script type="text/javascript">
 
/* In registry: Manager/Includes should contain valid includes needed for this script */
 
var $si = jQuery.noConflict();
 
var grid = {awc:ctrl.gridcolumns}; // 16 of 12 cols-grid
var maxcols = 8; // maximaal aantal kolommen
var cols = 0; // aantal columns
var totalWidth = 0; // totale breedte in columns
var col1w = 100/grid;// breedte van 1 column 100/16 = 6.25%
var intId;
var contentColumnField;
 
function foutmelding(txt){
$si('#grmelding').show().find('span').html(txt);
}
 
function drawColumns(){
totalWidth = 0;
$si('tr[id*=CTSpecificText]').addClass('hidden');
 
for (var i=1;i<9;i++){
$si('input[id=CTSpecificInt'+i+']').attr('value',0);
}
 
$si('#grm_row .grm_col').each(function(x){
var width_cols = $si(this).data('width_cols');
$si(this).css('width',(width_cols*col1w)-0.5+'%');
$si(this).css('left',(totalWidth*col1w)+'%').css({marginLeft:'0.25%',marginRight:'0.25%'}).data('left_cols',totalWidth);
totalWidth = totalWidth + width_cols;
$si("#CTSpecificInt"+(x+1)).attr('value',width_cols);
$si('#CTSpecificText'+(x+1)+'_row').removeClass('hidden');
$si(this).attr('id','column'+(x+1));
$si('.colw', this).html('Width:'+width_cols);
$si('.colname', this).html('Col:'+(x+1));
});
}
 
function addColumn(w){
if (cols < maxcols){
if((totalWidth)<grid){
if(!w){wc=1;}else{wc=w};
$si('#grm_row').append('<div class="grm_col" id="col'+cols+'"><div class="grm_colpad"><span class="colname"></span><span class="colw"></span><a href="#" class="colb coldel">X</a><a href="#" class="colb colmin">-</a><a href="#" class="colb colplus">+</a></div></div>');
var newCol = $si('#col'+cols);
newCol.data('width_cols',wc).data('left_cols',totalWidth);
newCol.find('.colname').after('<span class="maincol"><label for="mainSelector_'+cols+'">Contentkolom</label><input type="radio" name="mainSelector" id="mainSelector_'+cols+'" value="'+(cols+1)+'" /></span>');
 
var mainSelector = newCol.find("#mainSelector_" + cols);
if (cols+1 == contentColumnField.val()) mainSelector.attr("checked","checked");
mainSelector.change(function(){
if(this.checked) contentColumnField.val(this.value);
});
 
cols = cols +1;
if(!w){drawColumns();}
} else {
foutmelding('Er is geen ruimte voor een nieuwe column. Verklein een andere kolom om ruimte te cre&euml;ren');
}
} else {
foutmelding('Het maximaal aantal kolommen is: '+ maxcols);
}
}
 
function deleteColumn(obj){
if(cols>1){
obj.remove();
cols = cols-1;
drawColumns();
} else{
foutmelding('Een rij moet minimaal 1 kolom bevatten');
}
}
 
function pluswidth(obj){
if((totalWidth)<grid){
var width_cols = obj.data('width_cols');
obj.data('width_cols',(width_cols+1));
drawColumns();
 
} else {
foutmelding('De maximale breedte is bereikt.');
}
}
 
function minwidth(obj){
var width_cols = obj.data('width_cols');
if (width_cols>1){
obj.css('width',((width_cols-1)*col1w)+'%').data('width_cols',(width_cols-1));
drawColumns();
}
}
 
function loadGrid(grids){
$si('#grm_row .grm_col').remove();
cols = 0;
contentColumnField = $si("#" + getContentTypeField("ContentColumn",0).p);
totalWidth = 0;
if(grids){
myArray = grids.split(",");
for ( i=0; i<maxcols; i++) {
if(myArray){addColumn(myArray/1);}
}
drawColumns();
} else {
if ($si('#CTSpecificInt1').attr('_value') !== undefined) {
return false;
} else {
 
for ( i=1; i<=maxcols; i++) {
 
var w = $si('#CTSpecificInt'+i).attr("value")/1;
if(w)
{
addColumn(w);
}
 
}
if (cols==0){
addColumn();
}
clearInterval(intId);
drawColumns();
}
}
return false;
}
 
$si(document).ready(function(){
 
$si('#Layout').css('height','');
 
$si('.colplus').live('click', function(){
pluswidth($si(this).parents('.grm_col'));
});
$si('.colmin').live('click', function(){
minwidth($si(this).parents('.grm_col'));
});
$si('.coldel').live('click', function(){
deleteColumn($si(this).parents('.grm_col'));
});
$si('.closemelding').click( function(){
$si('#grmelding').hide();
});
 
// maak grid tabel als achtergrond
$si('#grm_row').append('<table><tr></tr></table>');
for (i=0;i<grid;i++){
$si('#grm_row table tr').append('<td style="width:'+col1w+'%"></td>');
}
 
$si('.grm_col').live('click', function(){
var nr = $si(this).attr('id');
});
 
intId = setInterval(loadGrid,250);
 
});
</script>
<div id="gridmanager">
<div id="grm_row"></div>
<div id="grmelding"><span></span><a href="#" class="closemelding">OK</a></div>
</div>
<button id="add_column" class="cmd" onclick="addColumn()"><img class="" src="/res/new.gif" complete="complete"/>Kolom toevoegen</button>
 
<a href="" onclick="loadGrid('16');return false;">Laad 1 koloms grid</a>
<a href="" onclick="loadGrid('8,8');return false;">Laad 2 koloms grid</a>
<a href="" onclick="loadGrid('5,6,5');return false;">Laad 3 koloms grid</a>
<a href="" onclick="loadGrid('4,4,4,4');return false;">Laad 4 koloms grid</a>
]]>

This was not Web Guidelines compliant.

For installation in an existing site, download the update from the iXperion Market: http://bit.ly/nRNHoL

Friendly urls are shown instead of complex internal Smartlet links

In SmartInstant, the search box in the upper right corner uses the query string to pass the searchterm to the search engine.

This approach is not recommended by the The web guidelines (Webrichtlijnen).

To forward the search term using a form post instead of the query string, apply the following changes to an existing SmartInstant site:

1. In the Manager, jump to item preset_Header_Search() and edit the translation CustomFunction() in the same folder. Replace method="get" by method="post".
2. Edit item sml_FacetedSearch(). Duplicate this code block, present in the smartlet item:

   <se:case expression="!smartlet.hasclientvalues() AND request.query.exists(q)">
   	{smartlet.set(searchterm,request.query(q,true))}
   </se:case>

   In the copy, replace query by form (2x):

   <se:case expression="!smartlet.hasclientvalues() AND request.form.exists(q)">
   	{smartlet.set(searchterm,request.form(q,true))}
   </se:case>

3. Forms posts often cause 'Web page has expired' errors when using the browser back button. To avoid this, add the response.setmaxage() viper directly above the line thats adds the jQuery include:

   {response.setmaxage(0, rem="suppress 'web page has expired' errors when using form post")}
   {placeholder.addjavascriptinclude('/Scf/jQuery/jquery-ui.js',false, 90)}

Text retrieved by the Twitter Smartlet was not escaped for XHTML display.

SmartInstant sites created using the 1.4 setup will automatically be updated.

To implement the changes manually, make the following changes to the Format() translation:

{translation.localscope.expand(scope.format.field(text))}</span>
==>
{translation.localscope.expand(string.xmlencode(scope.format.field(text), Ampersand))}</span>

... and ...

<em>{scope.format.field(source)}</em>
==>
<em>{string.xmlencode(string.xmldecode(scope.format.field(source)), 'Ampersand,DoubleAmpersand')}</em>

Due to the inclusion of a stripped version of jQuery-ui.css, the dialogs shown when clicking on external links, gennerated by the BrowseAway Smartlet, had erroneous styling. This was fixed in work item 9684.

Web Guideline prescribe that table elements are decorated using the 'scope' attribute.

To implement the changes in an existing Web Toolkit install, open the BuildCalendar() translation, and:

- add scope="row" to each th element under the tr with class 'smlPanelHeader'

- add scope="col" to each th element under the tr with class 'DayNames'

- add scope="col" to each td element

The HTML did not conform to Web Guidelines.

SmartInstant installations and updates will have the changes necessary.

To update existing sites, download the updated Flickr Smartlet (3.0) from the iXperion Market: http://bit.ly/nZphP7.

The ItemComments Smartlet had some non-compliant HTML.

To update an existing implementation, open the sml_ItemComments() item, and search for:

<se:if expression="smartlet.testaccess(forumpost)">
	<se:then><h3>{locale.translate("Comments have been closed for this item.")}</h3></se:then>
	<se:else><h5>{locale.translate("You are not allowed to post here.")}</h5></se:else>
</se:if>

... and change it to:

<se:if expression="smartlet.testaccess(forumpost)">
	<se:then><div class="smlNotification">{locale.translate("Comments have been closed for this item.")}</div></se:then>
	<se:else><div class="smlNotification">{locale.translate("You are not allowed to post here.")}</div></se:else>
</se:if>
<div>
	<input type="submit" class="buttonSubmitHide"/>
</div>

Now, open the ClientData/Css Item, and add the following code at the bottom:

{smartlet.nameselector("div.smlNotification")} {
	font-size: 120%;
	font-weight: bold;
	color: #808080;
}

For compliance with webRichtlijnen, these directives have been moved to a style sheet in the head section.

To make smartlet 'Create Account' function properly, move item 'Security Extension Assembly' (GUID-C37163170E7C4966A31C88A30FFBC031) to a folder which is registered as a folder for virtual assemblies. In case of new implementations: SI_VIRTUALASSEMBLIES.

For more information refer to: http://docs.ixperion.smartsite.nl/doc/Add-On_Modules-SmartInstant/Manager-Action-Duplicate-Design.html.

It is now easier to debug Javascript and CSS includes by disabling the Include Aggregator and minification both in the TestSuite in the Debug menu and in the Smartsite.config file in the debug section by enabling the debug feature "DebugIncludes".

To fix this issue in an existing site:

• Open the SmartletConfig() translation in [Shared Configuration/Scf/Smartlet Helpers]
• Add the attribute [keydependencies="ch={channel.code()}"] to the se:cache element that is saved as "css"

Smartsite would detect the relation between the two items, without checking whether the channel is to be deleted as well.

This would result in an error if the smartlet being edited is not available in the default channel.

Previously, the feature only worked in CodeEditor (SXML) fields.

The full version of jQuery-UI.css stylesheet contains non 2.1, and thus non-web guidelines compliant CSS. In the previous release the original jQuery-ui.css was stripped and placed into the /scf/jquery/smoothness/ folder under the same name, but we have now decided to include the full, original version and add an adapted version under a new name, sms-jquery-ui.css. We use progressive enhancement to then reinstall some of the CSS3 functionality, using a sms-jquery-ui.js file.

The Empty Site now comes with both the original 1.8.2 jQuery-ui.css and the 2 files needed for Web Guidelines compliancy.

By default, the SmartInstant setup and the 1.4b3 publication update use the compliant version of jQuery-UI.

To implement the compliant versions in your own sites, make sure the original jQuery-ui.css is no longer referenced, and add the following SXML in your render templates:

<!--// customized jquery-ui - CSS2.1 compliant, stripped from unneeded stuff -->
<se:placeholder.addcssinclude url="/scf/jquery/smoothness/sms-jquery-ui.css" media="screen"/>
<!--// to keep compliancy but enable newer CSS rules -->
<se:placeholder.addjavascriptinclude url="/scf/jquery/smoothness/sms-jquery-ui.js" />

The Includes Aggregator is now able to parse the aggregated CSS and process @import statements.

@import statements can either be moved to the top of the document, or be 'expanded' in place.

Steps needed to enable Import Processing:

Open the Shared /Configuration/Scf/Includes Aggregator/MergeIncludes(dataTable, type, minify) translation

Search for:

<se:if expression="$isjavascript">

    {buffer.set(result, $result)}

</se:if>

Replace this fragment with:

<se:if expression="! $isjavascript">

    {buffer.set(result, scf.includes.processaggregatedcssimports($result, Expand))}

</se:if>

When using an argument index in translation.arg(), argument type checking was skipped.

The Design/Stylesheets folder, within a Smartinstant design, now includes a translation named StockColor(name). To initialize the stock color, invloke the translation, without parameters, from the Logic field. You can then use {stockcolor(name)} to apply a stock color value.

When request.transfer() was used to reroute the request to another location without a client roundtrip, the dependency dropdown list would not refresh.

The SXML Visualizer has been updated to have better SXML statement to HTML element connectivity.

This had been fixed in Faceted Search Smartlet/Clientdata/Script.

There now is a different set of includes for screen, print and pdf.

The content of translation ixs_RenderFormControls() has been updated.

The searchterm input now includes an additional attribute type="text" to comply with the Webrichtlijnen validation.

This has also been changed in SmartInstant which uses its own version of ixs_RenderFormControls().

De layout parameter for CSS includes is no longer needed. The include item itself can determine the current design using the channel.state.get() viper.

This had been implemented in the layout item and other items in the Desisgn\stylesheets folder.

The vipers placeholder.addaggregatedjavascriptinclude and placeholder.addaggregatedcssinclude have been deprecated. You should now use the original methods placeholder.addjavascriptinclude and placeholder.addcssinclude instead.

The new MapLinkUrls property of the Smartlet Macro makes the Smartlet.Link() viper generate friendly urls on pages that support UrlParameters. This is especially helpful in strict Web Guidelines envionments, where querystring parameters are not allowed on Urls.

This ensures that the browser cache is automatically refreshed whenever an aggregated CSS or Javascript include changes.

Examples:

<link rel="stylesheet" type="text/css" href="/1/Config/GlobalStyles.css?ts=2011-08-17T13:25:22" media="screen" />

Smi's behavior for measuring visitors has been changed. Previously a visitor was only measured on its first visit ever. If the visitor visited your site for the first time yesterday and comes back again today, it was not counted as a new visitor. This could lead to the situation where there were several pageviews but no visitors on a certain day because all visitors has already visited your site before. Because people found this confusing, the behavior was changed such that a visitor is counted as a new visitor if it is a new visitor on that day. You can switch back to the old behavior by sett the attribute "visitormode" to "continuous" on the element "visitors" under the element "logging" in the Smiserver.exe.config file. Documentation is located here: http://docs.ixperion.smartsite.nl/doc/iXperion/Installation_and_Configuration/Smartsite_Configuration_files/Configuration_Files_Reference/SmiServerexeconfig/SmiServerexeconfig-configuration/sites/site/site-logging/visitors/visitormode.html

You can add additional text to the title by adding the following statement to the logic field of an item:

{placeholder.add(headtitle, ' additional information')}

You can also replace the standard head title:

{placeholder.clear(headtitle)}
{placeholder.add(headtitle, 'replacement title')}
{placeholder.add(headtitle, ' replacement additional information')}

The MapLinkUrls property was introduced purely for Web Guidelines compliance while using the Smartlet.Link() Viper Method. This method normally generates a Url with QueryString variables, but when specifying MapLinkUrls="true" in the Smartlet, it will automatically use Url Parameters (if supported by the hosting item)

You can now more easily preview System Translations using the Preview Logic field.

The SwitchProviderOnSupportedDomainsList release setting has been added to the smartsite.config of the EmptySix site template.

See the article <releaseSettings> element for more information.

To update existing sites manually, update the links in the rowformat property in smlWeblog() that use the smartlet.link() viper to use channel.link() instead:

<a href="{channel.link(this.field(nr))}"> ... </a>

The previous version of the Config Editor only supported the configuration for just one Active Directory membership provider.

However, as of iXperion 1.4 build 3, it supports the configuration for multiple membership providers and it supports LDAP membership provider(s) as well.

Furthermore, the Config Editor now also makes it possible to edit/review release and debug settings. These settings are available in Advanced Mode.

The SmartInstant ELBA element javascripts() no longer includes an explicit reference to Design/Javascripts/script.js.

Instead, this javascript has been added to the global javascript include.

In complex remdertemplates, such as in SmartInstant, Post Persistance handling could fail, resulting in persisted form data not being available using request.form() vipers.

Javascript items marked with 'Add to Global Include', were not loaded during Smartlet Editor previews, causing javascript errors.

The Synchronizer object (used within e.g. the Outscaling EventSubscriber) does now checks its database connection regularly, and when there's a problem a new connection is established. This prevents the log file from being flooded with error messages.

Checkboxes such as in Faceted Search options selector were not styled correctly.

Using sys.eval() could break code, due to erroneous checking whether the deprecated sys.eval(code, sciope, fallbackscope) was used.

When importing a contenttype, either using the Import / Export ContentType wizard or the Paste button within the cms manager Manage ContentTypes action, the events raised during the import process were not "consumed" by the import process itself.

Therefore, after an import contenttype action, the Outscaling eventqueue was filled with many ContentTypes events.

Unfortunately, the Outscaling mechanism to detect duplicate events wasn't optimal as well. When having an Outscaling scenario of multiple cms server instances each having their own database, this resulted in Outscaling sending the changed contenttype (to its cms subscriber instances) as many times as there were ContentTypes events within the queue.

Both these issues has been addressed. The Import ContentTypes function now, by default, "consumes" all ContentTypes events raised during the import process and raises a single ContentTypes.AddContentType (when it's a new contenttype) or ContentTypes.Update (when it's an update) event after it has finished the import. And the Outscaling mechanism to detect duplicate events has been adjusted as well.

This increase is needed when using multi-domaining of which field FQDN (Fully qualified domain name) of the user is stored in AllUsers.LoginName.

The cms manager stores persistant data of users in so-called user.dat files.

The naming convention for these files used to be "<username>.dat" (e.g. "admin.dat"). This has been changed into "<userid>.dat" (e.g. "1.dat").

Existing files will be renamed automatically when an user logs in.

As of iXperion 1.4 build 4, the Asynchronous Import also supports a returnUrl to a site which uses (integrated) Windows Authentication.

To switch to Windows Autenthication you must specify the parameter "ReturnUrlUseWindowsAuthentication" within the import settings element of the webservice call.

Of course, the supplied credentials (ReturnUrlUsername and ReturnUrlPassword) must then represent an domain account.

See the article Asynchronous Import for more information.

If "Events" was a friendly name of an item, then the file "/Events/foo.html" could no longer be retrieved. This has now been fixed.

This would break communication between publication and cms in the manager.

The check implemented within the DataEditor meta xml file osDatasources.xml was too strict.

The onbeforesave script within the logic section has been adjusted to fix this.

To fix this issue within existing sites running 1.4 build 2 or 3, change the onbeforesave script to:

If Site.AdoHelper.Tables.Exists(data("code")) Then
    Err.Raise 20002, "Invalid code", Context.Locale("Datasource code shouldn't equal an existing tablename.")
Else
    If Not IsNull(key) Then
        If Site.AdoHelper.ExecuteScalar("select count(*) from osDatasources where code=? and not nr=?", data("code"), CLng(key)) > 0 Then
            Err.Raise 20002, "Invalid code", Context.Locale("Datasource code must be unique.")
        End If
    Else
        If Site.AdoHelper.ExecuteScalar("select count(*) from osDatasources where code=?", data("code")) > 0 Then
            Err.Raise 20002, "Invalid code", Context.Locale("Datasource code must be unique.")
        End If
    End If
End If

The Url Parameters feature now escapes and unescapes '.' characters in querystrings.

The digid.redirecttologin viper generates an url which includes the original source url as query-string viper.

The viper now also has overloads which will generate an Web Guidelines compliant url (sourceurl included as url parameter).

When you use one of the overloads of the digid.redirecttologin() viper with which you can specify the sourceUrl, the sourceUrl specified is now checked if it contains a valid Item reference. If not, the sourceUrl is not added to the url as querystring parameter (or url parameter when the option useUrlParameterMapping has been set to true).

The Outscaling background component does check the database connection every 20 seconds, and when doing so a standard log message ("Synchronizer object: Checking ado connection...") is written to the Smartsite log (on level 10).

In rare occasions, writing this log message causes the error ("Object variable or With block variable not set"), which is then written to the Windows Application log.

Notice that this doesn't affect the Outscaling process at all and/or logging other messages. The "only" downside is that the Windows Application log is flooded with the message: "Error while logging Outscaling\Synchronizer object: Checking ado connection...: Object variable or With block variable not set" (every 20 seconds).

To prevent this from happening, the logging of the procedure checking the ado connection has been adjusted. If the problem still occurs, adjust the Outscaling loglevel to a lower level (<10).

As part of fixing work item 8774 ("when saving an item within the cms manager, the item-cache of that item is now cleared immediately"), the ContentChange.Activation event has been added to the built-in event filtering of Outscaling.

This means that the ContentChange.Activation event was always skipped and never sent to another server instance.

This did cause problems when using an Outscaling configuration of multiple (cms+pub) server instances with a shared database. When changing an item on a cms server instance, the publication server instance(s) belonging to the other (subscribed) cms server instance(s) never received an event to indicate this change. Therefore, the item-cache wasn't cleared on the publication server instance(s).

This problem has been fixed, the ContentChange.Activation event has been removed from the built-in event filtering.

When the Outscaling background component thread is busy for over 5 minutes synchronizing a set of items, it could happen that the main Smartsite thread started a new Outscaling background component.

This is the AutoRestart behaviour, which is intended to make sure there's always an active Outscaling background component.

To prevent this from happening, various changes have been implemented:

- The AutoRestart interval (which represents the number of seconds between the last activity - represented by the LastRun property - and

the current date/time which must have been passed before a new background component will be started) can now be configured within the registry

(AutoRestartInterval string value within the "BackgroundComponents\Outscaling" key, defaults to 300).

- The LastRun property (which is used to determine if the Outscaling background component is still active) is now updated more often.

- The (internally used) LastActivationDate registered within osDatabaseInstances will now only be updated if the new value is greater than the old value.

Notice that the AutoRestart behaviour can be switched off by means of adding AutoRestart string value with value "0" to the "BackgroundComponents\Outscaling" key.

Due to a culture-related bug, the calendar macro could show wrong results.

To simplify problem detection, Smartsite now fails to start if it has insufficient permissions on the registry. Run SetSiteSecurity to resolve the problem if it occurs.

In previous versions, a lookuplist was represented as a datatable in normal render mode and as an integer or float in preview mode. This caused preview of such items to fail. With this fix, lookuplist fields are now represented as a datatable in both normal render and preview mode. Note that you may have implemented a workaround in your site for this problem. That workaround may need to be removed.

When renaming a logical fieldname on a master contenttype (using manage contenttypes), this change is reflected on the derived contenttypes as well.

However, in an Outscaling scenario, the master contenttype on the subscriber server instance was updated accordingly, but the derived contenttypes were not.

The field was actually been removed from the derived contenttypes. This has been fixed.

Also, when using an Outscaling scenario with a shared database, the affected contenttypes were not reloaded.

This bug only occurred when an item is updated by the import process, initial creation of the item worked correctly.

This would typically result in extra ampersand-escaping for these fields.

Repository workflows did not start under Active Directory because the Smartsite Middleware user does not exist under Active Directory. A new registry setting has been introduced that allows you to optionally set the user used for repository workflows. You can set the repository user by setting a username in the registry setting <site root>\CMS\Repository\WorkflowUser.

A bug was fixed where the Tabbed Preview component would fail, depending on the SubTree configuration of a channel.

When pulling was enabled, sometimes an item was pulled incorrectly due to the fact that the OriginitatorInstanceID field was reset to null between two updates.

Previously, the editor would remove everything after the ampersand.

Synchronizing an item selection without selecting the recursive option didn't work anymore.

When Internet Explorer has a CSS file in its cache, it doesn't always check the server to see if it has been modified since the file was cached. The cache will be refreshed on an uncertain schedule determined by the browser.

Clearing the client cache will result in the changes becoming visible in the editor.

A Smartsite XML import file can contain a hierarchy of items to import. A parent item usually includes a field stating that the item is a folder. If this field is omitted the importer will automatically assume a folder. This mechanism contained a flaw that occurred if the folder field is omitted and if the item is already present as an item rather than a folder. This is now fixed.

As a result, the AutoRestart option did mistakenly detect that the Outscaling background component wasn't active/running anymore and started a new instance.

This resulted in low(er) performance and various errors.

Now that Smi registers errors per page, you can zoom in a specifc error and see on which page it occurred.

Due to a logic error, some charts were not displaying all lines. The data displayed in the table below the chart was correct.

In previous releases, an Xml export always contained all rows available. From now on, an Xml export contains the number of rows configured in the report. You can still select 'all rows' if you want to retrieve all rows a specific report.

In the standard Faceted Search configuration, the initial sort order of the search result is always searchrank desc.

This is needed because, as long as the result with the highest searchrank is not known, a relative ranking indicator cannot be shown.

By making the changes to the Faceted Search smartlet as listed below, the initial search order can be overruled, and can, for example, be set to publication date.

{sml_facetedsearch(orderby="c.ActivationDate DESC")}

Note that, as long as the result has not been sorted by searchrank, the ranking indicator is not valid and will not be displayed.

item sml_FacetedSearch()

Replace
{smartlet.set(orderby,"searchrank DESC")}
with
{smartlet.set(orderby, smartlet.get(orderby,default="searchrank DESC") )} 

item ixs_ShowRating

Enclose existing img-tag with a condition test:
<se:if expression="translation.arg(mul,default=0) GT 0" trim="both">
  <img ... />
</se:if>

This caused problems when working with case-sensitive UNIX servers.

The urls will now be registered in the casing they have in the site.

To fix existing databases, you will have to do a full AIM rescan (with 'Remove all existing AIM data'), using the AIM tab in the System Panel action.

The scheduled events were not executed on the specified time, but they were executed 24 hours after the last time they had run.

The error could occur if many logins happened in a short amount of time, due to an object, not being disposed immediately.

When the search terms did contain one or more stopwords, the main search query gave the correct number of result due to the "exact phrase" condition (which is basically a concatenation of the search terms) which is always added to the full-text predicate.

However, the facets didn't show any result due to the fact that this "exact phrase" condition wasn't added to the full-text predicate in case of a facet query. This has been fixed.

Notice that this issue only applies when using full-text search.

When setting items inactive or archiving, aim references were kept intact, causing blocking relations.

A security issue was fixed in the Login macro. It no longer accepts any url as ReturnUrl parameter: it must point to a valid site HostHeader.

Because the image macro did not use the file cache when determining the width or height of a transformed image, the macro was performing the costly transform operation every time it was called.

When using the Sql.Execute() viper method instead of a full-fledged SqlQuery macro, the database connection would not be closed immediately after statement execution. This could cause the Database Connection Pool to be overflowed.

When isolating channels using the useglobalhostheaders="false" setting, previewing items on that channel in the Smartsite Manager, went wrong.

If a specific channel responds to a different hostheader than the default channel, the webeditor would often break internal links within that channel.

An error occurred when updating a content relation field using the bulk update action.

When using legacy forms, inputs of type checkbox did not return the correct value.

The SimpleN2N storage handler now better detects the appropriate n-2-n relation.

In some rare scenarios, when a SQL server database had been downgraded from SQL Server 2008 R2 to SQL Server 2008 R1, detecting the appropriate n-2-n relation did cause a problem.

This resulted in synchronization problems for channel and render template items.

Database view vwSchemaLookup was modified by some customers, as a workaround for an issue with N to N content relations. This issue was solved with a refinement of the involved storage handler. The modification of the view definition is no longer required and 1.4 build 8 restores the original definition.

When using seperate channel hostheaders, and useglobalhostheaders="false", you could not use a channel-specific LoginUrl.

When Smartsite has been configured to use a multi-domain Active Directory configuration, users not on the default domain were unable to save items: the content validation failed with the exception message "User not found in Active Directory store".

Notice, when using multi-domain configuration, you need to check if the release setting SwitchProviderOnSupportedDomainsList has been enabled.

The PublicationServerRequestInterval setting (root of the site registry) can be used to set the interval (in seconds) after which the CMS server will issue a 'keep-alive' request to the Publication Server.

The PublicationServerRequestUrl setting can be used to use an alternative url for the keep-alive request (the PublicationServerAddress setting will be used by default).

Use the ExecutePublicationServerRequestOnStartUp setting (boolean) to enable or disable the keep-alive.

The returnUrl send to DigiD didn't use the correct escaping/encoding.

Due to a fix within 1.4 build 6, which had to do with synchronization of a rename action on a contenttype field, adding a contenttype field was not synchronized correctly anymore. The new field was only added to the master contenttype and not its derived contenttypes.

This has been fixed, now both adding a contenttype field and renaming an existing contenttype field is correctly synchronized to the master contenttype and its derived contenttypes.

In some previous versions of Smartsite the SmartletEditorDefaultTypes() item contained the following source:

<se:rowformat expression="this.field(type)==Boolean">

<label for="{this.field(name)}">{string.capitalize(this.field(name))}</label>

<se:if expression="this.field(defaultvalue)">

<se:then><input type="checkbox" checked="checked" class="Control {this.parent.field(type)}Control" name="{this.parent.field(name)}" id="{this.parent.field(name)}" /><br /></se:then>

<se:else><input type="checkbox" class="Control {this.parent.field(type)}Control" name="{this.parent.field(name)}" id="{this.parent.field(name)}" /><br /></se:else>

</se:if>

</se:rowformat>

This se:if must have a this.parent.field.

New source should be:

<se:rowformat expression="this.field(type)==Boolean">

<label for="{this.field(name)}">{this.field(caption)}</label>

<input type="checkbox" se:attr="{sys.iif(this.field(defaultvalue)==true, html.attribute(checked,checked))}" class="Control {this.field(type)}Control" name="{this.field(name)}" id="{this.field(name)}" /><br />

</se:rowformat>

The se:webservice macro now supports specifying an endpoint configuration, using the endpointconfiguration parameter.

This can be useful in advanced scenarios, where you need to specify behaviorConfiguration.

When an EndpointConfiguration has been specified, the webservice macro will create the endpoint using this configuration, including the address property and any behavior- and binding configuration specified on this endpoint.

The contract attribute for this endpoint must be set to "System.ServiceModel.Channels.IRequestChannel".

The endpoint itself must have been configured within the web.config, within the system.serviceModel/client section.

Example:

<endpoint address="http://testsite/cms/manager.dws" binding="basicHttpBinding" bindingConfiguration="cmsWebserviceSoapBinding"

contract="System.ServiceModel.Channels.IRequestChannel" name="MyEndpoint"/>

Notice that when you specify an EndpointConfiguration, the Url and MaxReceivedMessageSize parameters must not be specified (an exception will be thrown if you do).

When the site has been configured to use Active Directory (or LDAP), scheduled activation of an item fails.

The error that occurs is: "User not found in Active Directory store."

This is due to the fact that the activation takes place in a background process, using the system account (Smartsite Middleware).

This account, of course, can not be found within the Active Directory.

To fix this issue, it is now supported to specify a domain account, which will then be used as the system account within Smartsite iXperion.

To do so, change the smartsiteaccounts section within Smartsite.Security.config:

    <smartsiteaccounts>
      <guest loginname="guest" />
      <system loginname="username@domain.name" />      
    </smartsiteaccounts>

Specify the FQDN (fully qualified domain name) of a domain account as the loginname for the system account.

Best practice is to specify the same account which has been configured for the Active Directory membership provider within the web.config.

This account must not already exist within AllUsers! If it does, for whatever reason, create/choose another domain account.

On the domain, make sure this account is a member of the Smartsite Manager Access Group.

Also, make sure that the specified "domain.name" is listed as valid domain within the membershipMappings element:

    <membershipMappings>
      <add name="mm1" domain="domain.name" providerName="ADMembershipProvider" />
      <add name="mm2" domain="domain.name.alternative" providerName="ADMembershipProvider" />
    </membershipMappings>

The system user entry within AllUsers (the account with Nr = -99) will be updated automatically when the site has been restarted.

(It will also be reverted back to "System" automatically, when the loginname is changed back to "System" or any other account which does not represent a FQDN.)

The start page in de manager shows a list of recent edits, filtered given the current user. For large sites building-up this list could take a substantial amount of time. This has been optimized.

Smartsite iXperion now comes with Dutch Cookie Law adherence tooling. See http://docs.ixperion.smartsite.nl/doc/iXperion/Add-On_Modules/Enforcing-Cookie-Policies.html

Content type Channel is extended with field indicating whether the support for the cookie policy should be enabled. The support is disabled by default.

When changing the password format (Advanced Mode) from Clear to Hashed, the Config Editor does check if it is necessary to update the passwords within the database to a hashed version.

When that's the case, the update did fail due to a bug within a sql statement. This has been fixed.

Because the json was rendered inside a script tag in the head section of the page, a closing script tag inside a string property would break the page. In Internet Explorer this even happens if all the code within the script element is placed inside a CDATA block.

To alleviate this problem, the string "</script>" in the json output of a smartlet will be replaced by "<\/script>" and "]]>" by "\]\]>".

When using json objects directly, the developer is responsible for escaping these strings.

Notice this only occured when only guest access was set on the item priorly, which was then removed and no other content access for any other group was set.

This problem occurred when using the following Outscaling scenario:

- two Cms Server Instances (CMS1 and CMS2)

- two Publication Instances (PUB1 and PUB2)

- all of them using a shared database

- CMS1 does have two subscribers: CMS2 and PUB1

- CMS2 does have one subscriber: PUB2.

When changing the access rights for a specific item on the CMS1 server instance, the PUB2 instance wasn't notified of this change.

Under specific load, a situation could occur where database connection of different threads were mixed up, leading to unpredictable results.

This redesigned dialog does not only display the activation dates, but can now be used to actually synchronize out-of-date items to cms subscriber instances.

Within the database setup/update scripts, it is common that some records are added or changed, such as contenttypes, contenttype field properties, access type levels, etc.

When these database scripts are executed on an Outscaling subscriber instance, these changes are skipped, since it is the responsibility of the Outscaling publisher instance to push these changes to its subscribers.

However, the database scripts, when run on the Outscaling publisher instance, did not detect the appropriate publisher instance.

Therefore, the required Outscaling events were generated, but for the wrong instance.

As a result, Outscaling skipped the events, because the Originator of the events did not match with the local server instance's ID.

This has been fixed.

When a synchronization or import error did occur, the registration of this error was removed when retrying failed items.

Now, the error registration is kept within the "Database Sync Errors" subaction of the Outscaling Console and the retry count is increased by one when retrying a failed item.

After a while, when on the remote server instance there's no longer an error indication for a specific item, the local copy of the error for that item is removed.

This could happen when within the same time-interval of a background loop of the Outscaling Background component, one or more items have been adjusted and saved to an Active state and at least one item has been Deleted.

The Outscaling Background component did use two separate queries to determine which items needs to be synchronized:

- The first query to determine which items have been deleted since the last synchronization loop.

- The second query to determine which (other) items have been adjusted since the last synchronization loop.

The date-input for the second query was wrong. This was especially noticeable when the interval of the Outscaling Background component was set to a higher value (5 seconds or more).

To fix this problem, the process of synchronizing items has been redesigned:

- To determine which items needs to be synchronized, now a single query is used.

- For each item that needs to be synchronized, now a new and specific Outscaling event (Outscaling.SynchronizeSingleItem) is directly added to the Outscaling queue.

- Therefore, the recordset can be processed much faster, so it's no longer needed to limit the number of items processed within a background loop.

- The fact that events are added to the Outscaling queue to synchronize items gives more insight into which items will be / have been synchronized.

The publication update scripts distinguish whether updating the master database or a subscriber database, when in outscaling scenarios. Logic is added to the update for the cookie policy support in order to correctly handle the scenarios with and without outscaling.

Cookie usage policies without a reference to a cookie usage application were not listed in the Cookie Policy Manager action of the Manager. This is fixed. Also these usage policies were not porperly outscaled. This is also fixed.

The publication update scripts distinguish whether updating the master database or a subscriber database, when in outscaling scenarios. Logic is added to the update for the cookie policy support in order to correctly handle the scenarios with and without outscaling.

A new database function fn_RecurseAllChildren has been added, supporting to recurse all items, including deleted items. The performance of the function has been improved. The existing function fn_RecurseChildren is updated with the improved implementation. The table returned by the existing function now more columns, in addition to the existing columns which remain unaltered.

A new action is made available for Outscaling, allowing to check the outscaling status of a file. A new privilege grants or denies access to an Outscaling tab with details.

Column "Object / Key" on the event queue tab of the Outscaling console now shows information in more event type cases.