AquaLogic Interaction Publisher 6.3 - released October 2006 for Windows, Solaris, and AIX

These release notes cover all releases of AquaLogic Interaction Publisher 6.3, including hotfixes and service packs. For information on a particular release, please go to the appropriate section of these release notes.

Release notes are occasionally updated after the release date. For the most up-to-date release notes, go to http://www.oracle.com/technology/documentation/index.html.

Refer to the Interoperability page in the Product Center at support.plumtree.com for the latest information on supported operating systems, application servers, databases, and browsers.

At the time of release, AquaLogic Interaction Publisher 6.3 supports the following:

• Operating Systems: Windows 2003 Server SP1, Solaris 8, 9, and 10 on SPARC, and AIX 5.3 on POWER3, POWER4, POWER5
• Databases: MS SQL Server 2000 SP3a, MS SQL Server 2000 SP4, MS SQL Server 2005, Oracle 9i (9.2.0.4, 9.2.0.5, 9.2.0.6 and 9.2.0.7), Oracle 10g (10.1.0.3) and Oracle 10G R2 (v.10.2.0.x)
• Browsers: Administrative Use (IE 5.5, 6.0); Contributing Use (IE 5.5, 6.0, Firefox 1.0+, Netscape 7.2); Browsing Use (IE 5.0, 5.5, 6.0, Firefox 1.0+, Netscape 4.71, 7.2, Safari 1.2+)

Refer to the Interoperability page in the Product Center at support.plumtree.com for the latest information on supported BEA products.

At the time of release, AquaLogic Interaction Publisher 6.3 supports the following:

• AquaLogic Interaction 6.1

The product distribution includes the following documents in the Documentation folder. For the most up-to-date documentation, go to http://www.oracle.com/technology/documentation/index.html.

• Plumtree Publisher has been renamed to AquaLogic Interaction Publisher
• AquaLogic Interaction Publisher 6.3 supports Solaris 10
• AquaLogic Interaction Publisher 6.3 supports MS SQL Server 2005

