Title: TeamPage 6.1.11

Traction® TeamPage 6.1.11 is focused on fixing a handful bugs and issues. Please read this entire change log to find out if there's a fix or change related to an issue that affects you.

Download TeamPage 6.1


Bug Fixes



• Fixed a javascript bug that was a regression introduced in TeamPage 6.1.10 that could prevent changes to server-level ACLs from being applied. (bcc25a584025)

• Fixed a bug with the inline comment form that prevented images or other media uploaded via the various rich text dialogs (Insert Image, Insert Media, Insert Widget, etc.) from being properly attached to the resulting comment. (fd69d887a995)

• Restored the appearance of the "Only include posts by this user" checkbox in the section configuration interface when appropriate (generally for user profile or digest subscription sections). (Server80003)

• Updated the version of the Jetty web server to a more recent version to pick up various fixes and improvements. This includes a fix for a concurrency issue in the Jetty codebase pertaining to tracking session data associated with user authentication, which was an error that was recorded in some TeamPage deployments' log files (although it is not known at this time whether this resulted in any user-visible effects). (Help11105)

• Fixed two issues related to the use of the special built-in "Owner" account. (The Owner account is only available on a temporary basis with the use of a special license file that has to be created for a particular journal.) (Server80033 / Server80038)

• Fixed a bug that prevented the proper set of feedback details from being included with feedback reports generated from the Help > Send Feedback item in TeamPage's normal (Proteus skin) user interface. (Server80058)

• Fixed a possible Javascript issue in the classic edit views still in use with retired skins, and in for the expanded status update and comment forms. (This issue was reported by a customer using Internet Explorer with the Mexico skin. If your TeamPage deployment is still using an old skin, and not the Proteus skin, we strongly encourage you to switch to the Proteus skin. Older skins are no longer maintained; and the most recent of the old skins, while still available in the com.traction.classic plug-in, was officially retired in TeamPage 6.0.10. We also encourage users of Internet Explorer versions 10 and earlier to upgrade to version 11 or to the Edge browser, as earlier versions of Internet Explorer will no longer be supported starting in January of 2016.) (JPBO10433)

• Fixed a bug that prevented the "New Separator" action from creating separator entries (it would instead create ordinary articles). (JPBO10469)

• Fixed a bug that caused certain types of sections to erroneously appear in the context menu's "Add to Section" sub menus. The "Add to Section" feature only works for sections that are based upon "Tag" or "Tag Added" queries, and work by adding the appropriate tags to the target entry. (Server80137)

• Fixed the handling of errors reported by the server when using the context menu to perform tag change operations. Previously, when such errors happened, there was either no feedback to the user, or, in the case of such operations performed from a single entry view, the entire contents of an HTML page intended to be displayed by itself to the user to explain the error was inserted into the side column, causing chaos with the page layout. The user will now see a simple alert dialog explaining the error. (Server80139)

Other Changes



• Users will no longer receive email or other notifications pertaining to the special "proxy" entries that are created when using various SEW (Social Enterprise Web) features such as commenting on or sharing an external web page in TeamPage. Also, users will not receive notifications for any file-related activities related to those proxy entries or to template entries. (See also "For Developers" below.) (Server80111)

• The Attach Inline Images and Stylesheets digest setting is now set to yes by default, and stylesheets used in the email digest will now be included inline in the HTML document (using STYLE tags in the HEAD) generated for the message body. This is intended to improve the experience for users of some mail readers such as Lotus Notes Web Mail, which may not retrieve the styles from the server when they are included via a URL pointing to the TeamPage server, or in cases where the TeamPage server may not be visible from the machine where the user is reading the digest message. (Server80110)

• The descriptions for various password requirements (e.g., minimum length or minimum number of special/punctuation characters) are now properly localized for Japanese. (JPBO10194)

• The placeholder text in the inline task form, "Add a new task", has been internationalized and properly localized for Japanese. (JPBO10473)

• Reduced the frequency of the appearance of the generic error message text "There was an unexpected problem servicing this request." when notifying a user of an error (and when recording these conditions in TeamPage's log files). This error message text is unhelpful, so we have made all efforts to retrieve the most detailed and specific possible error message, which will be of more use to the user and to Traction Software support staff when we are working with you to resolve an issue you've reported. The generic error message text, though, has also been internationalized and properly localized for Japanese. (Server80156)

• Moved some spurious warning logging generated by TeamPage's WebDAV repository to "informational" or "debug" logging, meaning that various sorts of diagnostic (and possibly "scary" looking information) will not appear in your TeamPage log files unless you take specific actions under the guidance of Traction Software support staff to activate it. (Server80109)

For Developers



• Event listeners may now specify explicitly whether they would like to receive events related to proxy entries that are created during SEW operations such as commenting on or sharing external web pages, or external results that appear in Attivio Search views for Attivio+ licensed customers. By default, proxy entry related events do trigger event listeners. To opt out of such events, developers may either create a custom subclass of tsi.config.ListenerConfig which overrides the wantsProxyEntryEvents (set your event listener's class= property to point to your custom class that is included in your plug-in), or simply by specifying the property proxies=false in their event listener configuration file.

• The "author_last_update" EntryField has been added to support filtering on and/or rendering the author of the last visible update to an entry. (Server80022)

• The skin.stylesheets SDL tag now supports the inline=true/[false] attribute which indicates whether the stylesheet contents should be included inline in a STYLE tag rather than by reference. The com.traction.sdk.skin.Skin class now declares a getStylesheetsHtmlInline method to handle the case of inline=true to support the case of inline=true; Skin classes that can should override this method, whose default implementation defers to getStylesheetsHtml, to generate the inline HTML equivalent of references to the appropriate stylesheets.



Article: Customer4878 (permalink)
Categories: :Doc:changelog, :Doc:R61
Date: January 9, 2016; 5:34:57 AM Eastern Standard Time

Author Name: Christopher Nuzum
Author ID: cjn