Issues resolved in SDL Web 8
A list of issues that were resolved in SDL Web 8
Content Manager
- Installing Content Manager Publisher as a standalone module did not install a prerequisite automatically
-
In an outscale scenario, you may choose to install the Publisher of Content Manager as a standalone item on its own dedicated machine. The Publisher has Microsoft Visual C++ 2010 Redistributable SP1 (x64) as a prerequisite. If that prerequisite was not present on the target system, the installer should install it for you, but it did not. As a result, the Publisher could not start successfully on the machine, and your installer would show an error to that effect.
Microsoft Visual C++ 2010 Redistributable SP1 (x64) is now automatically installed on your target system if it is not yet already present on your target system.
Content Manager Explorer
- Uploading multimedia files of a type not listed in the default Multimedia types
-
If you attempted to upload a binary file of a type that was not listed among the default Multimedia Types, even if the file extension was added, the upload would fail. This problem is no longer reproducible in SDL Web 8.
- Target Groups did not appear as Processed Items in a Publish Transaction view
-
As of SDL Tridion 2013 SP1 HR1, Target Groups that have a Context Expression tab can be published. However, if you performed such a publish and then selected Publishing Queue, the Publish Transaction dialog that opened would not show the Target Group in its Processed Items tab, even though the Target Group was published. This issue is now resolved.
- When using an Embedded Schema with a Keyword/Category list field, the default value was not applied to the second and further values added to a Component created with the Schema
-
In SDL Tridion 2013 SP1 HR1, an issue was discovered: the default value set for a multivalue field of a Component was not applied to any values but the first value. In SDL Tridion 2013 SP1 HR1, Hotfix 88281 fixed this problem in the majority of cases, but the issue remained in one specific scenario: when creating a Component based on an Embedded Schema with a Keyword/Category list field. This issue is now also resolved.
Context Engine
- Context Engine Cartridge CEL expressions now support Unicode
-
The Context Engine Cartridge could not evaluate an expression written using Unicode characters. This issue is now resolved.
Experience Manager
- Name for newly created Component did not appear until after Workflow Process ended
-
If a user created a new Component in Experience Manager (using cloning) and if that creation triggered a Workflow Process, the name that the user gave to the Component would 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 would continue until the Workflow Process ended. This issue is now resolved.
- When using Internet Explorer 11, clicking anywhere in an inline editable field made the cursor appear at the beginning of that field
-
If a user used Internet Explorer 11 and attempted to place the cursor anywhere in an editable field on the Web page, the cursor appeared at the beginning of that field. This is no longer the case.
Device Preview
- After upgrading, icons were missing from the Devices view
- After upgrading to SDL Tridion 2013 SP1, the Devices view would show no icons for specific devices. This issue was resolved and no longer occurs when upgrading to SDL Web 8.
Audience Manager and Outbound E-mail
- There is no longer a maximum length of 255 characters for Extended Detail fields
-
An issue has been resolved where saving a Contact with data exceeding 255 characters resulted in a database exception.
- You can delete Content Manager items that are in use by Audience Manager and Outbound E-mail
-
In previous versions, you were able to delete Content Manager items that were used by Audience Manager or Outbound E-mail. This is no longer possible - you will receive an error message stating that the item is in use. Additionally, you can now see which items are using the item you want to delete by using the Where Used functionality.
- Unable to create a custom WCF binding for Audience Manager
-
It is once again possible to create a custom binding for Audience Manager's connection to the Core Service. Specify the name of the binding you want to use in OutboundEmail.xml.
Translation Manager
- Authorization Required column was present when SDL WorldServer was configured
-
If SDL WorldServer was configured, the Authorization Required column appeared even though it should not be visible in the user interface for Translation source configuration and Translation target configuration sections.
- A Javascript error was thrown in Internet Explorer 9 and 10 when sorting on To-From
-
In Internet Explorer 9 and 10, when you added an item to an existing job, in the dialog that opened a Javascript error was thrown when you tried to sort entries by clicking the From/to column.