Last updated 11 December 2007
This file contains important information about defects corrected in the latest version of Serena Collage. For information on installing and using the current release of Collage, see the readme file.
(DEF111957) You cannot copy contribution documents more than once. The following error appears:
Could not copy asset
Unknown error occurred
(DEF115558) If you select multiple assets, display Properties | Metadata, select all metadata fields and then click Apply to all, all non-editable metadata fields for the assets you originally selected are set to a new value, or left undefined. Non-editable metadata fields should never be editable.
(DEF67056) When you copy an asset, image references are not updated so that they correctly point to the original location. Instead, the relative path as defined in the original asset is persisted. As a result, shadow assets for the images are created in the wrong locations, and the image references in the copied asset are broken.
(DEF90413) You cannot edit assets in the internal editor when the asset type is derived from another asset type. The Editor appears blank when you open it.
(DEF104418) In the following scenario, the AssetQuery component is stripped from an asset:
1. Add a new MIME type to a project with with the extension ".xml."
2. Create a new XML file and set it to the new asset type.
3. Add an AssetQuery component to the asset.
4. Copy the asset.
(DEF112021) The AssetQuery component deploys with incorrect links when both of the following are true:
1. Identical AssetQuery components exist in multiple assets
2. The parent folder of each file returned by the AssetQuery components starts with the same string, for example if one parent folder is named Doc10 and the other is named Doc10a.
3. The relative path in each AssetQuery component is set to: relative="."
(DEF115543) When the root property in the AssetQuery component is set to "/" no results are returned.
(DEF115559) If the <head> tag of a masterpage includes a component with a <style> tag and colons in the style definition, all components on any contribution document that uses that master page will break.
(DEF116386) The $node.absdetailsurl macro generates invalid links.
(DEF66607) In certain circumstances when querying for assets based on metadata values, the AssetQuery component sometimes returns the same asset twice.
(DEF67078) The Navigation Bar component does not return all nodes when it refers to a site structure that is split into multiple site structures. To enable this to work, you can now add the following attribute to the component:
MergeSiteStructures ="true"
(ENH68438) The Navigation Bar component should provide formatting control that results in a parent node appearing highlighted when a user is displaying pages under that node in the navigation hierarchy. To enable this, you can now add the following attribute to the component:
highlight="true"
(ENH79407, ENH90316) The Navigation Bar component should support the findfile attribute that is already supported by the Include component. This attribute allows you to identify the precise site structure file to be used to generate the navigation bar.
(DEF101867) If you attempt to edit or review a task that does not include any files, nothing happens.
(DEF109207) When choosing a deployment time, you should not have to click Done in order to save the time that you have selected.
(DEF111485) The following error appears if a user who does not have the View Assets permission attempts to create a new asset in a contribution folder:
Storage.CreateFileAsset: invalid folder asset:-1
(DEF112642) If you add a file to a task and then choose to save the task for later, the file appears to disappear from the task if you then click the filename. If you log out and log in, and then reopen the task, the file again appears.
(DEF113754, DEF127215) When you create a new task, assets associated with the task template are not added to the task.
(DEF114265) If you attempt to edit metadata for a task assistant, and there are multiple metadata fields with very long names, the following error may appear:
An Error Occurred
Error: incorrect data submitted from form.
The stacktrace is attached.
(DEF114888) With Collage running on WebSphere on Solaris, the following error appears when you attempt to use an assistant:
[Fatal Error] :1:249: The element type "Data" must be terminated by the matching end-tag "</Data>".
(DEF115554) When you attempt to deploy from a task using a deploy map that only deploys approved versions of assets, deployment fails even if the assets are already approved. The following error appears:
Approve action on asset level not allowed in a task context
(DEF115555) When you attempt to choose files to deploy from the Files to Deploy dialog box, the file picker is not visible. It opens behind the current window, and you must press ALT+TAB to see it.
(DEF125515) When secure HTTP (HTTPS) is enabled, the following error appears when you try to log in to Collage Contributor:
Expected token 'EOF' found ":":
/mfx-->:<--/mfx model
(DEF127211) The following error is incorrectly displayed when you click the Done button while displaying properties for assets in a task that is in its final state (such as Approved):
Cannot mark task done because you have checked out assets. Please check them in before marking done."
(DEF113320) The Filter HTML feature in contribution documents does not always follows the rules set in the AllowedFilterHTMLTags.xml file. As a result, attributes that should be filtered out are not.
(DEF106939) When you save a contribution document that includes links with javascript in them (such as <a onclick...>), the path is converted to the internal Collage preview URL. The file is then deployed with this URL, and the links do not work. Links including Javascript should be saved and deployed precisely as entered.
(DEF107011) With Firefox, if you switch between the Edit and Source views in the Contribution Editor, ASCII character entities are not correctly stored as defined in the char2HtmlEntities.xml file.
(DEF107109) When you edit a contribution document using the Contribution Editor in Firefox, extra question marks and <span> tags are inserted.
(DEF110519) With Internet Explorer 6, if you run spell check in the Contribution Editor in a document that includes links to anchors that are in the same document, the pound sign (#) is stripped and the links no longer work. This occurs when the anchors include underscore characters (such as "_target").
(DEF115545) With Internet Explorer 6, when you apply styles and save a contribution document, the pound sign (#) is stripped from links to internal anchors and the links no longer work.
(DEF111475) From the Content | Contribution view, if you select a contribution folder and click the Metadata button, you are unable to edit the folder description or metadata.
(DEF112448) The toolbar in the Contribution Editor becomes disabled when you insert an anchor in contribution document. You must save the document in order to re-enable the toolbar.
(ENH112626) When inserting an external link in a contribution document, it should be possible to sort on link name and description.
(DEF113529) When you delete a reusable content snippet from a document definition file, the dialog that appears incorrectly states that a field is being deleted, and that this will affect all documents that use that field.
(DEF113755) When you use the Contribution Editor to edit links with query string parameters, the parameters are duplicated. This can result in multiple broken links on a page.
(DEF113756) In Firefox, you cannot create a link in a link field type.
(DEF113757) Components stop working on the Edit page of the Contribution Editor when you enter an opening double quotation mark (") without closing it in the contribution fields.
(DEF113758) The following error sometimes appears when trying to create and save new contribution documents:
Storage.fetchFileAssetData Invalid asset 36888 Sql.DataAccessQuery:SELECT AV.FileName,D.FileDate,D.DataSize,AV.MasterPageAssetId,AV.Version,AV.IsMasterPage,D.DataId ,PF.Path FROM AssetVersion AV, Asset A, Data D,PubFolder PF,PubContains PC WHERE A.AssetId=36888 AND AV.AssetId=A.AssetId AND (EXISTS (SELECT TC.ChildId FROM TaskContains TC WHERE TC.ChildId=A.AssetId AND TC.ChildVersion=AV.Version AND TC.TaskId=-1) OR ((NOT EXISTS (SELECT TC.ChildId FROM TaskContains TC WHERE TC.ChildId=A.AssetId AND TC.TaskId=-1)) AND ((A.CheckOutUserId<>619 AND A.LatestVersion=AV.Version) OR (A.CheckOutUserId=619 AND A.LatestVersion+1=AV.Version)))) AND D.DataId=AV.DataId AND PC.ChildAssetId=A.AssetId AND PC.ParentAssetId=PF.AssetId
(DEF113759) All components in a contribution document stop working when all of the following are true:
1. The document includes a link with a single quote in the <title> tag.
2. There is another single quote somewhere in the document content.
(DEF115546) The following error appears when you attempt to create or edit a contribution document for which the document definition file has many reusable content snippets:
BuildLayoutPage exception: String index out of range: 0
(DEF115557) After upgrading to Collage 5.1.2.3, deployment of contribution documents fails when the documents include <div> tags with certain style attributes
(DEF115561) URLs in plain text fields are converted to HTML links.
(DEF123583) In Internet Explorer, when you select paragraphs and apply styles that are defined using <span> tags, additional paragraph <p> tags are inserted.
(DEF127212) When you add an external link to a contribution document, that link is not automatically approved.
(DEF127218) An error like the following appears when you attempt to create an external link in a contribution document that you have opened from a task:
WRN 2007/08/20 13:16:12 PDT-- Storage: Approve action on asset level not allowed in a task context
(DEF127733) When you upload an image to a contribution document that you have opened from within a task, the modified date is set to 12/31/69.
(ENH69896) By default all links in a contribution document are resolved as relative paths. There should be a way to force all references to resolve as absolute paths. You can now do this by setting the Use only Absolute Paths when deployed option appropriately, when setting options for document types from the Project | Contribution Setup view.
(DEF74807) The following error appears while deploying changed assets after creating a new version of a file that has a different asset type and MIME type than the original file:
error: Failed to convert.
Links to this document will not be valid. The return error message is:
General Exception java.lang.ArrayIndexOutOfBoundsException
(DEF101076) You cannot copy a project from a Sybase database server to an MS SQL server when you upload a file greater than 256 megabytes before attempting to copy. The copy fails and an error like the following appears:
EXP 2006/08/19 14:40:13 PDT-- Storage: SQLMigrator.insertData-SQLState(08S01),SQ
LException:[Microsoft][SQLServer 2000 Driver for JDBC]Connection reset by peer:
socket write error SQLState: 08S01 errorCode: 0
IMPORTANT! This has been completely fixed for SQL Server 2005, however the error may still occur with SQL Server 2000 if you upload files greater than 400 MB.
(ENH104624) To improve deployment performance with Oracle, the "Analyze" query in the GatherTableStatistics stored procedure should be replaced with the dbms_stats package.
(DEF115818) When upgrading to Collage 5.1.2 on Oracle, the database cannot be upgraded and an error like the following appears:
STS 2007/06/21 08:09:11 PDT-- Connection: Upgrading database ....v242 to v243
STS 2007/06/21 08:09:11 PDT-- Connection: Upgrading database ....v243 to v244
STS 2007/06/21 08:09:11 PDT-- Connection: Upgrading database ....v244 to v245
STS 2007/06/21 08:09:11 PDT-- Connection: Upgrading database ....v245 to v246
java.sql.SQLException: ORA-02296: cannot enable (myPorject.) - null values found
(DEF71204) On MS SQL, the following error appears if you attempt to copy a project that includes a period in the name:
Unable to open project or database is corrupt...unable to initialize.
(DEF106235) When searching for assets on non-English operating systems, the search fails if you specify a date range.
(DEF105955) On non-English operating systems, deployment activity reports are unreadable due to character display issues.
(DEF106348) If the default locale for the Collage server is set to anything but English, you cannot then log in with English set as the locale for the client.
(DEF113349) Encoding for XML, ASP, PHP, and JSP files is not honored. If no <meta> tag is defined with desired encoding in the layout or master page files, they are deployed as UTF-8 by default and as a result, multi-byte characters may be corrupted. Collage should honor the encoding in these files.
(DEF113524) Multi-byte characters entered from the Contribution Editor are deployed as question marks.
(DEF100710) If load balancing is enabled between two servers and you then attempt to start a deployment that runs on the other server, the following error appears on the Deploy | Activity screen until the deployment activity has completed finished running:
Activity terminated, unexpected shutdown
(DEF102152) When you deploy a file that links to a deleted asset, the deployment error returns the following generic message but does not include the name of the deleted asset:
error: refers to asset in recycle bin
Without the asset name, it is difficult to locate and restore the deleted asset.
(DEF103433) When deploying to the root directory on an FTP server, deployment fails if you select the Delete directory contents before deploying option. Any files at the root directory are deleted, however no files are then deployed to it.
(DEF104434) The following error occurs when running two or more scheduled deployment activities at one time:
error: IncludeAsset: null
completed (1.12 sec)
The deployment process failed
IncludeAsset: null
(DEF107213 and DEF107216) Files may be incorrectly deleted during deployment, in the following scenario:
1. You run a full deploy.
2. You then delete a folder (such as "new").
3. You add a new folder in the same location, with a name that is spelled the same but that has different capitalization (such as "NEW").
4. You deploy the new folder.
5. You make additional changes to the project, and then choose to deploy changed assets only.
As a result, files in the "NEW" folder are deleted.
(DEF107560) Files at the root of the website may be deleted incorrectly when deploying to a Secure FTP (SSH) site. For example, if you rename a folder in the project that contains a file called "index.html" and then deploy the root Website folder, the following occurs:
The original folder and its "index.html" file are deleted from the target server, and the new folder and "index.html" file are created. This is correct behavior. However, if there is a file called "index.html" under the root Website folder, it is deleted. This can result the entire Website becoming inaccessible.
(DEF111942) A deployment of changed assets takes far longer than a full deployment, in some cases up to 2000% longer. This may occur even when there are no changed files to deploy.
(DEF114596) When you deploy an asset containing a deleted link, the resulting error message omits the first character of the missing link. For example, if the link is mailto:collage@serena.com, it appears in the error text as ailto:collage@serena.com.
(DEF114885) A PublishStorage.addDependencies truncation error causes deployment to fail.
(ENH115327) To improve deployment performance, the site structure cache should be configurable so that the cache can store more than 25 site structures.
(ENH115324) Add index in the MetaData table to improve AssetQuery performance during deployment.
(DEF115552, DEF115553) The $node.absurl macro does not always resolve to the correct path.
(DEF115556) When you deploy to an FTP or Secure FTP server, expired assets are not deleted from the target location.
(DEF123753) The following out of memory error appears during deployment:
(java.lang.OutOfMemoryError)
(DEF125266) Starting with Collage 5.1.2, .site files are generated with every deployment, however they are never deployed even if the Deploy option is set to If referenced or Always.
(DEF127214) In some cases, Collage deploys "My Bookmarks" folders, causing deployment to fail with the following error:
Failed applying metadata
One of more of the selected assets are not checked out.
(ENH63158, DEF64549) If you have installed your deployment server separately from the primary Collage server, deployment status does not appear on the Collage server until the deployment activity is completely finished.
(DEF67188) Deployment on Oracle is very slow in comparison to MS SQL Server and Sybase.
(DEF71495) If you attempt to run a scheduled deployment activity that was created by another user, the following error appears:
Activies not started. One or more tasks could not be started
(DEF74989) If you attempt to start a scheduled deployment activity from one Collage server using a deploy map from another Collage server, the deployment fails to start and an error like the following appears:
Task #task does not exist on this server
(DEF95110) If an IncludeAsset component causes a "null" error during deployment, all components generated after this point may also fail.
(DEF99399) Assets that are referenced from an "asset" metadata field are not deployed during a "selected files and all references from those files" type deployment.
(DEF100708) If you copy an asset with an asset type metadata field assigned to it, Collage creates a new folder called $1 at the root of the project. If you then enter values for text type metadata fields for that asset and copy the asset again, none of the new metadata values are copied.
(DEF127213) The following error appears when you attempt to edit metadata for a deploy folder from the folder properties dialog box in the Deploy Folders view:
Failed applying metadata
One of more of the selected assets are not checked out.
(DEF127220) When you copy text from Microsoft Word and then paste it into a metadata field, all Word formatting should be removed. The text should be pasted as plain text.
(DEF111531) After upgrading from Collage 5.1.1 to 5.1.2, the following error appears when you click on folders in the Content | Deploy Folders and Content | Contribution views:
RequestBase.SimpleQuery-SQLState(23W01),SQLException:ASA Error -193: Primary key for table '#readassets' is not unique SQLState: 23W01 errorCode: 2601
(DEF111735) After upgrading to Collage 5.1.2, errors display when attempting to create or edit contribution documents. When creating a new asset, the following error appears:
Unknown error occurred. New Document Failed
When editing an asset and clicking Save or Exit, the following error appears:
Validation Error inXML. Checkingin the Asset failed
When editing an asset in Collage Contributor, the following error appears:
Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIXMLHttpRequest.send]
(DEF113599) If you install Collage 5.1, then upgrade to 5.1.1, and then upgrade to 5.1.2, several program files are missing and the installation fails.
(DEF127219) SSL is not always used with LDAP, even when SSL is enabled. Functionality in the System | Users and Groups screen always connects to the LDAP server without using SSL.
(DEF66947) When you change permissions for an asset, the changes are not listed in the Project | Audit Log view.
(DEF111953) The Collage server hangs when you restart it after adding the NASServlet.hostip property to the nas.properties file.
(ENH113503) The Collage client should be supported on Apple OS 10.4.9.
(DEF115542) The drop-down lists to select views (such as Content | Deploy Folders) do not work with new versions of Firefox.
(DEF115544) A masterpage with a <style> tag and <script> tag that includes the text "url" causes components to fail to generate and links to break.
(DEF127216) From the Content | Deploy Folders view, the More button has no effect in Firefox on the Mac OS.
(DEF127217) In Firefox on Mac OS, the refresh times on deploy folders are very slow, and an error like the following appears in the Java console:
java.lang.ClassFormatError: Incompatible magic value 1008813135 in class file merant/adm/applet/PopupMenuApplet
(DEF129112) When you attempt to copy a folder, copies of the assets inside the original folder are created in the original location. A new copy of the entire folder should be created, with copies of assets inside of it.
End Release Notes
Copyright © 2006-2007 Serena Software, Inc. All rights reserved.