Traction® TeamPage version 6.1.16 is focused on a small set of bug fixes and improvements, particularly some related to TeamPage's handling and display of attachments and other files.
• Fixed a longstanding limitation that could cause various problems when a user renamed an attachment. Previously, when the file name of an attachment was changed, TeamPage would report the file as missing when listing it in the parent entry's attachments, and generated URLs intended to be used to link to the renamed attachment would generate HTTP 404 (Not found) HTTP response errors. With this change, TeamPage now handles renamed attachments correctly in all contexts. (Server81274)
• Fixed an issue related to how TeamPage generates redirect URLs when sending an HTTP 302 response code. Previously, these URLs would be fully qualified using the same host or IP address from the HTTP request "Host:" header even when the server had been configured to force fully qualified URLs to use the address the server advertises for itself configured on the server settings > network page. The "Always Use Server Base URL instead of Host Header for Fully Qualifying URLs" setting is now respected in this context. This setting may be relevant to customers who deploy their TeamPage server behind a reverse proxy server. (Server81341)
• Fixed a bug likely introduced in TeamPage 6.1.13 which caused the URLs generated to refer to search results to be incorrect and/or broken. These URLs are once again being generated properly. This issue might have been noticeable to customers who use certain customizations involving summary reports on search results from external search engines, in which case these URLs were used to link from the summary to actual pages of search results. (Server81295)
• Fixed a bug that could cause an error to be reported in certain document folder views, such as the view of a folder that contains an individual attachment, or other parent folders in the hierarchy used in the URI/URL "path" for attachments and entry shared files in TeamPage. When viewing these folders, (Server81330)
• Fixed a bug that prevented a custom relationship type from being correctly created and applied in the advanced relationships editor dialog that can be launched from some TeamPage forms. Custom relationship "verbs", for those users who are allowed to create them, are now correctly created and the relationships involving these newly created relationship types are correctly applied when submitting a new entry or an update to an existing entry. (Server81298)
• Fixed a bug that could prevent the "Delete..." link from appearing in a documents view when the user had selected one or more files or folders that they had permission to delete. (Proteus14199)
For Developers
• The com.traction.sdk.TractionUrlGenerator class's setSkin method has now been modified to accept a String instead of an actual com.traction.sdk.skin.Skin object. This is convenient for modifying the Skin whose rules are to be involved in generating URLs by its logical name (e.g., "proteus" or "simple"), since arbitrary Skin objects are not actually accessible via the public SDK. In conjunction with this change, the url.urlgen tag has been modified to accept an optional skin= attribute that can be used to indicate a value to be passed to the TractionUrlGenerator's setSkin method so that the current TractionUrlGenerator's skin can also be set from SDL. The url.urlgen tag's noskin= attribute continues to work as it has, but is ignored if the skin= attribute is specified. (Server81326)
• The ReferenceBucket and LabelNameBucket classes in the com.traction.sdk.data package have been modified so that methods that formerly returned Iterables over com.traction.sdk.References, com.traction.sdk.LabelNames or com.traction.sdk.Labels now return the appropriate type-specific Iterators from the com.traction.sdk.iter package, i.e., ReferenceIterator, LabelNameIterator and LabelIterator. If you have custom code that makes use of these APIs, you will need to modify your code. Please file a support request if you need assistance with this migration.
• The com.traction.sdk.Journal class's getFile method and the com.traction.sdk.file.AttachmentStore class's getFile method have both been modified so that if the URI of the requested File resource refers to an attachment to an entry, a backing store-specific fully functional instance of com.traction.sdk.Attachment will be returned. Previously, sometimes the File returned for attachment URIs would either not be an instance of a class that correctly and fully implemented the Attachment abstract class's API, or would not be an instance of Attachment at all. (Server80185)
• The com.traction.sdk.Journal class's getWebdavFile method has been removed. If you have custom code that makes use of this API, you will need to modify your code. Please file a support request if you need assistance with this migration.
• Furthermore, TeamPage now correctly identifies the com.traction.sdk.search.DocumentType that should be associated with various types of com.traction.sdk.File objects, and correctly generates document IDs for all the various subclasses of com.traction.sdk.File, including when the file in question represents a directory. (Server81330)
• TeamPage's widget editor dialog now uses an automatic and extensible grouping mechanism instead of hard-coded layout of available insertable widgets. You can put your custom widgets into one of the standard groups using the group= configuration property for your htmledit TokenRenderer (the standard groups are "html", "media", "traction", "web" and "other". Widgets automatically go into the "other" group if the htmledit TokenRenderer does not have a group= property. You can specify a priority= value (generally from 0 to 100) to position your widget in the list relative to others in the same group; widgets are listed in descending order by priority. You can also add your own group names, and give them display names by adding a .properties file with the desired logical name to your plug-in's config/misc/widgetgroups directory (set the display_name= property to specify the heading text to use for your group). (Server81262)
Article: Customer4917 (permalink) Categories: :Doc:changelog, :Doc:R61 Date: May 22, 2016; 1:48:46 PM Eastern Daylight Time
