• Fixed a bug that caused a character set parameter (generally "charset=UTF-8") to be improperly added to every "Content-Type" HTTP response header sent by TeamPage when serving a file, even when it made no sense for the file's media type. For example, the "charset=UTF-8" parameter would be added to the "Content-Type" response field when TeamPage was serving an MPEG-4 video file of media type "video/mp4". This could prevent some browsers from handling the file in the expected way (for example, in the case of video files served by TeamPage, Safari would be unable to play the video). The "charset=" parameter is now only set when necessary (although it will still almost always be set when serving text files, including HTML files, XML files, etc.). (cjn4531)
• Restored the editor for the server default value of the "Allow Invitations to This Space" space setting on the server settings > defaults page. (Server81668)
• Fixed an issue that could cause the display name of the associated entry type (e.g., "Project" or "Milestone") to be wrong when displayed in a Status Updates page (when displaying a status update bound to a special type of entry). (JPBO12336)
• Fixed a bug that prevented the number of results displayed in some cases for type-ahead completions for users or spaces not to be limited. This issue applied to some user or space form fields that offer type-ahead completion, inline @ mention completion suggestions, and certain other places (not including the type-ahead search box that appears at the top of any page in the TeamPage UI). The number of results in these cases is now correctly limited to 20 users or spaces. (Proteus14271)
• Modified the "Lookup User" behavior on the "Migrate Principals" admin page (optionally used when switching to a new user directory configuration for your TeamPage server/journal) to avoid an unexpected issue that could cause an error message to be displayed when looking up users, and prevent matching user accounts from being displayed at all. (Server81579)
• Fixed an issue that prevented configuration settings changes from being applied in many admin / setup pages when the currently installed license has expired or the server has otherwise entered the "violated" state (e.g., when there are too many active users or spaces in the current journal). (Server81837)
• Fixed a bug that prevented custom width and height properties from being applied to some media widgets, including "Quicktime" and "Media Resource" widgets. (Server81873)
• Fixed an issue that caused the wrong date / time to be displayed for a task's, project's or other action-oriented entry's completion date if it was created in the completed state (i.e., with the "done" tag applied at creation time), and later re-opened and re-closed. The date / time displayed would be that of the entry's original creation. With this change, the date / time will always be that of the last time the entry was marked completed. (Server81803)
• Fixed a bug that could cause the relative time an entry was created to incorrectly appear as "0 minutes ago" in certain cases, such as in the case of very recently created entries appearing a project or milestone dashboard's "Activity" area. (Server81804)
• Fixed an apparently long-standing issue that could prevent updates from appearing in some views, such as the Activity > Feed view, in some cases in which they were supposed to appear. (Server81731)
• Fixed a bug that prevented the correct file extension from being used when a user clicked the "Download" button when exporting entries to a format such as PDF. This could prevent the browser from handling the export output document properly. The TeamPage server will now set the expected file extension (e.g., .pdf for a PDF) when the user clicks the export "Download" button, just as it does when the user clicks the "Preview" button. (Server81729)
Other Changes
• Implemented a much easier editor for Section Table widgets. From now on, by default when creating a new section table widget, users will be able to choose what columns to display from a selector instead of having to manually author specially formatted JSON data to define the columns and their properties. Existing section table widgets can still be edited with the classic editor, and anyone wishing to have more customizable columns can still use the classic widget editor. Expect further improvements to the section table widget in upcoming releases. (Server75882)
• When the currently installed license has expiredor the server hasotherwise enteredthe "violated"state (e.g., when there are too many active users or spaces in the current journal), a message will be presented to server administrators on each page of TeamPage's main interface explaining the condition (in a fashion similar to the display of the same information that appears for administrators on setup pages). (Proteus11344)
• Improved handling of certain HTTP request headers as applied to GET and HEAD requests for files and other static resources by improving support for the "Range" and "If-Modified-Since" headers, and implemented handling for the "If-Unmodified-Since", and "If-Range" HTTP request headers. (Server81306)
• Properly internationalized the display of the month and year that appears at the top of TeamPage's various Calendar views. (JPBO12127)
• Internationalized the text that now appears in the "Post via Email" side box. (JPBO12383)
• Modified the Wiki space template "Bulletins" dashboard section to use "Titles" instead of "Brief" volume, and to be sorted alphabetically by title rather than in reverse chronological order. (Server81700)
For Developers
• Added support to com.traction.sdk.view.Section and the <section> SDL tag (used to define a Section on-the-fly) for index entry types. Although the section editor UI does not yet support them, the entrytypesfilter= attribute can now be used on a <section> SDL tag to specify a comma-separated list of index entry type names, and those will be used when applicable just as they would be if specified on an <entries> SDL tag. (Server81704)
• The com.traction.view.listener.notifier.transport.EmailTransport / PreferredEmailTransport now have a protected non-final method called "skipSend" with the following signature:
Subclasses of either of these classes now have a method to override whether a particular notification email message should be vetoed. The default implementation is based upon the values of the skipsend= transport configuration property, and the skipsend= and forcesend= URL parameters (all of which are generally only defined during development or testing). (Server81792)
