Documentation Center

Known issues in Experience Manager

The following list describes issues that are known to exist in Experience Manager.

When using Internet Explorer 11, clicking anywhere in an inline editable field makes the cursor appear at the beginning of that field

If a user uses Internet Explorer 11 and attempts to place the cursor anywhere in an editable field on the Web page, the cursor appears at the beginning of that field.

To work around this problem, the use of a different browser is recommended.

Name for newly created Component does not appear until after Workflow Process ends

If a user creates a new Component in Experience Manager (using cloning) and if that creation triggers a Workflow Process, the name that the user gives to the Component will not yet appear in every part of Content Manager Explorer and Experience Manager. Instead, a user would see the name of the original Component that was cloned (made unique if necessary). This situation continues until the Workflow Process ends.

For example, let's say a user creates a new Component in a Folder Building Blocks\Foo\, based on the original Component called 'Dolly', which is located in the Folder Building Blocks\Foo\ as well. Even though the user gives the new Component a name 'My Report 2015', a user looking at the contents of Building Blocks\Foo\ sees a Component called 'Copy of Dolly' until the Component finishes its Workflow Process.

Under certain conditions, placeholders for optional fields may disappear

In SDL Tridion 2013 SP1, an issue was discovered: an update preview could result in the disappearance of optional fields. In SDL Tridion 2013 SP1 HR1, Hotfix 87889 fixed this problem in some, but not all cases.

If you encounter this problem, you can work around it by clicking on the page in the breadcrumb, and then clicking on another field value.