Title: TeamPage 6.0.06

This article describes what's new in Traction® TeamPage 6.0.06. Features include: Improved support for IE 11; Proteus skin support for IE 8 browsers with Compatibility Mode selected; Developer SDK improvements. This release also includes additional internationalized interface elements and Japanese language translation, as well as bug fixes.

Download TeamPage 6.0


Bug Fixes



• Fixed a bug that prevented the creation of a new TeamPage user account for users signing in for the first time using an external security principal that has "Login" permission in TeamPage. (Server72573)

• Fixed a bug that caused entries from inactive spaces to be returned in all space queries until the TeamPage server was restarted or had its caches cleared. (JPBO3131)

• Fixed a bug that caused daemons (configurable periodic background processes) to be started when the TeamPage server's caches were cleared even if an administrator had specified that daemons should not run at all (a rare but possible configuration seutp). (Server72631)

• Fixed a bug that caused an error to be displayed when viewing an entry which is a comment on a paragraph in another entry when that specific target paragraph had been removed. (Server72605)

• Fixed a bug in the classic PDF export feature that prevented PDFs being generated when one or more entries being exported include ordered or unordered lists. (This issue affects the classic PDF export feature only, which is an optional plug-in that must be manually installed. It does not affect the new PDF export feature that was included in the first release of TeamPage 6.0.) (Server72572)

• Fixed a bug that could cause cookie values to be scrambled when using certain types of HTTP redirects. This issue was never observed (and is not likely to have ever materialized) in any customer's TeamPage environment, but could be a problem in certain specially configured servers. (Server72597)

• Fixed a bug that caused the Print Version URLs for some of the subtabs for a specific project or milestone to point to the wrong view. (Proteus10923)

• Fixed a bug that caused some setting editors on the Server Setup > Defaults page's Space Settings > Display subtab to appear twice in the page, possibly leading to corruption of some setting values. This bug was only present in TeamPage installations that did not have an active Attivio Search support plug-in, and is therefore unlikely to have occurred "in the wild," since the TeamPage 6 installers always install an Attivio Search support plug-in. (Server72507)

• Created a GWT version of the Status Update form so that the correct form can be launched via the "Add" button when the "Status Update" article class is selected in the section's configuration. (Proteus10915)

• Fixed a bug that caused an error message to be displayed to a user who canceled a reply in a Status Updates view. (Server72349)

Features



• TeamPage now has full support for Microsoft® Internet Explorer® version 11. Previous versions of TeamPage were functional with Internet Explorer, but some features that are specific to Internet Explorer may have been missing. (Server72578)

• TeamPage's most up-to-date user interface -- the Proteus skin -- can now be used by users of Microsoft® Internet Explorer® version 8 even when "Compatibility Mode" has been enabled. Previously, having "Compatibility Mode" enabled for a TeamPage site would cause TeamPage to treat those requests as coming from an Internet Explorer version 7 browser, which, as of TeamPage 6.0, is no longer supported by the Proteus skin. (Server72554)

• Added a space setting to the Section Table plug-in that allows space administrators to choose whether, by default, the section table controls for expanding and collapsing the rows for individual entries will be displayed. This is an option that should be considered by TeamPage administrators whose users are copying the contents of section tables to be pasted into spreadsheets. (Server72472)

• Internationalized a few user interface elements, such as the "Templates" menu heading that appears in most standard forms, which had been previously overlooked; and provided Japanese l10n in addition to the English l10n. (JPBO2943 / JPBO2971)

• Internationalized the Section Table Widget, Source Code Widget and Embed Widget plug-ins. (Server72541 / Server72634)

Developer



• Made a minor but useful change to the way that the class= attribute value is generated for the BODY tag as users navigate around the Proteus skin to take into account view type specific class names for views focused on a single inactive space. Now, in that case, rather than just a single class name -- e.g., "view-foo-inactive" -- the BODY tag will have two class names representing both the view type specific class name and the view type specific "inactive space" class name -- e.g., "view-foo" and "view-foo-inactive". This may make it easier for developers to write view type specific CSS rules, since they will no longer have to write them to cover both the view type specific class name and the view type inactive space specific class name. (Proteus4486)

• Pursuant to the issue described above related to Print Version URLs for subtabs of a specific project or milestone, we have reorganized and cleaned up the GWT-RPC skin view configuration files for views specific to single projects or milestones. The most important change is the addition of two abstract GWT-RPC view configuration files, from which all views for project and milestone subtabs now inherit (directly or indirectly): project_base.properties and milestone_base.properties. Previously, all single project and single milestone specific view configuration files inherited from the project_dashboard.properties and milestone_dashboard.properties files. This meant that the descendant view configurations ended up including some properties related to aspects they didn't really have in common with single project or milestone dashboard views. This improper inheritance hierarchy sometimes led to unwanted behaviors that could be awkward to override. The new abstract view configurations contain only those properties that genuinely apply to all single project and single milestone specific views, making the built-in view configuration files cleaner, and making it easier for developers to implement the views that go with custom subtabs for single projects or single milestones. (Proteus10923)



Article: Customer4513 (permalink)
Categories: :Doc:changelog, :Doc:R60
Date: June 2, 2014; 3:52:45 PM Eastern Daylight Time

Author Name: Dave Shepperton
Author ID: shep