• EDK call to IContentItemManager.getContentItem() fails if a user that had previously published the item is deleted from the portal. (Issue #46108)
• EDK call to IContentItemManager.getContentItem() has slow redundant calls. (Issue #50954)
• Data entry templates with "default value" collection items fail with a generic database error. (Issue #51093)
• Sometimes user will see 'Database is busy' error when editing a content item. (Issue #51036)
• Content item properties are not being indexed using the proper language. (Issue #52136)
• A Javascript error occurs when linking a content item to another content item in the rich text editor whose name or folder name contains an apostrophe. (Issue #50575)
• When using ftp to transfer files to publishedcontent filesystem, Publisher will only use port 21. (Issue #44461).
• Content items crawled into KD using publisher crawler not deleted from KD after expiration (Issue #53902).
• Editing a content item linked to another content item garbles the URL in the edit pop up window. (Issue #52588)
• File Leak in .dotnet publisher EDK 5.3. (Issue #53884)

• An Uploaded document on an news item is not deleted from the search index when it is deleted from the news item. (Issue #54019)
  
• Content expiration doesn't remove content from publishing target when using Japanese character in file or folder name. (Issue #54148)
  
• Error in javascript causes 404 errors for /imageserver/plumtree/content/private/img/spacer.gificon_object.gif image request in web server logs. (Issue #54151)
  Workaround: Find navigate.js under in $PT_HOME/ptimages/imageserver/plumtree/content/private/js. Replace line 341 in navigate.js (see below):
  
  old line:
  sb.append(new MenuButton('<img src="' + portalImagePath + 'action_new.gif" align="absmiddle" border="0"><img src="' + portalImagePath + 'icon_object.gif" align="absmiddle" border="0"><img src="' + spacerGif.src + 'icon_object.gif" width="3" height="25" align="absmiddle" border="0">' + _UI_STRING.NavMenuButtonNew + '&nbsp;<img src="' + IMGURL('down.gif') + '" border="0">', "spacer3x15.gif", "actionbarText", newWorkingItemMenu.id, true));
  
  new line:
  sb.append(new MenuButton('<img src="' + portalImagePath + 'action_new.gif" align="absmiddle" border="0"><img src="' + portalImagePath + 'icon_object.gif" align="absmiddle" border="0"><img src="' + spacerGif.src + '" width="3" height="25" align="absmiddle" border="0">' + _UI_STRING.NavMenuButtonNew + '&nbsp;<img src="' + IMGURL('down.gif') + '" border="0">', "spacer3x15.gif", "actionbarText", newWorkingItemMenu.id, true));
  
  offending fragment:
  <img src="' + spacerGif.src + 'icon_object.gif" (concatenates spacer icon with icon_object)
  
• Cannot enter text into the Rich Text Editor for Content Canvas when IE Explorer "Show friendly HTTP error messages" is checked. (Issue #54045)
  Workaround: This problem is caused by a flaw in Internet Explorer. Under the Tools | Internet Options | Advanced | Browsing section, there is an option for "Show friendly HTTP error messages." This option somehow causes the iFrame to fail. Uncheck the box to prevent the error.
  
• Adaptive Tag is broken at switching WYSIWIG to HTML editor. (Issue #54748)
  
• Publishing a content item does not always set the item to status Published the first time. The status is set to Publish the second time the publish is attempted. (Issue #54749)
• It is not possible to re-publish an item to a Knowledge Directory folder different than the folder to which the item was originally published. (Issue #45903)
• Object category names containing spaces and non-ASCII characters on the Advanced Settings screen of the portlet configuration editor for published content portlets are not properly escaped. (Issue #46013)
• Child folders whose ACLs are emptied and inheritance settings are disabled automatically revert to inheriting security from parent folders. (Issue #46676)
• Content items published to the Knowledge Directory with a comma in their name appear to be published into multiple folders. (Issue #46868)
• Images uploaded to the rich text control have incorrect target URLs if LTCUserRelativeURLs is set to true and if images are published to an alternate image publishing target. (Issue #47402)
• Object migration is not supported in Firefox 1.0+. (Issue #47500)
• Sorting by "Modified On" in Publisher Explorer does not work. (Issue #47549)
• Relative URLs will become corrupted if the preview publishing target is not in the gateway space of the portlet the rich text control is opened from. (Issue #47651)
• A javascript error occurs when opening Publisher Explorer in Chinese Taiwan (zh-tw) locale. (Issue #48586)
  Workaround: Rename imageserver/plumtree/content/private/js/resources/zh-tw to imageserver/plumtree/content/private/js/resources/zh_TW (i.e. change folder name zh-tw to zh_TW)
• Preview of folders gives a 404 error when directory browsing is disabled. (Issue #48505)
• Chinese Taiwan help files are not accessible. (Issue #48586)
  Workaround: Rename the "zh-tw" help file folder (imageserver/plumtree/content/private/helpl/zh-tw) to imageserver/plumtree/content/private/helpl/zh_TW.
• Publisher and Workflow images are missing when the Portal server has SSO enabled (SiteMinder 6.0.2.05 and Apache 2.0.53). (Issue #49324)
  Workaround:
  1. Log in SiteMinder Policy Server Admin Console
  2. Find and open the Agent Conf Object under System
  3. Iin Parameter Name, find BadUrlChars
  4. Remove ""//"" from the Value string
• WebDAV fails with Apache front end and WebSphere configuration on AIX. WebDAV/WebEdit functionality is not available on AIX when running an Apache front end with WebSphere. (Issue #49340)
• Data Entry Templates with "Date" type properties do not convert the time to the user's locale when creating a content item. (Issue #53973)
• On UNIX systems, locale information is not being set correctly in the Publisher service.conf file. To enable UTF-8 characters, the following modifications need to be made to the $PT_HOME/ptcs/6.2/settings/service.conf file. (Issue #48284)
  Workaround:
  
  On Solaris and SUSE environments:
  1) Modify the line starting with "set.LANG" to read set.LANG=en_US.UTF-8
  2) Modify the line starting with "set.LC_CTYPE" to read set.LC_CTYPE=en_US.UTF-8
  
  On AIX:
  1) Modify the line starting with "set.LANG" to read set.LANG=EN_US.UTF-8
  2) Modify the line starting with "set.LC_CTYPE" to read set.LC_CTYPE=EN_US.UTF-8
  
  Also, be sure to install any necessary operating system patches needed to support UTF-8 characters.

• The installation guide has been updated with the following information: users should republish their published content after they upgrade from Content Server 5.x to Publisher 6.3. (Issue #55376) December 11, 2006