• Fixed a problem with the way project settings are managed. This particularly affected the Posting Comments to Other Projects setting's "Default (Comments Can Be Posted to Any Project)" option, resulting in the target project for posting comments to be incorrectly restricted to the moderation project. (Server42647)
• HTML comments that appear in incoming email messages are now stripped out before the message content is posted as the body of a TeamPage article. In TeamPage 4.1.2.3, a similar change was made that affected content copied from Microsoft Word and other Microsoft Office applications into TeamPage's interactive editors. This change addresses a similar problem that affected incoming mail messages from Microsoft Outlook. (LiveBlog2499, Server42466)
• The "Limit results by project" selector control that appears in FAST search views for users of Microsoft Internet Explorer 6 is now hidden when any of the navigator frames (for "Keywords", "Projects", "Labels", etc.) are being displayed. This prevents the selector control from appearing on top of the navigator frame (which is the result of a well-known limitation of the HTML SELECT element in Internet Explorer 6). (Server42595)
• Changed the rendering of by-name links so that the user viewing the article in which the link appears must have at least Access permission in the name's project in order to see a link instead of just plain text. (Server42890) Links using names from the "global" scope still always render as links.
• When a user visits a name style URL, such as teampage.traction…, and either the user doesn't have at least Access permission in the project identified in the URL (e.g., Doc) or the project doesn't exist, the user will be redirected to a login form (or to the other appropriate page if a single sign-on setup is configured) with a message explaining that either the project doesn't exist or they do not have permission to see it. Previously, they would be directed to the parallel page scoped to some other project that they happened to be able to see -- either a page explaining that the page could not be found in the other project, or the article with that name if it happened to exist in that project. In any event, the existence of a project the user should not have been able to know about would not have been confirmed or denied; but the resulting page could be confusing. (Server36222)
• Fixed a problem that caused the default entry style for a project to supercede an existing entry's already selected entry style when editing. The selected project's default entry style now correctly applies only to new articles. (Server42897)
• Re-organized the toolbar layout of TeamPage's embedded rich text editor. This was done primarily to prevent content from being obscured by the right sidebar in Mexico and other skins when a page is being viewed on a display of 1024x768. (The inline comment form that appears at the bottom of most single article views could cause the middle column to expand enough that it would extend beneath the right column.) (Server42436)
• Fixed a problem with the way files are moved across different volumes or file systems. Some customers have reported problems installing licenses and plug-ins (on the Server Setup | Plugins page, you may have seen the message "Could not move the uploaded file to the plugins directory). This fix should address that problem. (Server42247)
• Removed unnecessary thread synchronization code that lead to reduced concurrency. (Server42931)
• Fixed a bug in loading of template articles that caused the labels loaded to be only those labels from the template article's project. Labels loaded with a template article, for the entire article and for individual paragraphs, should be all the labels from projects in which the user creating the new article has either Author or Change Labels permission. (Server42973)