Hotfixes included in 2011 SP1
The SDL Tridion 2011 SP1 release includes the latest set of hotfixes. You can find these hotfixes, and information about them, on the SDL Tridion World Web site.
To see and download all hotfixes, visit SDL Tridion World at http://www.sdltridionworld.com, log in using your SDL Tridion World username and password, and select from the menu at the top.
Included in SDL Tridion 2011 SP1 are the following Content Manager hotfixes:
- 74265
- Multiple value / repeating Embeddable schemas did not display drop-down values correctly.
- 74280
- Styles in FormatAreaStyles.css did not show up in the Firefox or Google Chrome drop-down.
- 74316
- If you delete the last field from metadata in a Schema, this did not affect previously created Components.
- 74359
- On SQL Server, Content Manager timed out after 30 seconds.
- 74412
- The Core Service and the GUI sometimes reported the following error when searching for a Component: "The specified item type 'Component' does not exist in the colletion of mappings between an ItemType and a data object type."
- 74587
- EDA_ITEMS_ITEMIDENTIFICATIONCONFLICT and EDA_ITEMS_CATEGORYIDENTIFICATIONCONFLICT were unnecessarily slow, increasing the chance of deadlocks when creating/updating items.
- 74658
- It was not possible to add a Flash file when adding an image to a Format Area.
- 74708
- Editing data cells in the table editor was not possible in Firefox.
- 74732
- In a Format Area, once a style had been selected for text in a Format Area, it could no longer be cleaned or changed.
- 74821
- The editor did not allow users to select an empty background color, empty text color or empty language.
- 74846
- A defect in the EDA_SYSTEM_SETPUBLISHSTATE stored procedure caused the publish to not always update after successfully publishing a page.
- 74870
- Custom resolvers only allowed items to be added to the resolved items collection, and not removed. This had been possible in earlier releases.
- 74936
- The option to Allow on page using dynamic assembly for a Component Template did not work properly.
- 74946
- The presence of a double slash (//) in a URL caused problems in combination with single sign-on software.
- 74990
- Opening a Component could cause the contents (that is, the results) of a Virtual Folder to change.
- 75000
- Saving a Component with an Embeddable Schema caused the blank fields to be updated with the values from the last embedded component.
- 75012
- Internet Explorer sometimes experienced slow typing and/or missing characters in a Format Area because of cross-window calls.
- 75219
- Retrieving a BluePrint hierarchy was sometimes unnecessarily slow.
- 75252
- In a Schema originally created in 5.3, the 'Allowed Actions' field could be empty.
- 75290
- Applying custom restrictions within the cm_xml_usr.xsd configuration file made it impossible to save pages with " " (a space) or "&" in the file name.
- 75311
- If a Schema with a custom filter XSLT was modified, this made it impossible to save Components.
- 75323
- In some cases, when creating a new Page item, the dropdown to select a Page Template was empty.
- 75383
- See 75219.
- 75488
- Components accessed using the TOM based event system, on the Pre-action events types, were found to have incorrect properties.
- 75769
- When loading a .NET assembly during Template Building Block creation, the assembly could not be saved.
- 75946
- A Schema field with the string 'password' in its Description caused the input field to display text as bullets.
- 76461
-
Retrieving a Keyword from a Category, based on its title (
Category.GetKeywordByTitle) would throw an exception for non-administrator users.
Also included in SDL Tridion 2011 SP1 are the following Content Delivery hotfixes:
- 73992
- Large publish transactions, performed using HTTP, would cause an "error in opening zip file".
- 74213
- Large publish transactions would cause the Content Deployer to time out; a deployment failure would fail to be notified to the Content Manager; and the unpublishing of binary variants did not work properly.
- 74325
-
Because the Linking Windows service did not properly release
ComponentLinkreferences, the service caused a memory leak. - 74436
- After installation of the Hotfix Rollup 1, the Linking and WAI Windows services would not start.
- 74446
- See 73992 and 74213.
- 74930
- Publishing many items resulted in permanetly "throttled" items with a limited window size.
- 75207
-
The Content Delivery Web service returned incomplete formatting on
CustomMetacolumn links. - 75266
- In an HTTP Upload scenario working in .NET, a big zip file could take too much time to save, causing the Content Deployer to attempt to open the zip file too soon.
- 75560
- Transport over SSHFTP/SFTP could cause intermittent outages.
- 75913
- Committing Deployment could take too much time, resulting in out-of-memory issues.
- 76495
-
On a Linux system, the Content Deployer could create a wrong file name for transport packages, causing it to raise a
java.text.ParseException.