Resolved issues in SDL Tridion 2013
A list of issues that were resolved in the SDL Tridion 2013 release.
Content Manager
- Slow performance for non-admin users
- Logging in, listing folder contents etc took noticeably longer for non-admin users than for admin users. This performance problem was fixed.
- Updated of an item subject to workflow listed as done by NT AUTHORITY\SYSTEM
-
When a user updated an item that was workflow-enabled, its updates would appear in the item's Version History as performed by
NT AUTHORITY\SYSTEM. Now, the user is displayed. - Custom Resolver could result in exception "Object reference not set to an instance of an object"
- This problem with custom Resolvers was fixed.
- Logging an error larger than a 16-bit integer failed
- Logging an error of the indicated size could throw an exception and even stop the Core Service. This was fixed.
- Thumbnail of binary in Multimedia Component was corrupted if the Multimedia Component entered a Workflow Process
- This issue no longer occurs.
Content Manager Explorer
- A hyperlink in a bullet in a Format Area resulted in wrong HTML
-
The
<a href=...>element was placed before the<ul>element. This is now fixed. - Large, complex, nested Taxonomy may cause Go To Location control to fail
- The Go To Location button in search results now works as expected.
- Search scope was set to All Publication if you navigate too far down a Category tree
- Now the scope is set correctly.
- Pasting text from Microsoft Word in Firefox would include Word's XML comments
-
This would cause strings like
<!-- [if gte mso 9] -->to appear in the Format Area. This now no longer happens. - Items To Publish list erroneously claims Dynamic Component Presentations will be unpublished as part of a Page unpublish
- Only the Page actually gets unpublished, but Content Manager Explorer was still displaying wrong information. This is now fixed.
- Unwanted spaces were added to a Format Area containing only a bullet list
- Also, highligthing the list showed the selected element to be 'Text Selection'. This issue was fixed.
- Needed to explicitly select an image to see its properties
- Placing your cursor next to the image and selecting Image would open a dialog for a new image. This is now fixed.
- Internet Explorer displayed 'NaN' for certain date ranges
- In certain situations Internet Explorer would display the text NaN (not a number) for date ranges. This is now resolved.
- Scheduled For Publish items did not always appear correctly in the Publishing Queue
- Issue resolved.
- Reordering embedded Format Area fields would cause Format Area to become empty
- This issue was fixed.
- Description of localized Schema could not always be changed
- All types of Schemas can now have their descriptions changed, whether they are localized or not.
Experience Manager
- 'Enable for inline editing' check box in Page Templates
- Before this release, this check box would enable or disable Experience Manager functionality, not just for the Page objects being rendered by the Page Template, but also for all Components listed for the Page. This was not correct behavior. Now, this check box only affects the Page object itself (that is, Page metadata and the adding, moving or removing of Component Presentations).
Translation Manager
- Add Items list in Translation Job was not sortable or resizable
- List was made sortable and resizable.
Content Delivery
- Deployment fails: unable to unzip
- Deployment would sometimes fail with the message 'Unable to unzip', 'The system cannot find the file specified'. This is now fixed.
- Monitoring returns 'Not Responding' for an active Cache Channel Service
- Monitoring would erroneously report that the Cache Channel Service was not responding when it was in fact up and running. This is now fixed.
- Publish transaction details could show 'Ready for Transport' for an item that had already been transported
- In certain cases, this wrong information could appear, now it no longer does.
- Content Delivery Web service did not handle OData standard dateTime properly
- Date-time filters were implemented according to OData specifications.
- When publishing a binary inside a Component, the last published date is not updated in the Content Data Store
-
Updated so that
LAST_PUBLICATION_DATEis updated. - Content Deployer would stop if Cache Channel Service was not responding
- Fixed: the unavailability of the Service no longer blocks the Content Deployer message queue.
- Publishing unmanaged binaries could result in publishing of unrelated Pages
- Unmanaged binaries are now properly identified and published without such side effects.
- Deployment of content failed when Page metadata was too large
- Deployment now fails only if Page metadata does not fit available storage size.
Outbound E-mail and Audience Manager
- Implementers could not check existence of a Contact before loading it
-
Because of this restriction, the implementer could not prevent a
"ContactDoesNotExist"exception from being raised if the Contact did not exist, because the exception could not be caught. This was fixed by introducing theContact.Existsmethod (.NET) and theContact.existsmethod (Java). - Maximum open cursors was exceeded (JNDI only, and possibly only WebSphere)
-
'ORA-01000 Maximum open cursors exceeded'was regularly thrown by Audience Manager on the presentation side becauseResultSets were not explicitly closed. According to the JavaDoc forResultSet::it isn't necessary, although this seemed to be only true when not using JNDI; when using JNDI it would leave the cursors open.The problem is now resolved.
Documentation
- Wrong instructions for setting default values for mandatory Multimedia Schema fields for WebDAV
- Documentation erroneously claimed that this should be configured in a file cc_crtd_def.xml when in fact it must be configured using the Event System.
- Wrong description text for IncludeComponentLinks in TOM.NET and Core Service API reference documentation
- Claimed that the Boolean should be set to 'true' exactly when it should be set to 'false'.