Published and released Jul 28, 2012 Traction® TeamPage 6.0.10 release follows quickly on the heels of Customer4621: TeamPage 6.0.09 to fix several disruptive issues and bugs that were discovered in 6.0.09, as well as make incremental cosmetic and functional improvements to in-page notifications. All customers who upgraded to TeamPage 6.0.09 should upgrade to this version as soon as possible.
• Fixed a regression that caused a dialog with an error message to be displayed when using NTLM authentication. Since we were not able to reproduce the underlying issue in testing, we cannot say at this time whether this issue prevented the NTLM authentication from succeeding, or whether this issue affected users of the Proteus skin. But this issue was reported by one customer in their TeamPage test environment while using the Mexico skin (the skin for an older generation of TeamPage's UI, which is still present but no longer actively developed). (Server73302)
• Fixed a regression that caused an error page to be displayed when clicking a link for one of the locales appearing on the login form. (Server73291)
• Fixed a regression that caused metrics data pertaining to full text search query terms not to be collected when using TeamPage native fulltext queries. Customers may have seen this error reported in their log file with the message "Warning: SDL SQL exception java.lang.IllegalArgumentException: No SQL to run.. See traction.log for details." along with diagnostic stack traces. (Server73315)
• Fixed a serious problem with TeamPage's GWT Javascript modules which power the Proteus skin, as well as various other administrative features. This issue is known to have caused a dialog with the following erroneous message to be displayed each time the user navigated to a page containing a form (or clicked a link or button to open a form): "The server has been upgraded. To proceed, you must reload this page. Click OK to continue. Click Cancel to stay on this page." It is possible that this issue could have caused other unpredictable behaviors which might have varied by which browser and locale the user was using. (Proteus11032)
• Fixed a bug that caused in-page notifications of edits to existing entries, as they appeared in the notifications menu, to be attributed not to the editor but to the original author. (Proteus11026)
• Fixed a bug that could cause the hover menu outline for certain types of search results in Attivio search pages to have the wrong dimensions. In some cases, such as for results representing files with more than one period in their name, parts of the hover outline would overlap the expanded search result. (Proteus11041)
• Fixed a regression that prevented further details from appearing when expanding search results for files in an Attivio search feed view. (Server73316)
• Fixed a bug that could prevent further details from being displayed for notifications of file creation events when expanding an item in the Profile > Notifications page if the file had not yet been added to the Attivio search index. (Server73317)
i18n/l10n
• Internationalized the in-page notifications menu, and provided en and ja localizations. (JPBO4017)
Other
• Added JMX metering for all significant "unified search" sources so that JMX monitoring can provide access to that information for diagnostic purposes. (Server73280)
• Modified the display of in-page notifications related to files so that the file path displayed to the user will not contain URL encoded character sequences in place of their normal unencoded equivalents. (Proteus11038)
• Stopped offering TeamPage's custom context menu in Attivio search pages for those results that don't support it. Previously, right clicking on such a search result would cause the browser to raise an alert dialog with the message "IllegalArgumentException: The context menu requires a target entry." (Proteus11021)
