Title: TeamPage 6.1.20

Traction® TeamPage 6.1.20 is focused on bug fixes and a few other improvements. Some bug fixes may be of particular interest to international customers who may have space names, file names, and other data whose names or titles include non-ASCII characters.

Download TeamPage 6.1


Bug Fixes



For Customers Using the Legacy "File attachment store"



• Fixed a regression introduced in TeamPage version 6.1.19 that prevented users from being able to download attachments whose names contain non-ASCII characters from a TeamPage journal still using the legacy ("file") attachment store. (Server82487)

Other Bug Fixes



• Fixed a bug related to some URL encoded URLs that prevented a TeamPage server from properly resolving certain links when they contained URL encoded characters. For example, a permalink to an entry belonging to a space whose name contained non-ASCII characters would send the user to a search page rather than to the single entry view of the target entry. This bug was likely a regression introduced in a recent version of TeamPage. (JPBO12661)

• Fixed a bug related to the sorting of results from tag-driven queries which in some cases would prevent the containing page from loading properly and the error message "java.lang.IllegalArgumentException: Comparison method violates its general contract!" to be displayed to the user. (Server66911 / Server82504)

• Fixed an issue that could cause requests for previous versions of a file stored in a TeamPage journal's WebDAV-compatible file repository to fail with an error message such as "java.lang.ClassCastException: tsi.file.webdav.slide.ArchiveRequest cannot be cast to tsi.http.TsiServletRequest." Requests to the "archive" for previous versions of files that are under version control should now be handled normally. (Server81993)

• Fixed a bug that prevented users who did not have "Modify Account" permission (i.e., permission to modify the configuration settings for their own account) from being able to set a new password when an administrator required them to choose a new password. The permissions model underpinning TeamPage's SDK has long reflected this special exception to the general rule that the "Modify Account" permission is required to make any changes to one's own account settings, but users will now be able to access and use the user settings > password page in this situation in order to actually be able to choose a new password when the administrator has required them to do so. (Server82482)

• Fixed a bug which could prevent a user whose account was configured to require them to change their password from accessing the login form from a certain URL when they were already logged in. (Server82342)

• Fixed a bug that prevented Children editor dialog, used to add or remove children from an article to create a hierarchical tree of articles, from showing any existing children in some cases when there were sufficiently many names already bound to an existing article or in-progress new article. (Server82007/Proteus14273)

• Fixed a bug that prevented tasks marked as due at exactly 12:00 midnight on a particular day from appearing in Calendar views. The bug, but would only have been visible to users of TeamPage servers which have the "Support for Times in Project Management Form Date Fields" (com.traction.pmtimes) plug-in. (JPBO12945)

• Fixed a bug that could prevent the Manager view from displaying properly, which in turn could prevent administrators from being able to clear all currently active sessions. (Server82131)

• Fixed a long-standing issue for users of premium search that could prevent articles, comments or other entries from being removed from an external search engine index when they were deleted. All versions of deleted entries are now correctly removed from an external search index on deletion. (Server53212)

• Fixed an issue that caused tags that had previously been entered into a section definition's Tags field (which is only visible when a tag-driven section type has been selected) from improperly having some effect on that section even if its type was changed to a non-Tag based type. In particular, the tags would appear in the Tags field of any form launched from that section's "Add to Section" link. (Server81994)

• Fixed a bug that prevented the "Event Duration" column from displaying the length of an event in a Section Table widget at a resolution finer than day. The "Event Duration" column will now display the length of the event to the nearest minute. (JPBO12757)

Other Changes



• The keyboard shortcut for deleting the currently selected entry has changed from Backspace to Delete. (Server82021)

• The delete confirmation message has been modified to refer to the ID of the entry being deleted, making it easier for users to know for sure that they're deleting the entry they intend to delete. (Server82033)

• If you reply to an article, comment, status update, or other entry, any in-page notifications you have received pertaining to that entry will automatically be marked read. This is useful when you reply via the Status Update page, or by replying to an email notification message, or some other way that doesn't already involve viewing the entry in a way such that the TeamPage service considers those notifications read. (Server82165)

• Performance of some general file I/O operations has been improved.

• Some files that pertain to older versions of the Attivio premium support module are now correctly removed on startup when they're present. Any (spurious) warnings you may have seen in your TeamPage server's console output pertaining to such files will no longer appear. (The latest versions of any of these files are now -- and have been for some time -- contained entirely in the appropriate plug-in package.) (Server82010)

i18n/l10n



• Some Japanese localizations, including the title for the "Today by Project" sub-tab of the User Profile > Tasks tab and the "Discussion Thread" tab that appears near the bottom of most single entry views, has been improved. (JPBO12883 / 8af8206c1c78 / a9cae0aee506 / e79734feeaa4)

• Some Section Table column display names have been internationalized, with English and Japanese localizations. (JPBO12999)



Related Articles
referenced by (1)
Customer4962: TeamPage 6.1.24
references (1)
Customer4941: TeamPage 6.1.19
Article: Customer4948 (permalink)
Categories: :Doc:changelog, :Doc:R61
Date: September 23, 2016; 9:43:43 AM Eastern Daylight Time

Author Name: Christopher Nuzum
Author ID: cjn