This release includes the following changes. You can always download the latest TeamPage release from /share/customer/dist/latest.
• Fixed a major problem for users of Microsoft Internet Explorer version 7 that caused the content area to be collapsed in rich text edit mode, making it impossible to create a new article or edit an existing article using IE7. This affected the Create New Article, Edit Article, Add Comment and Email Reply popup views. This only affects upgraded TeamPage installations, and only those that have ever run a version of TeamPage in the approximate range of 3.7.1.3 through 3.7.2.0.9.1 (October, 2006 through February, 2007). (Server42286)
• Fixes a bug related to updating the full text index used for wiki name completion in the Insert / Edit Link dialog's "Link to a named page" panel and the "Choose Name to Add" dialog. If a wiki name were changed during an edit to a named article, subsequent wiki name auto-completion searches would either include a result for that name that made it appear the name belonged to the wrong project, or would not include a result for that name at all. (Server42565)
• Fixed reporting of certain mail configuration problems in the Email Articles view. Previously, certain mai configuration problems were not reported properly, which made it appear as though clicking the "Send" button had no effect, but without reporting that there was any problem. (Server43014)
• Fixed resizing of the Email Articles view's log message content area in both rich text and plain text edit modes. In rich text mode, the dynamic vertical resize control also used in the inline comment form is now present; and in plain text mode, the vertical expander tool now works correctly. (Server43013)
• Fixed a regression introduced in 4.1 from 4.0 that caused the server administrator's selection of the "Shared Article Templates" setting on the Server Setup | Email page's Composition not to take effect until the server were restarted or until its caches were cleared. (Server43008)
• Changed the Email Articles feature so that the moderation status of the resulting article reflects the default status -- either published or draft -- of normal new articles in the project in which the article is posted. (Server38835)
• Fixed the behavior of the "emails" reference type for the "Reference Types to Be Displayed as Comments" setting. Previously, when the Email Articles feature was used but the log message was not saved, the generic but empty article titled "Emailed Articles" was still displayed as a comment on the articles that were emailed. Now, only the email articles records that have log messages (and therefore some article content to display) are displayed as comments on the articles that were emailed when the "emails" reference type is included in the "Additional Comment Reference Types" list. The "Reference Types to Be Displayed as Comments" setting is located on the Personal Setup | Preferences page on the Comments tab. (Server43035)
• Fixed a bug in the section list editor, used to edit newspage, frontpage, and other lists of sections, that caused the selection of "Current Project" to be hardened to the actual current project when editing sections for a specific project's newspage or sections for an article to be posted in a specific project. (Server42766)
• Fixed a bug in the section list editor that caused the selected sort option, such as "Alphabetical by Title" or "Oldest First", for an existing section to revert to the default sort option for the type of section being edited. (The selected sort option was still correctly and expressed correctly when the section was viewed.) (Server43046)
• Repaired the way that the Traction TeamPage system decides the content-type or mime-type of files that are uploaded or received as email message attachments. Applicable file extension to mime-type mappings in the mime.types file are now correctly preferred to the content-type sent by the browser or email client. Previously, a regression had caused file extension to mime-type mappings to be ignored in favor of what was sent by the browser. This could cause files previously uploaded or received to be sent with the wrong mime-type when requested by a user, which could result in the wrong application being opened or the wrong action being taken by the browser when the file was downloaded. (cvs35527, cvs35528, cvs35529)
now works correctly. (Server43013)