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.
The following issues have been addressed in release 5.1.2.
ENH104668: Collage must support the change to the start date of Daylight Savings Time in the United States. To support this, Collage must ship with the latest release of JDK 1.4.2, and it must support versions of application servers that work with the Daylight Savings Time change.
ENH104705: To support the changes to Daylight Savings Time in 2007, Collage must provide version 1.5.0_06 or later of the Sun Java Virtual Machine.
DEF69566: When you upload a file using the Upload Folder command, absolute paths inside the file may be changed, resulting in incorrect file references. Specifically, an extra folder name may be added to the absolute paths.
DEF69909: You cannot copy an asset that has an Asset type metadata field assigned to it. When you do this, the new asset does not have the correct value in the metadata field.
DEF80158: Collage does not parse background:transparent url properties in cascading style sheets.
DEF82591: Collage drops trailing quotes from style definitions in XSL files.
DEF84998: Collage does not correctly parse CSS files that include @ symbols in comments.
DEF86345: Collage does not parse links or anchors that include data field macros, such as $node.assetid.
DEF88468: When previewing or deploying an Excel file, the following error sometimes occurs:
Storage: BlobCache.getDataBlock-file IO
Converter failed. Exitvalue from DocConvApp.exe : 3(DocumentNotConverted)
java.io.IOException: Converter returned invalid code of 500.
at com.merant.nebula.storage.cache.BlobCache.convert(BlobCache.java:1060
This results in deployment failure.
DEF90079: Collage incorrectly resolves URLs in ColdFusion include tags (<cfinclude>) to absolute paths, including the http:// prefix.
DEF92334: You cannot create a new asset if you include an apostrophe in the asset description.
DEF64827: When you define the nodes attribute in the NavBar component as FirstLevel, it does not correctly display the nodes in the site structure, when the site structure contains multiple root nodes.
DEF64864: Components that include Chinese language characters display those characters incorrectly if the HTML files are not encoded correctly to UTF-8.
DEF64967: When the NavBar component is configured to sort on a metadata field, it in fact first sorts assets based on the asset IDs of their folders, and then on the metadata field values. This results in an incorrect sort order; the component should sort on folder name first, then on the metadata fields.
DEF66558: The AssetQuery component sorts results incorrectly when you set it to sort based on integer metadata fields. Instead of ordering results sequentially, it orders them as follows:
1
10
100
2
200
DEF69573: The DBQuery component generates invalid HTML code when it encounters a database cell with a NULL value. Specifically, it may omit some rows from the data, and exclude the code from the <prolog> portion of the component.
DEF71071: The AssetQuery component does not generate the correct path to assets using pdfurl, htmlurl, or psurl macros if there are multiple MIME types defined for the same file extension.
DEF75467: The IncludeAsset component displays the following error when the query results return an external link:
ERROR: IncludeAsset could not find file matching [link]
DEF80721: The IncludeAsset component incorrectly deploys the $node.name macro as "$node.name" instead of replacing it with the name of the asset it refers to. This happens when the referred asset is set to never be deployed.
DEF81534: When you define the root attribute in the AssetQuery component as "/" the component does not query the entire folder structure as expected. It is changed to %24 when you check the file in.
DEF81589: The MetaTag component only functions correctly when it includes a $node macro in the component body, or no body section at all.
DEF85677: When you define the nodes attribute in the NavBar component as "FirstLevel," the component should only return the assets nested one level beneath the root folder. However, the component also returns assets directly under the root folder.
DEF86276: When you include a max attribute in a Select component, the $node.recordnumber macro does not return the correct values.
DEF88238: The AssetQuery component fails to generate correctly if it includes a metafilter attribute with a value of "M." in it.
DEF100832: The AssetQuery component returns items from similarly named folders, when the levelsdeep property is used.
INT102524: When defining a contribution assistant, you can choose to automatically expand the list of properties when users create or edit a document using the assistant. However, this setting does not work.
DEF85712: Required list metadata fields do not display the icon indicating that they are required.
DEF86202: You cannot browse to select an asset when updating asset type metadata fields.
DEF86343: When you open a task, the Edit link for associated assets is available even when the task is not currently in the Edit state.
DEF86463: You can save a file without completing required contribution fields.
ENH88605: When browsing files, any user can see all folders in the project, regardless of permissions.
DEF89591: If you open a file from within a task and then choose to save it for later without checking it in, you are unable to then open and save the same file from under "Files I’m Working On." This is because the file is already in use by you in context of a task. To prevent this from occurring, you should not be able to open a file from under "Files I’m Working On" if you already have the file open from within a task.
DEF89743: You cannot create a new file unless you have full permissions to the folder. Attempting to do so results in a stack trace error. You should be able to create a new file with just the Create, Modify, and Read / Use permissions.
DEF92478, DEF95580: When a user with no permissions to the /System folder attempts to create a new file in Collage Contributor, a message should appear that explains that you cannot create a file without access to the /System/Flows folder.
DEF93556: When you attempt to edit an asset, the following error occurs:
Storage.GetEmailAddress - uknown user
This occurs when Collage is set to use LDAP for authentication, with case sensitivity, and you log in with mixed case.
DEF97695: When you save changes to metadata fields, the documents are not refreshed in Collage Contributor with the new metadata values.
DEF91633: When you preview a site from the Contribution view, you can choose to preview the \System folder. This folder should not be available to preview.
DEF84578: When creating a file using the Create-Modify default assistant, you can browser to choose a folder. When you choose a folder in this way, the folder you choose does not appear as it should in the Folder field on the New File dialog box.
DEF100712: You cannot create image links using Firefox.
ENH103004, DEF90078: It is not currently possible to control the specific HTML elements and attributes to which the Filter HTML setting applies. You cannot make exceptions for specific HTML markup that contributors may need to enter.
DEF66566: If a table border is set to 0, no guidelines appear in the Contribution Editor when you edit the table. This makes it difficult to distinguish the location of cells. To work around this issue, you must save the contribution document, or enable the Filter HTML option in the document definition file.
DEF66593: When you apply a style in the Contribution Editor that applies the <blockquote> element, you can no longer assign other styles.
DEF67029: When inserting external links in the Contribution Editor, you can hover over the links to see the URLs. However, long links do not display in their entirety; they are cut off after 64 characters.
DEF67307: If you define the font size for a rich text field as a px value (such as 11px), you are unable to save changes to documents created using that document definition file.
DEF69463: The Contribution Editor does not function correctly when working with documents for which the <!DOCTYPE> tag is set to XHTML. Collage should support XHTML documents in the Contribution Editor.
DEF69470: When you check in changes to a document definition file, the dialog box does not refresh. The Check In button is still visible, even though you must actually check the file back out before you can again check it in with more changes.
DEF69593: Contribution documents are not checked in when you close them from the Preview using the X icon on the Contribution Editor window.
DEF79735: From the Contribution Editor, you can enter a vertical space value for images. However, if you enter a value of 0, the vspace attribute is not added to the <img> tag.
DEF80335: When you create tables in the Contribution Editor, the values for the valign and align attributes are switched for <td> tags. For example, if you define valign as middle and align as center, the actual code appears as:
<td valign=center align=middle>
DEF82393: Multiple users cannot create contribution documents with the same names while working in context of tasks. The expected behavior is that Collage will automatically add numbers to each new instance of the same file name in order to avoid filename conflicts.
DEF83362: When you save a contribution document that includes Javascript references in <a> tags, the tags may be saved incorrectly. For example, if the tag links to French language characters, portions of the tag may not be saved.
DEF83428: When you paste text that includes paragraph <p> tags into text fields that are set to allow only one line, the Contribution Editor does not strip the <p> tags. The <p> tags should be removed in text fields that allow only one line.
DEF85638: The Contribution Editor toolbars are disabled when you attempt to edit reusable text snippets that include references to CSS style definitions that contain width or height values.
DEF86053: The Contribution Editor crashes when you hit the ENTER key after a link that uses a style definition that includes display:block code.
DEF86224: When you switch from the Internal to the External tab while inserting a link, any class and style definitions you had defined for the link are lost.
DEF86264: When you attempt to edit the global styles document definition file, the following error appears:
"" is checked out to another user. Open in editor anyway?
DEF86287: When you assign a link (containing a style) to an image in the Contribution Editor, the style is incorrectly stored. It should be stored as a value for the class attribute, but is instead stored as a value for the style attribute, with className prepended to it. For example, it appears as:
style="className:StyleClass
Instead of:
class=StyleClass
DEF86402: The right pane of the Insert Link dialog box does not consistently display the contents of the selected folder.
DEF87001: When you paste markup into a plain-text contribution field, the markup is not always converted into plain text. The markup is instead deployed. For example, is not converted to a space.
DEF89053: The following error appears when opening the Contribution Editor:
Undefined label 'locale=en_US' in toolbar definitions
DEF89694: The Spell Checker causes the browser to hang when you choose to change all occurrences of a spelling error.
DEF89695: When the Auto Approve option is enabled under Project | General Setup, new links in the Contribution Editor should be automatically approved. They are not.
DEF89883: When you switch between the Edit and Source views in the Contribution Editor, you are prompted to save the current document if you haven’t already done so. Every time you accept this prompt, a new version of the document is created even though you have not actually checked the document in.
DEF90075: When metadata fields are displayed in the Edit view, the view is not refreshed after you edit metadata values.
DEF90076: The Undo button in the Contribution Editor undoes too many actions at one time, rather than just the last change.
DEF90081: If you save a contribution document and then attempt to apply a style to linked text, the link is removed from the text.
DEF91052 / DEF83211: Each time you apply a new font to text in the Contribution Editor, extraneous <font> tags are added instead of simply replaced with the new font style. Eventually, you can no longer edit the contribution document.
DEF91523: In the Contribution Editor, when you add a table with border set to 0, the table tags are incorrectly coded, and internal cmid tags are visible in the content.
DEF91638: The Clear Formatting command is not accessible when the screen resolution is set to 1280 x 1024.
DEF91640: A Java error results when you attempt to apply certain styles to multiple paragraphs at one time. This occurs when the style applies the <p> tag.
DEF91906: In the Contribution Editor, the Indent command behaves unpredictably when you attempt to indent items in a list. For example, text may indent while the list number does not, or numbering may be restarted.
DEF92172: When you enter and edit forms in the Contribution Editor, an outline clearly locates the form on the page. However, this outline disappears after you save the contribution document when using the Firefox browser.
DEF92230: Colors are not correctly applied to items in a list. The nesting of the <font> tag is incorrect, with the result that the color is applied to only part of the list.
DEF92272: When you insert links to Microsoft Media Server (MMS) pages, the links are corrupted when you save the document. A pound sign (#) is added before the URL (which should begin with mms://).
DEF94097: The following stacktrace error appears after applying changes to a contribution document definition file:
Exception occurred:JSP.as_Contribdeftree.jsp
DEF94106: The following error sometimes occurs when running spell check:
Spell checker cannot select/change this word
This may occur when the text field includes multiple instances of a word that has been added to the dictionary, but when the first occurrence of the word includes different case than the word included when it was added to the dictionary.
DEF94626: When you change the border width for a table to 0, the class attribute for the table is incorrectly set to the following value:
class=tableborderzero
DEF94628: If you Click Save from the Source view and then quickly click the Edit view, a prompt appears asking if you want to save the document. If you click Yes or No, a runtime error appears and asks if you want to debug. If you choose No, another runtime error appears. At this point you must cancel. If you then click Exit, the browser may hang with the following error:
The instruction at "0x0945b0c5" referenced memory at "0x00000034". The memory could not be "read".
INT96568: When you exit the Contribution Editor, the Main Collage window hangs.
DEF101868: When content is pasted into a plain text field, all of the spaces within that field are converted to . This only happens when using Firefox.
DEF104380: Editing a page containing named anchors causing the anchor to be re-written incorrectly. This causes the Contribution Editor toolbar to no longer function, and may cause text on the page to display with incorrect styles.
DEF82133: It is difficult to apply and remove styles from text in the Contribution Editor. You can only apply styles to text by first selecting existing text. The styles then apply to any additional text that you enter. You should be able to instead turn styles on or off as needed, either for selected text or for new text.
DEF106176: When you apply formatting to text in the Contribution Editor, undo does not work when you first hit the Undo button or enter CTRL+Z. Undo only works the second time you hit the Undo button or enter CTRL+Z.
DEF87158: During installation, the administration database connection verification will fail in the Microsoft SQL user has "master" set as the default database.
DEF90040: Scheduled backups of Admin databases fail to send email notifications, and the backup may hang after the initial run.
DEF90401: When you schedule a backup of the Admin database, you are prompted for the system password, even when the system password is already stored on the Database Servers screen .
ENH91636, INT96690: Collage does not support Microsoft SQL Server 2005.
DEF93985: When you attempt to upgrade a project running on Microsoft SQL Server that has WebDAV task triggers defined, the following error occurs:
WRN 2006/04/27 11:54:08 PDT-- Storage: Asset.InitComponents-SQLStateHY000),SQL
xception:[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Subqueries are no
t allowed in this context. Only scalar expressions are allowed. SQLState: HY000
errorCode: 1046
DEF92533: Scheduled backups of project databases fail with Oracle DB servers on UNIX.
DEF100177: During secure FTP deployment, Collage fails to transfer files to the right level in the directory hierarchy. Collage creates the target directories one level too deep; because the directory structure does not match the folder structure in Collage, deployment then fails.
DEF101340: Deployment fails when you define a deploy map that maps a root folder to multiple locations, and the path to each location is identical.
DEF64970: When you include quote characters (") in the descriptions of deployment locations, Javascript errors then occur when you try to use the locations in deploy maps.
DEF66571: After changing the name of a project, the following error appears when you attempt to edit a scheduled deployment activity:
Edit unsuccessful. Entry could not be updated because of invalid permissions
DEF66728: If you deploy two root deploy folders to different locations, and if each root deploy folder begins with the same string of characters (such as "website"), image references from one site to another may not be generated correctly. Specifically, if each site has its own external URL defined, the external URLs are not correctly appended to the image references.
DEF66996: It should not be required that the masterpage and site structure files be deployed.
DEF69424: Deployment fails if the Applied Master Page field under Project | General Setup | Properties is set to None.
DEF69803: When you convert a Microsoft Office document to PDF format during deployment, links to that file are not correct. This occurs when the filename includes periods.
DEF69853: Links from Word documents that have been converted during deployment to HTML do not work correctly when those links refer to files that reside in the same folder in Collage.
DEF69920, DEF92123: Deployment logs do not display the name of assets that contain AssetQuery errors. The path to the asset containing the AssetQuery is given, but the filename for the asset is not. This makes it difficult to troubleshoot errors that occur when deploying components.
DEF72729: The following error appears in the deployment log when you deploy document definition files for which the Deploy property is set to If referenced:
error: refers to asset/System/Links which is not deployed
To prevent this error, document definition files should never be deployed by default.
DEF74443: The Deploy Archive portion of the Deploy | Activities view does not always display the correct start time for deployment activities.
DEF76475: You are forced to perform a full site deployment after adding a new project group.
DEF81342: Deploying an asset that includes a NavMap component fails if the component refers to a site structure definition that is set to never deploy. The error states that the site structure is a shadow asset.
DEF83317: Purging of deployment history is very slow when there is a lot of history.
DEF83432: When you deploy using a deploy map that is set to only deploy approved assets, unapproved master pages are used when there are no approved versions. Unapproved master pages should not be deployed in these cases.
DEF83502: Deployment performance is very slow when there is a large amount of deployment history.
DEF83962, DEF86781: Scheduled deploy activities occasionally do not appear in the deployment history, making it difficult to determine the success or failure of the deployment.
DEF86675: If you change the time that a scheduled deployment activity will take place, the new time is only honored if it starts after the currently scheduled start time or after Collage is restarted.
DEF88073: When you deploy an IncludeAsset component that includes a reference to a file that cannot be found, the deployment error report displays the asset name of the file being generated, when it should display the filename.
DEF89968: When as asset’s start date has passed, the asset is not automatically deployed during the next changed asset deploy.
DEF90966: After deleting assets that had the Force Deploy option enabled, messages about the deleted assets still appear in the deploy log, even though they are no longer included in the deployment activity.
ENH91804: Deployment fails when Collage attempts to deploy across a firewall that is set to close any session that is inactive for more than a short period of time. Collage should regularly ping the database during deployment in order to keep the session active.
DEF92119: When you deploy an asset that references an assets that has been permanently deleted from Collage, the deploy log incorrectly states that the asset is still in the recycle bin.
DEF92271: When you deploy to an FTP server using SSL, the deployment fails if multiple target directories start with the same word. For example, if you are deploying to folders called /folder and /folder1, deployment fails.
DEF93390: When multiple deployment activities are scheduled to start at the same time, the deployments fail with the following message:
Folder.PrepareReadFolderCache-SQLState(23000),SQLException:[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Violation of PRIMARY KEY constraint 'PK__ActiveUsers__6FB49575'. Cannot insert duplicate key in object 'ActiveUsers'. SQLState: 23000 errorCode: 2627-[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]The statement has been terminated.
DEF94239: When you edit a scheduled deployment activity, the levels deep setting is reset to a default value rather than retaining your original setting.
DEF95564, DEF95565, DEF95568: When you deploy multiple root folders and choose the Use temporary folders option, deployment may fail with the following error:
"Not able to rename the temporary directory: null to the [directory] directory"
In the worst case, when deploying three or more root folders, the entire target Website may be deleted and only the temporary files will remain.
Additionally, if the deployment termination level is set to only fatal errors, the deploy log will incorrectly state that the deployment completed with errors, when in fact it failed.
DEF102027: Folder and Asset deployments do not remove expired or deleted assets.
DEF104153: The deployment process may abort with the following error:
The deployment process failed null error: null no parent folder problem
DEF77233: Large FTP file operations do not fail when the timeout limit is reached. Instead, the operations proceed until they appear to have completed and then report the error that the operation failed.
DEF105316: When you deploy a file from Contributor, the Number of levels to deploy during single asset deploy setting is not honored. The options instead always defaults to Selected files, no references.
DEF96737: After a new asset has been uploaded via WebDAV, deployment of changed assets fails when the deploy map is set to only deploy latest versions of assets.
DEF72571: Deployment performance is poor until the /cmsessions folder is cleaned up. Collage needs to clean up this folder in order to improve deployment performance.
DEF102150: When displaying thumbnails in a folder that contains a large number of files, the Tomcat server stops responding and displays the following error:
Too many open files
DEF102573: When you check in multiple files using the Firefox browser, no scroll bar is visible on the dialog box when you enter a check-in comment. This makes it difficult to click the OK button.
INT103001: If you choose German or French as the default language when you initially log in to Collage, "invalid format" errors occur when you attempt to set start or expire dates on assets. To work around this issue, you must log in twice; first in English, and then again in German or French.
DEF78755: When you verify links, the following error is returned on a valid external URL:
Error: null
DEF80194: UI performance deteriorates significantly as the NEB_LC.TXT logfile increases in size.
DEF80893: Scheduled link verification activities hang on the final link. The only solution is to restart Collage.
DEF87057: A NullPointerException error may be thrown when multiple users attempt to log into a project at the same time.
DEF88241: When you choose to preview the deploy master-page while previewing an asset, the preview replaces the main Collage window instead of appearing on the current preview page.
DEF89144: When the Clear Type font display option is enabled in Windows XP, toolbar buttons in Collage appear bold and difficult to read.
DEF90082: When you finish editing a contribution document or other asset and check it in, the main Collage window does not refresh and display the correct status of the asset. The asset still appears checked out.
DEF90096: Collage cannot verify links when the paths include spaces.
DEF90122: Collage sometimes reports links as bad even when they in fact work fine, due to connection timeout issues.
DEF90411: When you choose the database type for a new database server (from System | Setup | Database Servers), the dialog box only mentions Oracle 9i. It should also mention Oracle 10g.
DEF90506: Absolute URLs to website roots are not correctly prefixed with the full URLs.
DEF91096: Valid high ASCII ISO-8859-1 characters that displayed correctly previous to version 5.1 of Collage are incorrectly encoded after upgrading to Collage 5.1.
DEF91764: In the Firefox browser on Macintosh clients, large gray blocks appear on each of the view titles in the main Collage window.
DEF92538: The browser status bar is missing when you preview an asset.
DEF94726: The search feature on Oracle based projects does not return all expected results.
DEF101866: The Move Asset dialog box does not display scroll bars with the Firefox browser.
DEF102867: Deploy backup does not always transfer all of the DDF files. This results in an incomplete project structure when importing these files.
DEF103696: If you copy an asset and later copy another asset within the same Collage session, the assets from both copies will be copied to the second location.
DEF105027: The French edition of Collage includes a mis-spelling on the New Folder button: the button reads Nouveau dossierr when it should read Nouveau dossier.
DEF105541: When you create a new folder from the Content | Deploy Folders view, under the /System/Links folder, no folder icon displays.
DEF106629: When multiple users log in at the same time, the following deadlock error occured:
WRN 2006/12/15 11:18:04 EST-- Storage: Storage.SetUserPrefs-SQLState(40001),SQLException:[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Transaction (Process ID 52) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. SQLState: 40001 errorCode: 1205
DEF79753: When you perform a deploy backup, nodes in a site structure that represent external links are deployed as asset IDs when they should be deployed as links. This results in errors when you restore site structures from deploy backups.
DEF88071: When you delete an asset that had previously been included in a site structure definition, the reference to the deleted asset remains in the source code of the .site file. This results in the following error durring deployment:
error: refers to asset in recycle bin [filename]
DEF79429: If you log in to Collage using case that is different than what is defined in LDAP, the following error appears when you attempt to check in a file after modifying its metadata from the Properties screen:
Failed applying metadata
Asset already checked out by [user]
DEF89880: If you log into Collage using case that is different than what is defined in LDAP, you cannot check in multiple files at one time.
DEF90145: If you log in to Collage using case that is different from what is defined in LDAP, the following error appears when you add new nodes to a site structure:
Asset checked out by another user
DEF91774: If you log in to Collage using case that is different than what is defined in LDAP, the following error appears when you upload a document for which metadata fields are required from the Content | Contribution view:
Failed applying metadata - Asset checked out to [user name]
DEF91776: If you log in to Collage using case that is different than what is defined in LDAP, the following error appears when you attempt to update metadata for a document from the Contribution Editor:
Failed applying metadata - Asset checked out to [user name]
DEF93543, INT96817: When you log into Collage using Active Directory authentication with a multi-domain configuration, the following error appears in the Tomcat log:
LdapContextManager -> authenticateUSer() userDN
java.lang.Exception: Cannot connect to LDAP server [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece ]
at com.merant.ldap.LdapContextManager.getLdapContext(LdapContextManager.java:436)
NOTE: You must set the "Root" option in Collage to the parent domain common to each child domain and the "LdapRerral" option must be set to "follow". In a multi-domain environment, LDAP will return the user references in child domains in the form of a URL to the entity. The "follow" option, tells Collage to "follow" that URL to find the user.
DEF67610: Error messages appear stating that a metadata field is required, even when a default value for that metadata field is already set. No error should appear unless the field is blank.
DEF67612: Metadata fields of type custom do not enforce the Required setting.
DEF69656: Boolean and list metadata field types are incorrectly given a default value, even if no default value has been defined. If the fields are required, this allows documents to be saved without requiring users to enter the correct value.
DEF85401: You cannot import users from the users.xml file if a user’s password includes an ampersand (&) character.
DEF101027: When a project group is deleted form a Microsoft SQL project, the following error appears and the group is not deleted:
Failed to remove groups. Storage. 8/9
DEF108632: After a user is denied permissions to a folder within a project, that user is then unable to log in to that project. The following error appears:
A project error occurred - please contact your administrator
Read/Use not granted for /System/Internal Editor Setup/AllowedFilterHTMLTags.xml to user1
DEF64807: When creating new tasks, Collage allows users to choose from any task template, including task templates for which the users do not have read / use permission.
DEF89882: You cannot upload a directory while working in context of a task.
DEF87835: The AIX Deploy Agent installer should be renamed to include the .bin file extension.
DEF87968: When installating to MS SQL using an existing Admin database, the database owner’s password is displayed in plain text.
DEF88332: The MS SQL 2000 database path dialog box is confusing, as it implies that you must enter the complete network path from the Collage server to the location of the MS SQL server.
DEF95302: After upgrading to Collage 5.1.1 on Linux, the Sybase and Tomcat port number is not preserved and Tomcat may not start.
Sun Technology Licensing Information
This product includes code licensed from RSA Security, Inc. Some portions licensed from IBM are available at http://oss.software.ibm.com/icu4j/.
Solaris: Collage Uses Public GNU Commands
Serena Collage uses the "cp" and "bash" GNU tools that are protected under the GNU Public License. This license agreement states that you have the right to access the source code for these tools. The source code for these two commands can be found online.
End Release Notes
Copyright © 2006-2007 Serena Software, Inc. All rights reserved.