SiteEdit issues fixed in the SDL Tridion 2011 SP1 user interface update

This topic lists issues that were present in SiteEdit 2009 SP3 that are fixed in the user interface update for SDL Tridion 2011 SP1 (now called Experience Manager).

Component that contained an empty, mandatory Format Area could be saved without raising an error

If a user attempted to save a Component that contained a Format Area that was mandatory in the corresponding Schema, then the save operation did not fail in some browsers, because the browser kept an empty tag (such as a <br/> element) in the field.

Could not publish a Page if another user has it checked out

If another user had checked out a Page anywhere, you could not publish that Page from the editable Web page.

Nested Component Presentations

On an editable Web page, a nested Component Presentation was displayed as a removed Component.

Using an alternative BluePrint context could cause crashing behavior

Some reports of browser and even computers crashing due to the configuration of an alternative BluePrint context in SiteEdit were reported in the past. The new user interface no longer crashes if you configure an alternaitve BluePrint context.

Creating a page from preview opened a browser window with nonexistent URL

In SiteEdit, creating a new page from the preview area in Content Manager Explorer would open a new browser window and show a 404 message. This is no longer the case if you use the new user interface.

Uploading a binary yielded an error message about metadata even if metadata was optional

In SiteEdit, if you uploaded a binary file and your default Multimedia Schema had only optional metadata fields, you would still see a message "Unable to find metadata". This error can no longer occur.

Unusable controls were enabled in SiteEdit

In SiteEdit, controls that should have been disabled based on the user's security clearance were displayed as enabled. This is no longer the case.

Changes to items in Content Manager Explorer would require a refresh in SiteEdit

If, for example, an items was unlocalized in Content Manager Explorer, SiteEdit would continue displaying it as a localized item, but show an error if the user tried to edit it. Now, the item list is refreshed every 10 seconds, making this kind of scenario very unlikely, and the need to refresh no longer exists.

SiteEdit could produce unpredictable results if SiteEdit configuration referred to nonexistent items

In SiteEdit, conceivably, the SiteEdit configuration in SiteEdit_conf.xml could create problems if it contained the Content Manager URI of an item that no longer existed (or never existed). This is no longer possible: the new user interface no longer lists Content Manager URIs in a configuration file (and ignores the ones listed in old SiteEdit configuration files).

Category security

Inline editing allowed users to add a Keyword even if they did not have Category Management rights for that Category.