Telligent Evolution Platform and Applications Documentation

Email Templates

Jenny Jarrard — Thu, 09 Feb 2012 18:03:30 GMT

Current Revision posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 2/9/2012 12:03:30 PM

In Telligent Evolution 5.6, the following templates have been moved from the Web/Languages folder to the Job Scheduler/Languages folder (as noted below) and need to be modified there instead:

forumpost_mailgateway.txt
forumpost_postnotification.txt
forumpost_threadnotification.txt
weblog_newpost.txt
weblog_newcomment.txt

All of the emails sent out by the Telligent Evolution platform can be customized, both in how they look and what information they contain.

In the email templates, tokens are used to specify information. When the email is sent, the tokens are replaced by the correct values they represent (i.e., $Subject -> "Subject of blog post").

All templates are listed below along with the tokens available to the template.

How to customize an email template:

Navigate to the email template folder, which for 5.0 or 5.5 can be found in the Web/Languages/<your language>/emails folder, and in 5.6 in the Job Scheduler folder - typically c:\program files\Telligent\Job Scheduler\Languages\<language>/emails.
Find the name of the template that you want to change/edit.
The templates are stored as .txt files. Thus to change the forumpost_threadmovenotification template, open forumpost_threadmovenotification.txt in any text editor.
The list of available tokens is given below (along with the Global Terms).

Global Terms

A list of terms that are available on all templates is available on the [[The global term tokens|Global tokens]] page.

Account notifications

forgottenpasswordwithtoken.txt message file

$forgottenpasswordurl - string - The URL where the user can change their password.
$ip - string - The IP host address of the remote client.
$user - [[The user token|User]] - The user who forgot their password.

newuser_accountcreated.txt messages file

$user - [[The user token|User]] - The user who created an account.

newuser_approved.txt messages file

$user - [[The user token|User]] - The user whose account was approved.

newuser_generatedpassword.txt messages file

$user - [[The user token|User]] - The user created an account with a generated password.

newuser_pending.txt message file

$user - [[The user token|User]] - The user who has attempted to join the site and is awaiting approval.

newuser_rejected.txt message file

$user - [[The user token|User]] - The user whose account was rejected.

roleemail.txt message file

$user - [[The user token|User]] - The recipient of the message, a member of the role.
$post - [[The post token|Post]] - The post containing the message for the user.
$roleName - string - The name of the role the message was sent to.

user_changedpassword.txt message file

$user - [[The user token|User]] - The user who change their password.

user_forgottenpassword.txt message file

$user - [[The user token|User]] - The user who requested to be sent a new password.

userinvitation.txt message file

$invitation - [[The user invitation token|User Invitation]] - The invitation to the new user.
$user - [[The user token|User]] - The user who invited the recipient to the community.

userinvitation_withsection.txt message file

$invitation - [[The user invitation token|User Invitation]] - The invitation to the new user.
$user - [[The user token|User]] - The user who invited the recipient to the section/group.

Blog notifications

weblog_feedbacknotification.txt message file

$parent - [[The post token|Post]] - The blog post given the feedback.
$post - [[The post token|Post]] - The new blog feedback, which may need approval.
$user - [[The user token|User]] - The user who subscribed to new comments.

weblog_moderationthreshold.txt message file

$section - [[The blog token|Blog]] - The blog that needs moderation attention.
$user - [[The user token|User]] - Blog owner who can moderate the blog.

weblog_newcomment.txt message file

$post - [[[The post token|Post]] - The new blog comment.
$user - [[The user token|User]] - The user who subscribed to new comments.

weblog_newpost.txt message file

$post - [[The post token|Post]] - The new blog post.
$user - [[The user token|User]] - The user who subscribed to new posts.

weblog_subscriptionconfirmation.txt message file

$section - [[The blog token|Blog]] - The subscribed blog.
$user - [[The user token|User]] - The user who has subscribed to the blog.

Contact notifications

contactform.txt message file

$appTitle - string - The name of the blog or group.
$body - string - The body of the message.
$email - string - The email address of the sender.
$link - string - The URL of the home page of the blog or group.
$name - string - The name of the sender.
$subject - string - The subject provided by the user.
$to - string - The email address of the owner of the blog or group.

contactform_usertouser.txt message file

$post - [[The post token|Post]] - The message being sent.
$user - [[The user token|User]] - The recipient of the message.

Forum notifications

forumpost_mailgateway.txt message file

$attachmentUrls - NameValueCollection - A collection of urls for attachments to the post.
$charSet - string - The email encoding to use.
$list - [[The mailing list token|MailingList]] - The mailing list that the post was sent to.
$mime.EncodeHeader(string subject, string charSet) - string - The encoded subject of the post.
$parentPost - [[The post token|Post]] - The parent post of the post that triggered the notification.
$post - [[The post token|Post]] - The post which triggered the notification.
$subscriber - [[The user token|User]] - The recipient of the notification.
$subjectCharSet - string - The email encoding to use for the subject.

forumpost_messageapproved.txt message file

$post - [[The post token|Post]] - The post to the forum being approved.
$user - [[The user token|User]] - The author of the post.

forumpost_messagemoved.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The author of the post.

forumpost_messagemovedandapproved.txt message file

$post - [[The post token|Post]] - The post to the forum being moved and approved.
$user - [[The user token|User]] - The author of the post.

forumpost_messageremoved.txt message file

$moderatedBy - [[The user token|User]] - The moderator who removed the post.
$post - [[The post token|Post]] - The post to the forum being removed.
$reason - string - The reason for the removal provided by the moderator.
$user - [[The user token|User]] - The author of the post.

forumpost_notifymoderators.txt message file

$user - [[The user token|User]] - The moderator who is being notified.

forumpost_notifythreadstarterofanswer.txt message file

$post - [[The post token|Post]] - The post which was marked as the answer.
$rejectAnswer - string - The url to reject the post as the answer.
$user - [[The user token|User]] - The user who posted the thread starter.

forumpost_notifythreadstarterofsuggestedanswer.txt message file

$currentUser - [[The user token|User]] - The user who verified the post as an answer.
$post - [[The post token|Post]] - The post which was verified as an answer.
$rejectAnswer - string - The URL to reject the answer.
$user - [[The user token|User]] - The user who posted the thread starter question.
$verifyAnswer - string - The URL to verify the suggested answer.

forumpost_postnotification.txt message file

$post - [[The post token|Post]] - The post which triggered the notification.
$user - [[The user token|User]] - The recipient of the notification.

forumpost_threadmovednotracking.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The user being notified of the thread move.

forumpost_threadmovenotification.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The user being notified of the thread move.

forumpost_threadnotification.txt message file

$post - [[The post token|Post]] - The post which started a new thread.-
$user - [[The user token|User]] - The user who subscribed to this thread.

Friendship notifications

followers_notification.txt message file

$follower - [[The follower token|Follower]] - The relationship of the follower.

friendship_approved.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

friendship_requested.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

friendship_requested_nomessage.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

Group notifications

group_accessaccepted.txt message file

$group - [[The group token|Group]] - The group access has been granted to.
$user - [[The user token|User]] - The user being granted access.

group_accessrequest.txt message file

$group - [[The group token|Group]] - The group the membership request is for.
$message - string - The message provided by the user requesting access to the group.
$owner - [[The user token|User]] - The owner of the group.
$user - [[The user token|User]] - The user making the request for membership.

group_accessrequestdenied.txt message file

$group - [[The group token|Group]] - The group access has been denied to.
$user - [[The user token|User]] - The user being denied access.

group_useradded.txt message file

$group - [[The group token|Group]] - The group user has been added to.
$user - [[The user token|User]] - The user being added to the group.

Media Gallery notifications

mediagallerypost_commentnotification.txt message file

$parentPost - [[The post token|Post]] - The media gallery post the comment is for.
$post - [[The post token|Post]] - The comment to the media gallery post.
$user - [[The user token|User]] - The recipient of the comment notification.

mediagallerypost_newcomment.txt message file

Message notifications

group_messages_also_replied.txt message file

$message - [[The reply message token|Reply Message]] - The reply to the message thread.
$parent - [[The message token|Message]] - The first message in the conversation (the group message).
$recipient - [[The user token|User]] - The user that commented in the message thread.
$replies - [[The reply message token|Reply Message]] - The list of all replies to the parent group message.

group_messages_reply.txt messages file

$message - [[The reply message token|Reply Message]] - The reply to the parent group message.
$parent - [[The message token|Message]] - The first message in the conversation (the group message).
$recipient - [[The user token|User]] - The user the message who posted the status message.
$replies - [[The reply message token|Reply Message]] - The list of all replies to the parent group message.

messages_also_replied.txt message file

$message - [[The reply message token|Reply Message]] - The reply to the message thread.
$parent - [[The message token|Message]] - The first message in the conversation (the status message).
$recipient - [[The user token|User]] - The user that commented in the message thread.
$replies - [[The reply message token|Reply Message]] - The list of all replies to the parent status message.

messages_newconversationmessage.txt messages file

$conversation - [[The conversation token|Conversation]] - The conversation between the various participants.
$message - [[The message token|Message]] - The message in the conversation directed to the recipient user.
$user - [[The user token|User]] - The user the recipient of the message.

messages_newprofilecomment.txt messages file

$message - [[The profile message token|Profile Message]] - The comment on the profile.
$user - [[The user token|User]] - The user who received the comment (the profile's owner).

messages_reply.txt messages file

$message - [[The reply message token|Reply Message]] - The reply to the parent status message.
$parent - [[The message token|Message]] - The first message in the conversation (the status message).
$recipient - [[The user token|User]] - The user the message who posted the status message.
$replies - [[The reply message token|Reply Message]] - The list of all replies to the parent status message.

messages_spam.txt messages file

$message - [[The message token|Message]] - The message which has been marked as spam.
$messageUrl - string - The url of the activity message.
$spamScore - int - The score given to the message based on the spam rules.
$user - [[The user token|User]] - The recipient of the message.

messages_spam_deleted.txt messages file

$message - [[The message token|Message]] - The message which has been marked as spam.
$spamScore - int - The score given to the message based on the spam rules.
$user - [[The user token|User]] - The recipient of the message.

messages_spam_deleted_user.txt messages file

$message - [[The message token|Message]] - The message which has been marked as spam.
$user - [[The user token|User]] - The recipient of the message.

Wiki notifications

wikis_definitespam.txt message file

$page - [[The wiki page token|Wiki Page]] -The wiki page that has been flagged as possible spam.
$user - [[The user token|User]] - The user with permission to delete the wiki page to send the email to.

wikis_pageupdated.txt message file

$page - [[The wiki page token|Wiki Page]] - The updated wiki page.
$revision - [[The wiki page revision token|Wiki Page Revision]] - The previous version of the wiki page.
$user - [[The user token|User]] - The user who subscribed to updates to the wiki page.

wikis_possiblespam.txt message file

$page - [[The wiki page token|Wiki Page]] - The wiki page that has been flagged as possible spam.
$user - [[The user token|User]] - The user with permission to delete the wiki page to send the email to.

Customizing email replies to reply to the entire group whether you click Reply or Reply All

If upgrading to 5.x, you have the option of making all replies to a forum list go back to the entire group whether you click Reply or Reply all. This is a customization of the current 5.x behavior, which allows you to select replying to one member or replying all to the entire group.
1. Navigate to the email templates folder. For release 5.0 or 5.5, this will be in Web\Languages\<language>\emails\; for release 5.6 it will be in the Job Scheduler folder, which defaults to c:\Program Files\Telligent\Job Scheduler\, then continue to the \Languages\<language>\emails\ subfolder.)
2. Open forumpost_mailgateway.txt.
3. Under the line that begins with BCC:, add the following line:
```
Reply-To: <$globals.HtmlDecode($list.DetermineEmailAddress())>
```
  Setting the Reply-To will cause email clients to reply to the address listed instead of the address from which the email was sent.

Email Templates

Jenny Jarrard — Thu, 09 Feb 2012 18:00:47 GMT

Revision 18 posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 2/9/2012 12:00:47 PM

In Telligent Evolution 5.6, the following templates have been moved from the Web/Languages folder to the Job Scheduler/Languages folder (as noted below) and need to be modified there instead:

forumpost_mailgateway.txt
forumpost_postnotification.txt
forumpost_threadnotification.txt
weblog_newpost.txt
weblog_newcomment.txt

All of the emails sent out by the Telligent Evolution platform can be customized, both in how they look and what information they contain.

In the email templates, tokens are used to specify information. When the email is sent, the tokens are replaced by the correct values they represent (i.e., $Subject -> "Subject of blog post").

All templates are listed below along with the tokens available to the template.

How to customize an email template:

Navigate to the email template folder, which for 5.0 or 5.5 can be found in the Web/Languages/<your language>/emails folder, and in 5.6 in the Job Scheduler folder - typically c:\program files\Telligent\Job Scheduler\Languages\<language>/emails.
Find the name of the template that you want to change/edit.
The templates are stored as .txt files. Thus to change the forumpost_threadmovenotification template, open forumpost_threadmovenotification.txt in any text editor.
The list of available tokens is given below (along with the Global Terms).

Global Terms

A list of terms that are available on all templates is available on the [[The global term tokens|Global tokens]] page.

Account notifications

forgottenpasswordwithtoken.txt message file

newuser_accountcreated.txt messages file

$user - [[The user token|User]] - The user who created an account.

newuser_approved.txt messages file

$user - [[The user token|User]] - The user whose account was approved.

newuser_generatedpassword.txt messages file

$user - [[The user token|User]] - The user created an account with a generated password.

newuser_pending.txt message file

$user - [[The user token|User]] - The user who has attempted to join the site and is awaiting approval.

newuser_rejected.txt message file

$user - [[The user token|User]] - The user whose account was rejected.

roleemail.txt message file

user_changedpassword.txt message file

$user - [[The user token|User]] - The user who change their password.

user_forgottenpassword.txt message file

$user - [[The user token|User]] - The user who requested to be sent a new password.

userinvitation.txt message file

$invitation - [[The user invitation token|User Invitation]] - The invitation to the new user.
$user - [[The user token|User]] - The user who invited the recipient to the community.

userinvitation_withsection.txt message file

$invitation - [[The user invitation token|User Invitation]] - The invitation to the new user.
$user - [[The user token|User]] - The user who invited the recipient to the section/group.

Blog notifications

weblog_feedbacknotification.txt message file

weblog_moderationthreshold.txt message file

$section - [[The blog token|Blog]] - The blog that needs moderation attention.
$user - [[The user token|User]] - Blog owner who can moderate the blog.

weblog_newcomment.txt message file

$post - [[[The post token|Post]] - The new blog comment.
$user - [[The user token|User]] - The user who subscribed to new comments.

weblog_newpost.txt message file

$post - [[The post token|Post]] - The new blog post.
$user - [[The user token|User]] - The user who subscribed to new posts.

weblog_subscriptionconfirmation.txt message file

$section - [[The blog token|Blog]] - The subscribed blog.
$user - [[The user token|User]] - The user who has subscribed to the blog.

Contact notifications

contactform.txt message file

contactform_usertouser.txt message file

$post - [[The post token|Post]] - The message being sent.
$user - [[The user token|User]] - The recipient of the message.

Forum notifications

forumpost_mailgateway.txt message file

forumpost_messageapproved.txt message file

$post - [[The post token|Post]] - The post to the forum being approved.
$user - [[The user token|User]] - The author of the post.

forumpost_messagemoved.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The author of the post.

forumpost_messagemovedandapproved.txt message file

$post - [[The post token|Post]] - The post to the forum being moved and approved.
$user - [[The user token|User]] - The author of the post.

forumpost_messageremoved.txt message file

forumpost_notifymoderators.txt message file

$user - [[The user token|User]] - The moderator who is being notified.

forumpost_notifythreadstarterofanswer.txt message file

forumpost_notifythreadstarterofsuggestedanswer.txt message file

forumpost_postnotification.txt message file

$post - [[The post token|Post]] - The post which triggered the notification.
$user - [[The user token|User]] - The recipient of the notification.

forumpost_threadmovednotracking.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The user being notified of the thread move.

forumpost_threadmovenotification.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The user being notified of the thread move.

forumpost_threadnotification.txt message file

$post - [[The post token|Post]] - The post which started a new thread.-
$user - [[The user token|User]] - The user who subscribed to this thread.

Friendship notifications

followers_notification.txt message file

$follower - [[The follower token|Follower]] - The relationship of the follower.

friendship_approved.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

friendship_requested.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

friendship_requested_nomessage.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

Group notifications

group_accessaccepted.txt message file

$group - [[The group token|Group]] - The group access has been granted to.
$user - [[The user token|User]] - The user being granted access.

group_accessrequest.txt message file

group_accessrequestdenied.txt message file

$group - [[The group token|Group]] - The group access has been denied to.
$user - [[The user token|User]] - The user being denied access.

group_useradded.txt message file

$group - [[The group token|Group]] - The group user has been added to.
$user - [[The user token|User]] - The user being added to the group.

Media Gallery notifications

mediagallerypost_commentnotification.txt message file

mediagallerypost_newcomment.txt message file

Message notifications

group_messages_also_replied.txt message file

group_messages_reply.txt messages file

messages_also_replied.txt message file

messages_newconversationmessage.txt messages file

messages_newprofilecomment.txt messages file

$message - [[The profile message token|Profile Message]] - The comment on the profile.
$user - [[The user token|User]] - The user who received the comment (the profile's owner).

messages_reply.txt messages file

messages_spam.txt messages file

messages_spam_deleted.txt messages file

messages_spam_deleted_user.txt messages file

$message - [[The message token|Message]] - The message which has been marked as spam.
$user - [[The user token|User]] - The recipient of the message.

Wiki notifications

wikis_definitespam.txt message file

wikis_pageupdated.txt message file

$page - [[The wiki page token|Wiki Page]] - The updated wiki page.
$revision - [[The wiki page-revision token|Wiki Page Revision]] - The previous version of the wiki page.
$user - [[The user token|User]] - The user who subscribed to updates to the wiki page.

wikis_possiblespam.txt message file

$page - [[The wiki page token|Wiki Page]] - The wiki page that has been flagged as possible spam.
$user - [[The user token|User]] - The user with permission to delete the wiki page to send the email to.

Customizing email replies to reply to the entire group whether you click Reply or Reply All

If upgrading to 5.x, you have the option of making all replies to a forum list go back to the entire group whether you click Reply or Reply all. This is a customization of the current 5.x behavior, which allows you to select replying to one member or replying all to the entire group.
1. Navigate to the email templates folder. For release 5.0 or 5.5, this will be in Web\Languages\<language>\emails\; for release 5.6 it will be in the Job Scheduler folder, which defaults to c:\Program Files\Telligent\Job Scheduler\, then continue to the \Languages\<language>\emails\ subfolder.)
2. Open forumpost_mailgateway.txt.
3. Under the line that begins with BCC:, add the following line:
```
Reply-To: <$globals.HtmlDecode($list.DetermineEmailAddress())>
```
  Setting the Reply-To will cause email clients to reply to the address listed instead of the address from which the email was sent.

Email Templates

Jenny Jarrard — Thu, 09 Feb 2012 17:51:36 GMT

Revision 17 posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 2/9/2012 11:51:36 AM

In Telligent Evolution 5.6, the following templates have been moved from the Web/Languages folder to the Job Scheduler/Languages folder (as noted below) and need to be modified there instead:

forumpost_mailgateway.txt
forumpost_postnotification.txt
forumpost_threadnotification.txt
weblog_newpost.txt
weblog_newcomment.txt

All of the emails sent out by the Telligent Evolution platform can be customized, both in how they look and what information they contain.

In the email templates, tokens are used to specify information. When the email is sent, the tokens are replaced by the correct values they represent (i.e., $Subject -> "Subject of blog post").

All templates are listed below along with the tokens available to the template.

How to customize an email template:

Navigate to the email template folder, which for 5.0 or 5.5 can be found in the Web/Languages/<your language>/emails folder, and in 5.6 in the Job Scheduler folder - typically c:\program files\Telligent\Job Scheduler\Languages\<language>/emails.
Find the name of the template that you want to change/edit.
The templates are stored as .txt files. Thus to change the forumpost_threadmovenotification template, open forumpost_threadmovenotification.txt in any text editor.
The list of available tokens is given below (along with the Global Terms).

Global Terms

A list of terms that are available on all templates is available on the [[The global term tokens|Global tokens]] page.

Account notifications

forgottenpasswordwithtoken.txt message file

newuser_accountcreated.txt messages file

$user - [[The user token|User]] - The user who created an account.

newuser_approved.txt messages file

$user - [[The user token|User]] - The user whose account was approved.

newuser_generatedpassword.txt messages file

$user - [[The user token|User]] - The user created an account with a generated password.

newuser_pending.txt message file

$user - [[The user token|User]] - The user who has attempted to join the site and is awaiting approval.

newuser_rejected.txt message file

$user - [[The user token|User]] - The user whose account was rejected.

roleemail.txt message file

user_changedpassword.txt message file

$user - [[The user token|User]] - The user who change their password.

user_forgottenpassword.txt message file

$user - [[The user token|User]] - The user who requested to be sent a new password.

userinvitation.txt message file

$invitation - [[The user invitation-token|User Invitation]] - The invitation to the new user.
$user - [[The user token|User]] - The user who invited the recipient to the community.

userinvitation_withsection.txt message file

$invitation - [[The user invitation-token|User Invitation]] - The invitation to the new user.
$user - [[The user token|User]] - The user who invited the recipient to the section/group.

Blog notifications

weblog_feedbacknotification.txt message file

weblog_moderationthreshold.txt message file

$section - [[The blog token|Blog]] - The blog that needs moderation attention.
$user - [[The user token|User]] - Blog owner who can moderate the blog.

weblog_newcomment.txt message file

$post - [[[The post token|Post]] - The new blog comment.
$user - [[The user token|User]] - The user who subscribed to new comments.

weblog_newpost.txt message file

$post - [[The post token|Post]] - The new blog post.
$user - [[The user token|User]] - The user who subscribed to new posts.

weblog_subscriptionconfirmation.txt message file

$section - [[The blog token|Blog]] - The subscribed blog.
$user - [[The user token|User]] - The user who has subscribed to the blog.

Contact notifications

contactform.txt message file

contactform_usertouser.txt message file

$post - [[The post token|Post]] - The message being sent.
$user - [[The user token|User]] - The recipient of the message.

Forum notifications

forumpost_mailgateway.txt message file

$attachmentUrls - NameValueCollection - A collection of urls for attachments to the post.
$charSet - string - The email encoding to use.
$list - [[The mailing list-token|MailingList]] - The mailing list that the post was sent to.
$mime.EncodeHeader(string subject, string charSet) - string - The encoded subject of the post.
$parentPost - [[The post token|Post]] - The parent post of the post that triggered the notification.
$post - [[The post token|Post]] - The post which triggered the notification.
$subscriber - [[The user token|User]] - The recipient of the notification.
$subjectCharSet - string - The email encoding to use for the subject.

forumpost_messageapproved.txt message file

$post - [[The post token|Post]] - The post to the forum being approved.
$user - [[The user token|User]] - The author of the post.

forumpost_messagemoved.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The author of the post.

forumpost_messagemovedandapproved.txt message file

$post - [[The post token|Post]] - The post to the forum being moved and approved.
$user - [[The user token|User]] - The author of the post.

forumpost_messageremoved.txt message file

forumpost_notifymoderators.txt message file

$user - [[The user token|User]] - The moderator who is being notified.

forumpost_notifythreadstarterofanswer.txt message file

forumpost_notifythreadstarterofsuggestedanswer.txt message file

forumpost_postnotification.txt message file

$post - [[The post token|Post]] - The post which triggered the notification.
$user - [[The user token|User]] - The recipient of the notification.

forumpost_threadmovednotracking.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The user being notified of the thread move.

forumpost_threadmovenotification.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The user being notified of the thread move.

forumpost_threadnotification.txt message file

$post - [[The post token|Post]] - The post which started a new thread.-
$user - [[The user token|User]] - The user who subscribed to this thread.

Friendship notifications

followers_notification.txt message file

$follower - [[The follower token|Follower]] - The relationship of the follower.

friendship_approved.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

friendship_requested.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

friendship_requested_nomessage.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

Group notifications

group_accessaccepted.txt message file

$group - [[The group token|Group]] - The group access has been granted to.
$user - [[The user token|User]] - The user being granted access.

group_accessrequest.txt message file

group_accessrequestdenied.txt message file

$group - [[The group token|Group]] - The group access has been denied to.
$user - [[The user token|User]] - The user being denied access.

group_useradded.txt message file

$group - [[The group token|Group]] - The group user has been added to.
$user - [[The user token|User]] - The user being added to the group.

Media Gallery notifications

mediagallerypost_commentnotification.txt message file

mediagallerypost_newcomment.txt message file

Message notifications

group_messages_also_replied.txt message file

$message - [[The reply message token|Reply Message]] - The reply to the message thread.
$parent - [[The message token|Message]] - The first message in the conversation (the group message).
$recipient - [[The user token|User]] - The user that commented in the message thread.
$replies - [[The reply message-token|Reply Message]] - The list of all replies to the parent group message.

group_messages_reply.txt messages file

$message - [[The reply message-token|Reply Message]] - The reply to the parent group message.
$parent - [[The message token|Message]] - The first message in the conversation (the group message).
$recipient - [[The user token|User]] - The user the message who posted the status message.
$replies - [[The reply message-token|Reply Message]] - The list of all replies to the parent group message.

messages_also_replied.txt message file

$message - [[The reply message-token|Reply Message]] - The reply to the message thread.
$parent - [[The message token|Message]] - The first message in the conversation (the status message).
$recipient - [[The user token|User]] - The user that commented in the message thread.
$replies - [[The reply message-token|Reply Message]] - The list of all replies to the parent status message.

messages_newconversationmessage.txt messages file

messages_newprofilecomment.txt messages file

$message - [[The profile message-token|Profile Message]] - The comment on the profile.
$user - [[The user token|User]] - The user who received the comment (the profile's owner).

messages_reply.txt messages file

$message - [[The reply message-token|Reply Message]] - The reply to the parent status message.
$parent - [[The message token|Message]] - The first message in the conversation (the status message).
$recipient - [[The user token|User]] - The user the message who posted the status message.
$replies - [[The reply message-token|Reply Message]] - The list of all replies to the parent status message.

messages_spam.txt messages file

messages_spam_deleted.txt messages file

messages_spam_deleted_user.txt messages file

$message - [[The message token|Message]] - The message which has been marked as spam.
$user - [[The user token|User]] - The recipient of the message.

Wiki notifications

wikis_definitespam.txt message file

$page - [[The wiki page-token|Wiki Page]] -The wiki page that has been flagged as possible spam.
$user - [[The user token|User]] - The user with permission to delete the wiki page to send the email to.

wikis_pageupdated.txt message file

$page - [[The wiki page-token|Wiki Page]] - The updated wiki page.
$revision - [[The wiki page-revision-token|Wiki Page Revision]] - The previous version of the wiki page.
$user - [[The user token|User]] - The user who subscribed to updates to the wiki page.

wikis_possiblespam.txt message file

$page - [[The wiki page-token|Wiki Page]] - The wiki page that has been flagged as possible spam.
$user - [[The user token|User]] - The user with permission to delete the wiki page to send the email to.

Customizing email replies to reply to the entire group whether you click Reply or Reply All

If upgrading to 5.x, you have the option of making all replies to a forum list go back to the entire group whether you click Reply or Reply all. This is a customization of the current 5.x behavior, which allows you to select replying to one member or replying all to the entire group.
1. Navigate to the email templates folder. For release 5.0 or 5.5, this will be in Web\Languages\<language>\emails\; for release 5.6 it will be in the Job Scheduler folder, which defaults to c:\Program Files\Telligent\Job Scheduler\, then continue to the \Languages\<language>\emails\ subfolder.)
2. Open forumpost_mailgateway.txt.
3. Under the line that begins with BCC:, add the following line:
```
Reply-To: <$globals.HtmlDecode($list.DetermineEmailAddress())>
```
  Setting the Reply-To will cause email clients to reply to the address listed instead of the address from which the email was sent.

Email Templates

Jenny Jarrard — Thu, 09 Feb 2012 17:50:29 GMT

Revision 16 posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 2/9/2012 11:50:29 AM

In Telligent Evolution 5.6, the following templates have been moved from the Web/Languages folder to the Job Scheduler/Languages folder (as noted below) and need to be modified there instead:

forumpost_mailgateway.txt
forumpost_postnotification.txt
forumpost_threadnotification.txt
weblog_newpost.txt
weblog_newcomment.txt

All of the emails sent out by the Telligent Evolution platform can be customized, both in how they look and what information they contain.

In the email templates, tokens are used to specify information. When the email is sent, the tokens are replaced by the correct values they represent (i.e., $Subject -> "Subject of blog post").

All templates are listed below along with the tokens available to the template.

How to customize an email template:

Navigate to the email template folder, which for 5.0 or 5.5 can be found in the Web/Languages/<your language>/emails folder, and in 5.6 in the Job Scheduler folder - typically c:\program files\Telligent\Job Scheduler\Languages\<language>/emails.
Find the name of the template that you want to change/edit.
The templates are stored as .txt files. Thus to change the forumpost_threadmovenotification template, open forumpost_threadmovenotification.txt in any text editor.
The list of available tokens is given below (along with the Global Terms).

Global Terms

A list of terms that are available on all templates is available on the [[The global terms tokens|Global tokens]] page.

Account notifications

forgottenpasswordwithtoken.txt message file

newuser_accountcreated.txt messages file

$user - [[The user token|User]] - The user who created an account.

newuser_approved.txt messages file

$user - [[The user token|User]] - The user whose account was approved.

newuser_generatedpassword.txt messages file

$user - [[The user token|User]] - The user created an account with a generated password.

newuser_pending.txt message file

$user - [[The user token|User]] - The user who has attempted to join the site and is awaiting approval.

newuser_rejected.txt message file

$user - [[The user token|User]] - The user whose account was rejected.

roleemail.txt message file

user_changedpassword.txt message file

$user - [[The user token|User]] - The user who change their password.

user_forgottenpassword.txt message file

$user - [[The user token|User]] - The user who requested to be sent a new password.

userinvitation.txt message file

$invitation - [[The user invitation-token|User Invitation]] - The invitation to the new user.
$user - [[The user token|User]] - The user who invited the recipient to the community.

userinvitation_withsection.txt message file

$invitation - [[The user invitation-token|User Invitation]] - The invitation to the new user.
$user - [[The user token|User]] - The user who invited the recipient to the section/group.

Blog notifications

weblog_feedbacknotification.txt message file

weblog_moderationthreshold.txt message file

$section - [[The blog token|Blog]] - The blog that needs moderation attention.
$user - [[The user token|User]] - Blog owner who can moderate the blog.

weblog_newcomment.txt message file

$post - [[[The post token|Post]] - The new blog comment.
$user - [[The user token|User]] - The user who subscribed to new comments.

weblog_newpost.txt message file

$post - [[The post token|Post]] - The new blog post.
$user - [[The user token|User]] - The user who subscribed to new posts.

weblog_subscriptionconfirmation.txt message file

$section - [[The blog token|Blog]] - The subscribed blog.
$user - [[The user token|User]] - The user who has subscribed to the blog.

Contact notifications

contactform.txt message file

contactform_usertouser.txt message file

$post - [[The post token|Post]] - The message being sent.
$user - [[The user token|User]] - The recipient of the message.

Forum notifications

forumpost_mailgateway.txt message file

forumpost_messageapproved.txt message file

$post - [[The post token|Post]] - The post to the forum being approved.
$user - [[The user token|User]] - The author of the post.

forumpost_messagemoved.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The author of the post.

forumpost_messagemovedandapproved.txt message file

$post - [[The post token|Post]] - The post to the forum being moved and approved.
$user - [[The user token|User]] - The author of the post.

forumpost_messageremoved.txt message file

forumpost_notifymoderators.txt message file

$user - [[The user token|User]] - The moderator who is being notified.

forumpost_notifythreadstarterofanswer.txt message file

forumpost_notifythreadstarterofsuggestedanswer.txt message file

forumpost_postnotification.txt message file

$post - [[The post token|Post]] - The post which triggered the notification.
$user - [[The user token|User]] - The recipient of the notification.

forumpost_threadmovednotracking.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The user being notified of the thread move.

forumpost_threadmovenotification.txt message file

$post - [[The post token|Post]] - The post to the forum being moved.
$user - [[The user token|User]] - The user being notified of the thread move.

forumpost_threadnotification.txt message file

$post - [[The post token|Post]] - The post which started a new thread.-
$user - [[The user token|User]] - The user who subscribed to this thread.

Friendship notifications

followers_notification.txt message file

$follower - [[The follower token|Follower]] - The relationship of the follower.

friendship_approved.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

friendship_requested.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

friendship_requested_nomessage.txt message file

$friendship - [[The friendship token|Friendship]] - The relationship of the friendship.

Group notifications

group_accessaccepted.txt message file

$group - [[The group token|Group]] - The group access has been granted to.
$user - [[The user token|User]] - The user being granted access.

group_accessrequest.txt message file

group_accessrequestdenied.txt message file

$group - [[The group token|Group]] - The group access has been denied to.
$user - [[The user token|User]] - The user being denied access.

group_useradded.txt message file

$group - [[The group token|Group]] - The group user has been added to.
$user - [[The user token|User]] - The user being added to the group.

Media Gallery notifications

mediagallerypost_commentnotification.txt message file

mediagallerypost_newcomment.txt message file

Message notifications

group_messages_also_replied.txt message file

$message - [[The reply message token|Reply Message]] - The reply to the message thread.
$parent - [[The message token|Message]] - The first message in the conversation (the group message).
$recipient - [[The user token|User]] - The user that commented in the message thread.
$replies - [[The reply message-token|Reply Message]] - The list of all replies to the parent group message.

group_messages_reply.txt messages file

messages_also_replied.txt message file

messages_newconversationmessage.txt messages file

messages_newprofilecomment.txt messages file

$message - [[The profile message-token|Profile Message]] - The comment on the profile.
$user - [[The user token|User]] - The user who received the comment (the profile's owner).

messages_reply.txt messages file

messages_spam.txt messages file

messages_spam_deleted.txt messages file

messages_spam_deleted_user.txt messages file

$message - [[The message token|Message]] - The message which has been marked as spam.
$user - [[The user token|User]] - The recipient of the message.

Wiki notifications

wikis_definitespam.txt message file

wikis_pageupdated.txt message file

wikis_possiblespam.txt message file

$page - [[The wiki page-token|Wiki Page]] - The wiki page that has been flagged as possible spam.
$user - [[The user token|User]] - The user with permission to delete the wiki page to send the email to.

Customizing email replies to reply to the entire group whether you click Reply or Reply All

If upgrading to 5.x, you have the option of making all replies to a forum list go back to the entire group whether you click Reply or Reply all. This is a customization of the current 5.x behavior, which allows you to select replying to one member or replying all to the entire group.
1. Navigate to the email templates folder. For release 5.0 or 5.5, this will be in Web\Languages\<language>\emails\; for release 5.6 it will be in the Job Scheduler folder, which defaults to c:\Program Files\Telligent\Job Scheduler\, then continue to the \Languages\<language>\emails\ subfolder.)
2. Open forumpost_mailgateway.txt.
3. Under the line that begins with BCC:, add the following line:
```
Reply-To: <$globals.HtmlDecode($list.DetermineEmailAddress())>
```
  Setting the Reply-To will cause email clients to reply to the address listed instead of the address from which the email was sent.

Hotfixes for Telligent Evolution 5.6 including Telligent Community 5.6 and Telligent Enterprise 2.6

Jenny Jarrard — Tue, 31 Jan 2012 16:18:55 GMT

Current Revision posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 1/31/2012 10:18:55 AM

The following list details bugs that were fixed or will be fixed in chronological hotfixes. The hotfixes are cumulative, meaning that the more recent hotfix will contain fixes incorporated in previous hotfixes. Please contact Telligent Support to request any hotfix shown here, ask questions about specific bug fixes or get additional help in applying the hotfixes to your environment.

12 January 2012 5.6.583.21914 and 2.6.583.21914
10 December 2011 5.6/2.6.583.21163 and 2.6.583.21163
7 November 2011: 5.6.583.20496 and 2.6.583.20496
5 October 2011: 5.6.583.19849 and 2.6.583.19849
22 September 2011: 5.6.583.19431 and 2.6.583.19431
31 August 2011: 5.6.583.19199 and 2.6.583.19199
15 July 2011: 5.6.583.18163 and 2.6.583.18163
8 June 2011: 5.6.583.17018 and 2.6.583.17018
16 May 2011: 5.6.583.17018 and 2.6.583.17018
25 April 2011: 5.6.583.16466 and 2.6.583.16466
15 March 2011: 5.6.583.15464 and 2.6.583.15464
15 February 2011: 5.6.583.14653 and 2.6.583.14653
17 January 2011: 5.6.583.14036 and 2.6.583.14036
17 December 2010: 5.6.583.13797 and 2.6.583.13797
24 November 2010: 5.6.583.13623 and 2.6.583.13623
1 November 2010: 5.6.583.13179 and 2.6.583.13179

12 January 2012 5.6.583.21914 and 2.6.583.21914

13215 - Deleting a conversation message no longer gives an error because the application now checks whether the user has permission to delete a message before processing the delete request.
11510 - Blog Owners can now no longer upload restricted file types. Only users with OverrideValidation globally or on the group level can do so.
13274 -File access validators no longer reject file paths that include subfolders.
13271 - You can now create a username with less than three characters.
13647 - When a wiki page is created, there is no longer an "edited" wiki page activity message in the activity message list, but instead only and "added" wiki page activity message.
14272 - The cs_Group_Update.PRC now updates permissions only on the updated group instead of across all nodes. Previously, all nodes’ permissions were being updated, and this could cause a timeout.
13613 - The Blog Post List widget now loads faster.
13614 - The Tag Cloud widget now loads faster.

10 December 2011 5.6/2.6.583.21163 and 2.6.583.21163

8679 - The following endpoints were backported from trunk (RESTv2) to 5.6 to support SharePoint moving off REST v1 code: /blogs/{blogId}/posts.xml; /groups/{groupId}/forums.xml; /groups/{groupId}/blogs.xml; /groups/{groupId}/wikis.xml; and /groups/{groupId}galleries.xml.
12143 - When hitting the legacy URL redirect for a forum thread [/utility/legacyurlredeirects-forum.ashx?ThreadID=### (using an existing forum thread)]there was an argument out of range exception for the length (e.g., Length cannot be less than zero). This was due to the LegacyUrlRedirectHandler.cs having an invalid call to a substring. We added a conditional to circumvent this problem.
12176 - When you uploaded a file using Chrome, the dialog box no longer overlaps.
12818 - Stateful Quartz jobs (ex. search, ldap sync) now continue to run if an exception is thrown within the job startup.
12840 - The Job Scheduler processing model has changed from processing one type of application at a time to a round-robin approach that indexes x items within the content type and then moves on to the next content handler and comes back to the original after all others have been called. This change was made to avoid blocking other jobs if users needed to be reindexed. Added round robin processing to configurable maximum batch run size to job scheduler. Fixed issue with slow forum thread indexing when sticky posts are present.
12821 - CSValidationException was updated to include all validation errors in the Message property.
12875 - Wiki pages having a significant number of long and extensive revisions no longer cause performance issues with a wiki RSS feed. This was fixed by removing the comparison between versions, so that only new content is displayed in the wiki page’s RSS feed.

7 November 2011: 5.6.583.20496 and 2.6.583.20496

10299 - In sending an email to a blog owner via the contact.aspx page, line breaks in the email were removed. Such messages are now properly formatted. A $core_v2language.NewLine property was also added so this can be edited in the template as well.
10316 - If you responded to a forum post with a suggested answer, then went back into your response and edited it, saving the changes removed the "suggested answer" check mark. This has been fixed.
10300 - There was inconsistent spam engine behavior across applications. For example, forum posts caught by the spam engine were marked as "not approved," while media gallery comments were not caught or marked. This behavior has been corrected for media gallery comments to be marked as "not approved."
10324 - The report abuse forum and deleted forum posts were being subjected to spam filters. This has been corrected so that when the spam rule triggers, Telligent Evolution verifies it is running on a normal (e.g., not deleted or reporting) forum before processing.
10351 - When you set a custom profile field (such as Birthday) as a required field for the join community experience, the field was displayed but not validated. This has been corrected.
10691 - If you added a subgroup to a group containing many sub groups, using a duplicate key (that is, having the same key as another subgroup), you received a validation error - "The group name already exists under the selected parent group." This was due to the application checking only a subset of the groups for duplicates and not the entire set.
10798 - Non-duplicated wiki pages that used punctuation (such as period, dash, or colon) in their titles used numeric page IDs as their page URLs instead of converting the punctuation to spaces in their keys. For example, "Test three-four" as a wiki page title resulted in having an integer page key. This has been fixed.
10857 - This bug fixes an issue that could occur whenever a DNS problem happens and an image is cached in a users’ browser incorrectly.
11175 - The Extended Analytics module of Telligent Analytics was counting validated users' first visits as being by the anonymous user, using a random new guid instead of the user's membership guid. This was fixed so that the Web Analytics table captures the correct user ID the first time through.
11168 - When posting blog comments en masse, the indexes PC_cs_Threads and IX_Posts_Threads in procedure cs_Weblog_Post_Create became deadlocked and stopped the posting. We added nolocks to the two count(*) statements getting the count from te_BlogPost Comments to alleviate the problem.
11029 - Changing a group type previously caused orphaned data in cs_Security_EffectivePermissions, essentially keeping the permissions of the apps as the old permissions. We changed the sprocs cs_Security_EffectivePermissions_Calculate to eliminate corrupting data by pulling from the #temp table instead of the physical table.
10344 - A disabled blog post could previously still appeared via RSS feed. The disabled blog post is now removed from the RSS feed within several minutes of removal from the site.
10364 - If you edited the Registered User role's permissions, site read profile permission (SitePermission.ReadProfiles) was lost from the Registered users role and made users stop appearing in search. This was fixed.
9109 - Some invalid characters were not being removed from posts. XmlSanitization was added to HtmlSanitization so they are not persisted. XML-invalid surrogate unicode characters (as defined by the W3 http://www.w3.org/TR/2000/REC-xml-20001006#charsets) in post titles, bodies, and comments are now stripped.
9444 - The RSS Feed widget was showing an incorrect date for entries. RSS.NET was updated to support time zone abbreviation translations, and the hotfix includes an update to use the new build of RSS.NET.
10399 - This allows for Evolution to know the real IP address for a user who is behind a proxy.

5 October 2011: 5.6.583.19849 and 2.6.583.19849

9533 - In Active Directory, the group membership page add member box showed users with commas in the name (e.g., Johnson, Joe) with the comma turned into characters %2c. This was fixed.
9544 - In Active Directory, the group membership page add member box search returned computer names in addition to usernames. LDAP's user name filters were changed to not return computers when searching for users.
9615 - Forum and Mail Gateway inline attachment validators were added to 5.6/2.6.
9698 - Performing a get Search List request using a url filter for a known site page url that contained punctuation, like a period or comma, returned no results. The code for parsing out that url only considered alphanumeric characters and not other punctuation. This was fixed.
9791 - Changing the value of a profile field with a single selectable list field type did not update correctly; instead, the old value was displayed instead of the new one. This has been fixed.
10147 - The member search page in Control Panel was updated to be over SSL when ssl=Password is set in the communityserver.config file.
9981 - If your list of forums in a group exceeded 20, some forums were excluded from the Forum Moderation page. This was due to a default page size restriction. The returned record limit has been increased.
10149 - When logged out of the site, navigating to a site home page over SSL (e.g., https://site.com) redirected you to the site theme page. This was fixed to return the correct URL.
10178 - When you set ssl=Password in communityserver.config and requireSSL=false in web.config (Forms authentication), any request for https that does not transmit a password is now redirected to http.
10253 - The BaseAtomWriter was updated so that the Atom feed for a blog displays the user's display name rather than his/her username.
10346 - A problem with uploading a file such as an avatar in Firefox 7.0 has been resolved.

22 September 2011: 5.6.583.19431 and 2.6.583.19431

9152 - The secure RSS did not work as expected - if you clicked RSS on a blog in a private unlisted group and copied the URL, you were redirected to the login page when you tried to view the URL. This has been fixed.
7758 - You couldn't add a friend to a conversation if the friend was #21 or higher in your list of friends. This has been fixed.
9540 -The TinyMCE context menu was only supported in IE. TinyMCE has been updated to only show the menu when text is not selected or the user clicks on a <table>, <tbody>, <thead>, <tr>, <td>, or <th> tag. The cut, copy, and paste options were removed from the context menu.
5542 - The new forum post dialog for adding an attachment dialog was not localized; the browse button and form error messages had hard-coded values. The browse button cannot be localized because its caption is set by the browser. The error messages were localized.
9728 - If you gave a blog draft a future publish date, then saved it as a draft (i.e., not published), no publication notification was sent when the blog post was published. This has been fixed.

31 August 2011: 5.6.583.19199 and 2.6.583.19199

7869 - Formerly when you tried to block an IP address behind a load balancer, you could not get an accurate client IP address. This has been addressed.
8595 - It was possible in a forum to add, using the Image Upload button, file(s) whose extensions were not on the allowed extension list (Control Panel > System Administration > Forum Administration > Configuration > Global Forum Settings > Attachments). The attachments are now limited to those in the Control Panel list.
8731 - It was formerly possible to reuse a blog mirrored feed after it had been deleted but the ability was subsequently removed. This capability has been restored.
8732 - The blog lists management page (Control Panel > My blogs > [blog name] > Manage > Lists) didn't allow you to select a different list to manage. This has been fixed.
7884 - Wiki page links containing special characters could be broken after upgrading from 5.5 to 5.6. This is because in 5.6 and up, titles are supplied with HTML encoding while in 5.5, they were not. This problem has been fixed.
8662 - The CSControl:ValueSelectedContent control on uploadpostattachment.aspx now works in non-English sites.
8901 - If you created a wiki post with an uploaded image and set the file date on the server to future, the image could appear as a broken link in IE. This has been fixed.
8650 - If the "Allow Conversations From" option (Control Panel > System Administration > Membership Administration > [user] > Edit > Members and Roles > Manage Users > Email and Contact Info) was set to All Users, setting the "Share this" link did not work for specified members who were not friends. This has been fixed.
9671 - If you tried to add a blog to Windows Live Writer and then entered the URL to a public or joinless blog, you received an "index out of range" message. The code causing this issue has been fixed.
8816 - If, as an admin, you were managing comments for a particular blog (Control Panel > System Administration > Blog Administration > Blogs > [blog name] > Manage), clicking Recent Comments and selecting a blog, then clicking the Publish Selected or Publish button did not return new comments. This has been fixed.
8566 - A registered user who had been granted custom permissions (Blog - Create Posts and Blog - Edit Posts) was unable to edit a post after saving it as a draft. This has been fixed.
9255 (and 9185) - As a friend of a user in a private unlisted group, you could see that group member's private group activity. This has been fixed.
8574 - Calling the cs_Security_EffectivePermissions_Calculate process without a specified node ID caused a timeout because it deleted and inserted a large number of records into the effective permission table. This process has been fixed to use a temp table in order to improve performance.

15 July 2011: 5.6.583.18163 and 2.6.583.18163

6010 - You could get a yellow screen when attempting to view a forum post after changing its date in the database cs_Posts table for a zone which honors daylight savings time (such as [UTC] Dublin, Edinburgh, Lisbon, London). The error occurred because the server was set to Daylight Savings time, but the check box to honor Daylight Savings is not checked - meaning DateTime could create a date and time that did not exist within one hour from the spring forward point. We have updated userTime to check whether the supplied time is valid and, if not, to increment it by one hour. Note: In general we recommend that when you set time zones, you do not try to ignore daylight savings time because the database is not designed for this.
7352 - When calling the ForumThreads endpoint with a query type of Active, announcements were not being returned. We changed the endpoint to use ThreadSet.AllThreads instead of ThreadSet.Threads so that announcements are also included.
7457 - With SSO set up, there could be login problems for users with unvalidated email addresses after upgrading from Telligent Evolution 5.5 to 5.6. For a problem to occur, there were three possible causes: (1) The user had a setting that was valid in 5.5 and not in 5.6, such as an signature length over 255 characters, or an invalid email from an old version of Community Server; (2) SSO had not refreshed the user's profile in at least seven days, and (3) the SSO cookie had not provided a new public email from the single sign-on source. We have changed the setting so that public email and signature are not validated on the upgrade unless the values have changed. In effect, the 5.5 values for email and signature are grandfathered in until they are changed.
8019 - In IE9, the Wikis - Table of Contents widget did not display child pages (it showed a message of "loading") when expanded client-side. This was due to changes made to support IE9. The applicable changes were rolled back, and the widget now works correctly.
8022 - The Quick Post widget did not display a Browse button on its Share a File tab when dropped on the dashboard or user's profile page. media galleries. This was fixed in the code. Note: Search must be enabled for the applications to display the browse button.
8081 - The aggregate blog page showed a future date in its last post column when you set a blog post for a future date. This was fixed.
8103 - If you added a user's display name (different from their username) as a blog owner, the blog author display showed the user's username. This was fixed.
8210 - Accessing the ~/api.ashx/v2/forums/threads/active.xml node in REST for a forum, there could be differing post counts - such as two in TotalCount but one in the <threads> node. This was due to a redundant security check, which has now been removed. The totals now correspond.
8215 - Rating ability could disappear from a forum post after you posted a (non-rich-text) reply. This has been fixed.
8302 - Blog post comment moderation settings made at the blog level could be overridden by changing the setting in the Control Panel. The blog-level setting is now respected.
8506 - Users were automatically resubscribed to all forums in a group when a new forum was added. This has been fixed.
8535 - It was possible for the operation of adding a new role to a group to cause very large sites to time out. This was fixed.
8138 - With SSL set to password (SSL=Password), clicking any other element (such as banner links) on the login page caused you to be directed to unsecure pages over a secure encrypted connection (https). A script error was fixed.
8594 - You could not post to private blogs via Windows Live Writer using the metablog2.ashx endpoint. This was due to an issue with the group ID. It has been fixed.
6963 - In the Control Panel, Manage ranks was changed from using the number of posts to the number of points. The number of posts was previously what the rank in the User Hover showed, and that has now been changed to points. Users might consequently find that they have higher ranks after this change. For example, a rank that was 10 to 50 posts prior to this hotfix would now be changed to 10 to 50 points. Since one post can be worth more than 10 points, fewer posts would be required to reach the rank limit.

8 June 2011: 5.6.583.17018 and 2.6.583.17018

7232 - The popular posts (Forum Administration > Configuration > Global Forum Settings > Popular Posts) minimum number previously only counted posts with more than one reply as popular. The code now will count one reply as popular if you configure this to be the minimum.
7209 - When you created a post-dated blog post and selected its Featured Content check box, the blog post would post on the correct time and but would show its age as incrementing from the time it was actually created instead of its post-dated publication time. (For example, if you created a post at 3:00 p.m. and set it to publish at 3:30, the post published at 3:30 but said it was published 30 minutes prior.) This has been fixed, and the publication age now increments from the actual publication time.
7899 - When you modified roles on a site having a large number of posts (over 3 million), the permissions recalculation ran in addition to the cs_search_reindexall stored procedure; that procedure, which consisted mostly of site-resetting, could cause the two procedures to time out. In order to avoid the timeout, full-site search reindexes have been moved to a background job.
7939 - Fixed low-risk security vulnerability.

16 May 2011: 5.6.583.17018 and 2.6.583.17018

5759 - A user was previously able to delete others' blog posts without having the explicit permission (Blog - delete post) to do so. A user can no longer use the Delete button to remove a post if he/she does not have the authority to do so. However, the following scenarios do allow a user to delete post(s):
- A blog's author can delete any of the blog's posts.
- A user can always delete his/her own posts, even without the explicit Blog - delete post permission.
- A community member with the explicit delete permission can delete any blog post.
5817 - Three issues with IE9 were resolved:
- It wasn't possible to drag/drop widgets or tabs in the page-editing UI.
- There was a JavaScript error in TinyMCE.
- Images or videos could not be inserted via the editor in IE9, and their dialogs presented exception errors upon closing.
We also identified an issue with the Browse button occasionally not triggering the browse dialog if you click the button on the far-outer edges. That was not addressed in this bug.
6221 - In REST remote attachments for blogs, forums, and file galleries, it appeared that the filename and fileurl were being switched due to some repetitive code. While the two content types were not actually being switched, the code was cleaned up.
7047 - If you subscribed to a blog and then unsubscribed to it; changed your email address in your user account, and subscribed to the blog again, this created a duplicate key error resulting in a yellow screen. Blog subscriptions are now properly updated.
7214 - RSS feeds were returning full posts instead of excerpts. This was fixed.

25 April 2011: 5.6.583.16466 and 2.6.583.16466

5943 - Previously it was not possible to configure the height and width of videos. There is now a Media Settings tab (in Site Theme) that allows you to do this.
5944 - When a forum thread was created as a question as well as an announcement, it was missing an opening <div> tag, which caused the announcement to be placed incorrectly. This was fixed.
5867 - Normal (non-admin) users could not edit replies to sticky (forever) posts. This was fixed.
5646 - When you added a role as a group member, it was added with blank permissions rather than those expected for the member. This has been fixed.
5609 - Full-screen mode is now supported for YouTube videos.
5477 - Flood interval checking has been removed from the Control Panel.
1256 - In forums where both Question and Answer and Discussion types were enabled, the Suggested Answer check box could disappear from quick answers to questions. This has been fixed.
5536 - Activity Stream query performance was improved.
5622 - Uploading a PDF via the Add a Media Gallery Post REST v2 endpoint resulted in a "Data at the root level is invalid" error. This has been fixed.
3864 - Status message replies of any length were allowed. The max length restriction of 256 characters is now applied.
4140 - Site-mapping for wikis could cause an issue because null or empty tags were being populated and, in some cases, tags beyond the row count limit were not being selected. This has been fixed.

15 March 2011: 5.6.583.15464 and 2.6.583.15464

4889 - Forum replies from email added an extra space in the subject for each subsequent reply. This was fixed.
5203 - When you clicked Next in a forum to view the following page of a post, you needed to click Next twice. This issue was corrected.
3694 - When flood interval checking was enabled (Control Panel > System Administration > Forum Administration > Configuration > Global Forum Settings > Duplicates > Flooding), multiple posts were allowed within the time limit. This was corrected.
5512 - When the author of a question in a Q&A forum tried to mark a reply to his/her post made by another user as a suggested answer, or as an answer through the Update Forum Reply REST endpoint, it would return an error message that the user did not have permission to edit the reply. This has been corrected.
5238 - If a forum post was created using the mobile interface in a question-only forum, it was created as a discussion instead of question. This has been fixed.
5239 - If you created a thread in a forum supporting both thread types, the thread would be created with the correct type, but its ThreadStatus was "NotSet." (If you did the same on the main site, ThreadStatus was "NotAnswered.") This was corrected.
5390 - The Show Forum REST endpoint did not include the AllowedThreadTypes property. This property was added to RestForum.
3581 - An iTunes RSS feed was previously not generated properly for the modern iTunes standard. It was missing the author tag. This has been corrected.
3760 - The \Languages\en-US\error SiteUrlData.htm page was missing some text. This has been corrected.

15 February 2011: 5.6.583.14653 and 2.6.583.14653

3729 - Server licensing counts counted Job Scheduler on a separate server as a separate server. This has been fixed. Job scheduler on a separate server does not increase server count in licensing.
3758 - A user display name containing an apostrophe formerly could not be found in Control Panel's user search. Such a user is now found.
4139 - Shared membership was not working in 5.6 or trunk, creating an infinite loop. The validator now calls directly to the database, and the update only performs password rules validation for non-shared users so looping does not occur.
3686 - Forum posts - Anonymous users were able to delete/edit other anonymous users' forum posts. Anonymous users are no longer to delete/edit posts.
3706 - When assigning default new friends for a user joining or registering on a site, the Default New User Friends field content is now saved.
3953 - Changing a user profile page layout didn’t render when modified more than once. This has been corrected.
4533 - Wiki pages were not being flagged to be re-indexed when a group type was changed. This was fixed.
4272 - It was not possible to remove a license if a site was out of compliance for server counts. Servers are now properly deregistered.
3545 - We investigated searching *.docx text in file attachments and found it doesn't work on Windows 2003 R2 64 and Windows 2008.
3760 - \Languages\en-US\errors SiteUrlData.htm had some missing text. This was corrected.
428 - Control Panel - Content/site security - When a user added an incorrect IP address to the Address Banning page, a warning was displayed; when that IP was deleted or corrected, the warning was still displayed. This has been fixed.
609 - The Files-Download counter-Generate report option kept the same generation dates even if one or both of them changed. This has been fixed.
3578 - If a group name was too long, it was not broken to the next line on application pages.This has been fixed.
2602 - RSS and Atom feed handlers declared "Community Server" for the "Generator" field. This has been changed to "Telligent Evolution."
392 - If you edited a group from the main group and deleted any application, you weren't redirected to the site root group page (but instead were left on the same application page). This has been corrected.
386 - It was possible for a user to save his/her changes to a previously locked wiki page. This has been fixed.
3503 - Automatic activity message delivery was not working correctly. This has been fixed.

17 January 2011: 5.6.583.14036 and 2.6.583.14036

2744 - If you added an attachment to a forum post sent to a group without a media gallery, the attachment was dropped in emails. Forum list emails with attachments sent to groups with or without media galleries now show the attachment correctly.
2746 - If a user was set up not to receive HTML emails (Settings > uncheck Receive HTML emails), email from a wiki subscription was still sent in HTML. Wiki pages can now be rendered in plain text in emails.
2511 - When a user set his/her out-of-office email response, the message was sent in response to forum post notifications and then it remained in the SMTP dropbox instead of being deleted. This has been fixed.

17 December 2010: 5.6.583.13797 and 2.6.583.13797

1528 - The Activity List widget on the user profile displayed all users' activity to anonymous users. The widget was updated to support the "userprofile" mode when rendered to an anonymous user.
2082 - Auto-linking was updated to also be supported when using the (Please visit the site to view this file) embed code within HTML content. The link was updated not to open in a new window.
2583 - File viewers were fixed to honor the theme-defined maximum width/height. The fix ensures that embedded video is scaled to fit within the bounding box of the requested width/height using the same logic as image resizing.
1191 - The breadcrumb on the tags page were using the URL string for tag display rather than the tag as written in the database (such as if lowercase in the URL, being displayed all lowercase in the breadcrumb). SiteUrls.config was updated to identify that URLs containing tags should not be forced to lowercase.
2799 - Anonymous users can no longer access the Invite User page.
2593, 1252 - When code was entered into posts using the HTML source editor, JavaScript was being commented out twice - stopping inline JavaScript from working. HTML comments within a UL tag were generating an extra UL tag. We added support for HTML comments and CDATA elements in the HtmlSanitizer.
2601 - Creating a media gallery post could cause a reset when mousing over an anchor. The method that caused it was removed.
1786 - CS 2.1 attachment links were not resolving when upgrading to 5.5. This was fixed in 5.5 and 5.6.

24 November 2010: 5.6.583.13623 and 2.6.583.13623

373 - (Mobile): ForumService.CreateReply did not set the post subject when creating a reply to a thread. This was corrected.
1134 - Pages created in a non-English language could get duplicate page keys. The pages are now compared and if they have similar names, unique keys are generated.
1038 - Searching for a term could cause the browser to start hanging and generate a script warning. To remedy this, the result body was removed from the JSON word wheel search JSON response.
1183 - When a user changed his/her language to Japanese (JAJP), the date did not change to Japanese. If the language was changed back to ENUS, the date displayed in Japanese with English. This was fixed.
1192 - ATOM feeds had relative URLs instead of absolute URLs in them, causing external ATOM readers not to find the feed. The URL is now absolute.
1210 - If you entered a comment as an anonymous user on a blog post that you could receive the subsequent email notification on, the email version of the comment showed an anonymous user sent the email (instead of the name entered on the comment form). The activity list will not show the name entered on the comment form, it will still show anonymous. The email will show the name entered on the comment form.
1248 - Our locking patterns were updated to only use Monitor locks instead of ReaderWriterLockSlims.
1260 - Japanese strings could be improperly truncated halfway through a single character. Support was added to properly truncate strings that use surrogate pairs to form letter glyphs.
2312 - Configuration settings for valid media file extensions were being ignored, and they were only possible to permit or restrict on a gallery-by-gallery basis. Now only valid file extensions are allowed to be uploaded to media galleries by users who do not possess validation permissions. Remote files are checked for allowed file extensions or file viewers.
2340 - Forum attachment support was corrected to allow attaching remote URLs that don't pass file type validation but do have file viewers.
2422 - Blog attachment support was corrected to allow attaching remote URLs that don't pass file type validation but do have file viewers.
2498 - We improved performance by removing license checks for post and comment counts since these counts were not used.
2553 - It was possible to view future published blog posts if you knew the URL. A date check was added, and only users who can post to the blog can view future-dated posts.
2495 - A blog post remained in RSS and search after its status was changed from published to disabled or draft. The search csmodule was updated to flag blog posts for deletion when they go from a published to unpublished.
2419 - If enable passive mode (for email) was set to yes, email notifications were not sent to group members - whether internal or invoked by the post. You had to set Passive Mode=No in order to send email notifications; and group members could receive duplicate posts. This was introduced by 4787. It has been fixed.
1554 - When you used Customize mode to customize a new tab with widgets, locked widgets could be displayed on the home page. This was fixed.
1541 If a parent group and child group had the same name, updating the parent group would fail. Now if a second group is given the same name as the first, the second one is forced to have a different name (such as group1).
2456 - If a site running with Amazon S3 was upgraded from 5.5 to 5.6, user-uploaded files on S3 appeared missing. This was due to a post attachment folder with upper- and lowercase characters being changed to all-lowercase names (changing the keys). A migration tool has been created to copy and delete all of the files in old (mixed-case) files stores into the lowercase file stores.

1 November 2010: 5.6.583.13179 and 2.6.583.13179

4797 - Mail Gateway failed to log some emails in passive mode. There was a problem in determining which post the email was replying to. This was fixed.
4787 - A passive mailing list was sending mail to the forum, meaning the passive mailing list was not being passive. This was fixed.
631 - You could not use the jQuery Ajax method's cache set to false with REST v2. If you did, the URL generated by the jQuery (which included an underscore) caused an error in REST Console.
675 - The Media Gallery-RSS icon needed to be shifted to the right.
923 - In the communityserver.config files, the mime types needed to have forceDownload="false" so images were not forced to download locally.
1083 - When blogging by email, there is now verification that the email sender has authorization to post to the blog, and the sender is set as the post author.
1020 - Replying to a malformed forum post could lead to content spoofing. We added a class around the forum parent post rendering in the Forum - Create Edit Post widget to prevent content spoofing.
1022 - Theme.config HeaderFragments were using randomly generated IDs that prevented postback events (such as the linkButton_click event) from firing. This was corrected.

Hotfixes for Telligent Evolution 5.6 including Telligent Community 5.6 and Telligent Enterprise 2.6

Jenny Jarrard — Tue, 31 Jan 2012 16:17:58 GMT

Revision 1 posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 1/31/2012 10:17:58 AM

12 January 2012 5.6.583.21914 and 2.6.583.21914
10 December 2011 5.6/2.6.583.21163 and 2.6.583.21163
7 November 2011: 5.6.583.20496 and 2.6.583.20496
5 October 2011: 5.6.583.19849 and 2.6.583.19849
22 September 2011: 5.6.583.19431 and 2.6.583.19431
31 August 2011: 5.6.583.19199 and 2.6.583.19199
15 July 2011: 5.6.583.18163 and 2.6.583.18163
8 June 2011: 5.6.583.17018 and 2.6.583.17018
16 May 2011: 5.6.583.17018 and 2.6.583.17018
25 April 2011: 5.6.583.16466 and 2.6.583.16466
15 March 2011: 5.6.583.15464 and 2.6.583.15464
15 February 2011: 5.6.583.14653 and 2.6.583.14653
17 January 2011: 5.6.583.14036 and 2.6.583.14036
17 December 2010: 5.6.583.13797 and 2.6.583.13797
24 November 2010 : 5.6.583.13623 and 2.6.583.13623
1 November 2010 : 5.6.583.13179 and 2.6.583.13179

12 January 2012 5.6.583.21914 and 2.6.583.21914

13215 - Deleting a conversation message no longer gives an error because the application now checks whether the user has permission to delete a message before processing the delete request.
11510 - Blog Owners can now no longer upload restricted file types. Only users with OverrideValidation globally or on the group level can do so.
13274 -File access validators no longer reject file paths that include subfolders.
13271 - You can now create a username with less than three characters.
13647 - When a wiki page is created, there is no longer an "edited" wiki page activity message in the activity message list, but instead only and "added" wiki page activity message.
14272 - The cs_Group_Update.PRC now updates permissions only on the updated group instead of across all nodes. Previously, all nodes’ permissions were being updated, and this could cause a timeout.
13613 - The Blog Post List widget now loads faster.
13614 - The Tag Cloud widget now loads faster.

10 December 2011 5.6/2.6.583.21163 and 2.6.583.21163

8679 - The following endpoints were backported from trunk (RESTv2) to 5.6 to support SharePoint moving off REST v1 code: /blogs/{blogId}/posts.xml; /groups/{groupId}/forums.xml; /groups/{groupId}/blogs.xml; /groups/{groupId}/wikis.xml; and /groups/{groupId}galleries.xml.
12143 - When hitting the legacy URL redirect for a forum thread [/utility/legacyurlredeirects-forum.ashx?ThreadID=### (using an existing forum thread)]there was an argument out of range exception for the length (e.g., Length cannot be less than zero). This was due to the LegacyUrlRedirectHandler.cs having an invalid call to a substring. We added a conditional to circumvent this problem.
12176 - When you uploaded a file using Chrome, the dialog box no longer overlaps.
12818 - Stateful Quartz jobs (ex. search, ldap sync) now continue to run if an exception is thrown within the job startup.
12840 - The Job Scheduler processing model has changed from processing one type of application at a time to a round-robin approach that indexes x items within the content type and then moves on to the next content handler and comes back to the original after all others have been called. This change was made to avoid blocking other jobs if users needed to be reindexed. Added round robin processing to configurable maximum batch run size to job scheduler. Fixed issue with slow forum thread indexing when sticky posts are present.
12821 - CSValidationException was updated to include all validation errors in the Message property.
12875 - Wiki pages having a significant number of long and extensive revisions no longer cause performance issues with a wiki RSS feed. This was fixed by removing the comparison between versions, so that only new content is displayed in the wiki page’s RSS feed.

7 November 2011: 5.6.583.20496 and 2.6.583.20496

10299 - In sending an email to a blog owner via the contact.aspx page, line breaks in the email were removed. Such messages are now properly formatted. A $core_v2language.NewLine property was also added so this can be edited in the template as well.
10316 - If you responded to a forum post with a suggested answer, then went back into your response and edited it, saving the changes removed the "suggested answer" check mark. This has been fixed.
10300 - There was inconsistent spam engine behavior across applications. For example, forum posts caught by the spam engine were marked as "not approved," while media gallery comments were not caught or marked. This behavior has been corrected for media gallery comments to be marked as "not approved."
10324 - The report abuse forum and deleted forum posts were being subjected to spam filters. This has been corrected so that when the spam rule triggers, Telligent Evolution verifies it is running on a normal (e.g., not deleted or reporting) forum before processing.
10351 - When you set a custom profile field (such as Birthday) as a required field for the join community experience, the field was displayed but not validated. This has been corrected.
10691 - If you added a subgroup to a group containing many sub groups, using a duplicate key (that is, having the same key as another subgroup), you received a validation error - "The group name already exists under the selected parent group." This was due to the application checking only a subset of the groups for duplicates and not the entire set.
10798 - Non-duplicated wiki pages that used punctuation (such as period, dash, or colon) in their titles used numeric page IDs as their page URLs instead of converting the punctuation to spaces in their keys. For example, "Test three-four" as a wiki page title resulted in having an integer page key. This has been fixed.
10857 - This bug fixes an issue that could occur whenever a DNS problem happens and an image is cached in a users’ browser incorrectly.
11175 - The Extended Analytics module of Telligent Analytics was counting validated users' first visits as being by the anonymous user, using a random new guid instead of the user's membership guid. This was fixed so that the Web Analytics table captures the correct user ID the first time through.
11168 - When posting blog comments en masse, the indexes PC_cs_Threads and IX_Posts_Threads in procedure cs_Weblog_Post_Create became deadlocked and stopped the posting. We added nolocks to the two count(*) statements getting the count from te_BlogPost Comments to alleviate the problem.
11029 - Changing a group type previously caused orphaned data in cs_Security_EffectivePermissions, essentially keeping the permissions of the apps as the old permissions. We changed the sprocs cs_Security_EffectivePermissions_Calculate to eliminate corrupting data by pulling from the #temp table instead of the physical table.
10344 - A disabled blog post could previously still appeared via RSS feed. The disabled blog post is now removed from the RSS feed within several minutes of removal from the site.
10364 - If you edited the Registered User role's permissions, site read profile permission (SitePermission.ReadProfiles) was lost from the Registered users role and made users stop appearing in search. This was fixed.
9109 - Some invalid characters were not being removed from posts. XmlSanitization was added to HtmlSanitization so they are not persisted. XML-invalid surrogate unicode characters (as defined by the W3 http://www.w3.org/TR/2000/REC-xml-20001006#charsets) in post titles, bodies, and comments are now stripped.
9444 - The RSS Feed widget was showing an incorrect date for entries. RSS.NET was updated to support time zone abbreviation translations, and the hotfix includes an update to use the new build of RSS.NET.
10399 - This allows for Evolution to know the real IP address for a user who is behind a proxy.

5 October 2011: 5.6.583.19849 and 2.6.583.19849

9533 - In Active Directory, the group membership page add member box showed users with commas in the name (e.g., Johnson, Joe) with the comma turned into characters %2c. This was fixed.
9544 - In Active Directory, the group membership page add member box search returned computer names in addition to usernames. LDAP's user name filters were changed to not return computers when searching for users.
9615 - Forum and Mail Gateway inline attachment validators were added to 5.6/2.6.
9698 - Performing a get Search List request using a url filter for a known site page url that contained punctuation, like a period or comma, returned no results. The code for parsing out that url only considered alphanumeric characters and not other punctuation. This was fixed.
9791 - Changing the value of a profile field with a single selectable list field type did not update correctly; instead, the old value was displayed instead of the new one. This has been fixed.
10147 - The member search page in Control Panel was updated to be over SSL when ssl=Password is set in the communityserver.config file.
9981 - If your list of forums in a group exceeded 20, some forums were excluded from the Forum Moderation page. This was due to a default page size restriction. The returned record limit has been increased.
10149 - When logged out of the site, navigating to a site home page over SSL (e.g., https://site.com) redirected you to the site theme page. This was fixed to return the correct URL.
10178 - When you set ssl=Password in communityserver.config and requireSSL=false in web.config (Forms authentication), any request for https that does not transmit a password is now redirected to http.
10253 - The BaseAtomWriter was updated so that the Atom feed for a blog displays the user's display name rather than his/her username.
10346 - A problem with uploading a file such as an avatar in Firefox 7.0 has been resolved.

22 September 2011: 5.6.583.19431 and 2.6.583.19431

9152 - The secure RSS did not work as expected - if you clicked RSS on a blog in a private unlisted group and copied the URL, you were redirected to the login page when you tried to view the URL. This has been fixed.
7758 - You couldn't add a friend to a conversation if the friend was #21 or higher in your list of friends. This has been fixed.
9540 -The TinyMCE context menu was only supported in IE. TinyMCE has been updated to only show the menu when text is not selected or the user clicks on a <table>, <tbody>, <thead>, <tr>, <td>, or <th> tag. The cut, copy, and paste options were removed from the context menu.
5542 - The new forum post dialog for adding an attachment dialog was not localized; the browse button and form error messages had hard-coded values. The browse button cannot be localized because its caption is set by the browser. The error messages were localized.
9728 - If you gave a blog draft a future publish date, then saved it as a draft (i.e., not published), no publication notification was sent when the blog post was published. This has been fixed.

31 August 2011: 5.6.583.19199 and 2.6.583.19199

7869 - Formerly when you tried to block an IP address behind a load balancer, you could not get an accurate client IP address. This has been addressed.
8595 - It was possible in a forum to add, using the Image Upload button, file(s) whose extensions were not on the allowed extension list (Control Panel > System Administration > Forum Administration > Configuration > Global Forum Settings > Attachments). The attachments are now limited to those in the Control Panel list.
8731 - It was formerly possible to reuse a blog mirrored feed after it had been deleted but the ability was subsequently removed. This capability has been restored.
8732 - The blog lists management page (Control Panel > My blogs > [blog name] > Manage > Lists) didn't allow you to select a different list to manage. This has been fixed.
7884 - Wiki page links containing special characters could be broken after upgrading from 5.5 to 5.6. This is because in 5.6 and up, titles are supplied with HTML encoding while in 5.5, they were not. This problem has been fixed.
8662 - The CSControl:ValueSelectedContent control on uploadpostattachment.aspx now works in non-English sites.
8901 - If you created a wiki post with an uploaded image and set the file date on the server to future, the image could appear as a broken link in IE. This has been fixed.
8650 - If the "Allow Conversations From" option (Control Panel > System Administration > Membership Administration > [user] > Edit > Members and Roles > Manage Users > Email and Contact Info) was set to All Users, setting the "Share this" link did not work for specified members who were not friends. This has been fixed.
9671 - If you tried to add a blog to Windows Live Writer and then entered the URL to a public or joinless blog, you received an "index out of range" message. The code causing this issue has been fixed.
8816 - If, as an admin, you were managing comments for a particular blog (Control Panel > System Administration > Blog Administration > Blogs > [blog name] > Manage), clicking Recent Comments and selecting a blog, then clicking the Publish Selected or Publish button did not return new comments. This has been fixed.
8566 - A registered user who had been granted custom permissions (Blog - Create Posts and Blog - Edit Posts) was unable to edit a post after saving it as a draft. This has been fixed.
9255 (and 9185) - As a friend of a user in a private unlisted group, you could see that group member's private group activity. This has been fixed.
8574 - Calling the cs_Security_EffectivePermissions_Calculate process without a specified node ID caused a timeout because it deleted and inserted a large number of records into the effective permission table. This process has been fixed to use a temp table in order to improve performance.

15 July 2011: 5.6.583.18163 and 2.6.583.18163

6010 - You could get a yellow screen when attempting to view a forum post after changing its date in the database cs_Posts table for a zone which honors daylight savings time (such as [UTC] Dublin, Edinburgh, Lisbon, London). The error occurred because the server was set to Daylight Savings time, but the check box to honor Daylight Savings is not checked - meaning DateTime could create a date and time that did not exist within one hour from the spring forward point. We have updated userTime to check whether the supplied time is valid and, if not, to increment it by one hour. Note: In general we recommend that when you set time zones, you do not try to ignore daylight savings time because the database is not designed for this.
7352 - When calling the ForumThreads endpoint with a query type of Active, announcements were not being returned. We changed the endpoint to use ThreadSet.AllThreads instead of ThreadSet.Threads so that announcements are also included.
7457 - With SSO set up, there could be login problems for users with unvalidated email addresses after upgrading from Telligent Evolution 5.5 to 5.6. For a problem to occur, there were three possible causes: (1) The user had a setting that was valid in 5.5 and not in 5.6, such as an signature length over 255 characters, or an invalid email from an old version of Community Server; (2) SSO had not refreshed the user's profile in at least seven days, and (3) the SSO cookie had not provided a new public email from the single sign-on source. We have changed the setting so that public email and signature are not validated on the upgrade unless the values have changed. In effect, the 5.5 values for email and signature are grandfathered in until they are changed.
8019 - In IE9, the Wikis - Table of Contents widget did not display child pages (it showed a message of "loading") when expanded client-side. This was due to changes made to support IE9. The applicable changes were rolled back, and the widget now works correctly.
8022 - The Quick Post widget did not display a Browse button on its Share a File tab when dropped on the dashboard or user's profile page. media galleries. This was fixed in the code. Note: Search must be enabled for the applications to display the browse button.
8081 - The aggregate blog page showed a future date in its last post column when you set a blog post for a future date. This was fixed.
8103 - If you added a user's display name (different from their username) as a blog owner, the blog author display showed the user's username. This was fixed.
8210 - Accessing the ~/api.ashx/v2/forums/threads/active.xml node in REST for a forum, there could be differing post counts - such as two in TotalCount but one in the <threads> node. This was due to a redundant security check, which has now been removed. The totals now correspond.
8215 - Rating ability could disappear from a forum post after you posted a (non-rich-text) reply. This has been fixed.
8302 - Blog post comment moderation settings made at the blog level could be overridden by changing the setting in the Control Panel. The blog-level setting is now respected.
8506 - Users were automatically resubscribed to all forums in a group when a new forum was added. This has been fixed.
8535 - It was possible for the operation of adding a new role to a group to cause very large sites to time out. This was fixed.
8138 - With SSL set to password (SSL=Password), clicking any other element (such as banner links) on the login page caused you to be directed to unsecure pages over a secure encrypted connection (https). A script error was fixed.
8594 - You could not post to private blogs via Windows Live Writer using the metablog2.ashx endpoint. This was due to an issue with the group ID. It has been fixed.
6963 - In the Control Panel, Manage ranks was changed from using the number of posts to the number of points. The number of posts was previously what the rank in the User Hover showed, and that has now been changed to points. Users might consequently find that they have higher ranks after this change. For example, a rank that was 10 to 50 posts prior to this hotfix would now be changed to 10 to 50 points. Since one post can be worth more than 10 points, fewer posts would be required to reach the rank limit.

8 June 2011: 5.6.583.17018 and 2.6.583.17018

7232 - The popular posts (Forum Administration > Configuration > Global Forum Settings > Popular Posts) minimum number previously only counted posts with more than one reply as popular. The code now will count one reply as popular if you configure this to be the minimum.
7209 - When you created a post-dated blog post and selected its Featured Content check box, the blog post would post on the correct time and but would show its age as incrementing from the time it was actually created instead of its post-dated publication time. (For example, if you created a post at 3:00 p.m. and set it to publish at 3:30, the post published at 3:30 but said it was published 30 minutes prior.) This has been fixed, and the publication age now increments from the actual publication time.
7899 - When you modified roles on a site having a large number of posts (over 3 million), the permissions recalculation ran in addition to the cs_search_reindexall stored procedure; that procedure, which consisted mostly of site-resetting, could cause the two procedures to time out. In order to avoid the timeout, full-site search reindexes have been moved to a background job.
7939 - Fixed low-risk security vulnerability.

16 May 2011: 5.6.583.17018 and 2.6.583.17018

5759 - A user was previously able to delete others' blog posts without having the explicit permission (Blog - delete post) to do so. A user can no longer use the Delete button to remove a post if he/she does not have the authority to do so. However, the following scenarios do allow a user to delete post(s):
- A blog's author can delete any of the blog's posts.
- A user can always delete his/her own posts, even without the explicit Blog - delete post permission.
- A community member with the explicit delete permission can delete any blog post.
5817 - Three issues with IE9 were resolved:
- It wasn't possible to drag/drop widgets or tabs in the page-editing UI.
- There was a JavaScript error in TinyMCE.
- Images or videos could not be inserted via the editor in IE9, and their dialogs presented exception errors upon closing.
We also identified an issue with the Browse button occasionally not triggering the browse dialog if you click the button on the far-outer edges. That was not addressed in this bug.
6221 - In REST remote attachments for blogs, forums, and file galleries, it appeared that the filename and fileurl were being switched due to some repetitive code. While the two content types were not actually being switched, the code was cleaned up.
7047 - If you subscribed to a blog and then unsubscribed to it; changed your email address in your user account, and subscribed to the blog again, this created a duplicate key error resulting in a yellow screen. Blog subscriptions are now properly updated.
7214 - RSS feeds were returning full posts instead of excerpts. This was fixed.

25 April 2011: 5.6.583.16466 and 2.6.583.16466

5943 - Previously it was not possible to configure the height and width of videos. There is now a Media Settings tab (in Site Theme) that allows you to do this.
5944 - When a forum thread was created as a question as well as an announcement, it was missing an opening <div> tag, which caused the announcement to be placed incorrectly. This was fixed.
5867 - Normal (non-admin) users could not edit replies to sticky (forever) posts. This was fixed.
5646 - When you added a role as a group member, it was added with blank permissions rather than those expected for the member. This has been fixed.
5609 - Full-screen mode is now supported for YouTube videos.
5477 - Flood interval checking has been removed from the Control Panel.
1256 - In forums where both Question and Answer and Discussion types were enabled, the Suggested Answer check box could disappear from quick answers to questions. This has been fixed.
5536 - Activity Stream query performance was improved.
5622 - Uploading a PDF via the Add a Media Gallery Post REST v2 endpoint resulted in a "Data at the root level is invalid" error. This has been fixed.
3864 - Status message replies of any length were allowed. The max length restriction of 256 characters is now applied.
4140 - Site-mapping for wikis could cause an issue because null or empty tags were being populated and, in some cases, tags beyond the row count limit were not being selected. This has been fixed.

15 March 2011: 5.6.583.15464 and 2.6.583.15464

4889 - Forum replies from email added an extra space in the subject for each subsequent reply. This was fixed.
5203 - When you clicked Next in a forum to view the following page of a post, you needed to click Next twice. This issue was corrected.
3694 - When flood interval checking was enabled (Control Panel > System Administration > Forum Administration > Configuration > Global Forum Settings > Duplicates > Flooding), multiple posts were allowed within the time limit. This was corrected.
5512 - When the author of a question in a Q&A forum tried to mark a reply to his/her post made by another user as a suggested answer, or as an answer through the Update Forum Reply REST endpoint, it would return an error message that the user did not have permission to edit the reply. This has been corrected.
5238 - If a forum post was created using the mobile interface in a question-only forum, it was created as a discussion instead of question. This has been fixed.
5239 - If you created a thread in a forum supporting both thread types, the thread would be created with the correct type, but its ThreadStatus was "NotSet." (If you did the same on the main site, ThreadStatus was "NotAnswered.") This was corrected.
5390 - The Show Forum REST endpoint did not include the AllowedThreadTypes property. This property was added to RestForum.
3581 - An iTunes RSS feed was previously not generated properly for the modern iTunes standard. It was missing the author tag. This has been corrected.
3760 - The \Languages\en-US\error SiteUrlData.htm page was missing some text. This has been corrected.

15 February 2011: 5.6.583.14653 and 2.6.583.14653

3729 - Server licensing counts counted Job Scheduler on a separate server as a separate server. This has been fixed. Job scheduler on a separate server does not increase server count in licensing.
3758 - A user display name containing an apostrophe formerly could not be found in Control Panel's user search. Such a user is now found.
4139 - Shared membership was not working in 5.6 or trunk, creating an infinite loop. The validator now calls directly to the database, and the update only performs password rules validation for non-shared users so looping does not occur.
3686 - Forum posts - Anonymous users were able to delete/edit other anonymous users' forum posts. Anonymous users are no longer to delete/edit posts.
3706 - When assigning default new friends for a user joining or registering on a site, the Default New User Friends field content is now saved.
3953 - Changing a user profile page layout didn’t render when modified more than once. This has been corrected.
4533 - Wiki pages were not being flagged to be re-indexed when a group type was changed. This was fixed.
4272 - It was not possible to remove a license if a site was out of compliance for server counts. Servers are now properly deregistered.
3545 - We investigated searching *.docx text in file attachments and found it doesn't work on Windows 2003 R2 64 and Windows 2008.
3760 - \Languages\en-US\errors SiteUrlData.htm had some missing text. This was corrected.
428 - Control Panel - Content/site security - When a user added an incorrect IP address to the Address Banning page, a warning was displayed; when that IP was deleted or corrected, the warning was still displayed. This has been fixed.
609 - The Files-Download counter-Generate report option kept the same generation dates even if one or both of them changed. This has been fixed.
3578 - If a group name was too long, it was not broken to the next line on application pages.This has been fixed.
2602 - RSS and Atom feed handlers declared "Community Server" for the "Generator" field. This has been changed to "Telligent Evolution."
392 - If you edited a group from the main group and deleted any application, you weren't redirected to the site root group page (but instead were left on the same application page). This has been corrected.
386 - It was possible for a user to save his/her changes to a previously locked wiki page. This has been fixed.
3503 - Automatic activity message delivery was not working correctly. This has been fixed.

17 January 2011: 5.6.583.14036 and 2.6.583.14036

2744 - If you added an attachment to a forum post sent to a group without a media gallery, the attachment was dropped in emails. Forum list emails with attachments sent to groups with or without media galleries now show the attachment correctly.
2746 - If a user was set up not to receive HTML emails (Settings > uncheck Receive HTML emails), email from a wiki subscription was still sent in HTML. Wiki pages can now be rendered in plain text in emails.
2511 - When a user set his/her out-of-office email response, the message was sent in response to forum post notifications and then it remained in the SMTP dropbox instead of being deleted. This has been fixed.

17 December 2010: 5.6.583.13797 and 2.6.583.13797

1528 - The Activity List widget on the user profile displayed all users' activity to anonymous users. The widget was updated to support the "userprofile" mode when rendered to an anonymous user.
2082 - Auto-linking was updated to also be supported when using the (Please visit the site to view this file) embed code within HTML content. The link was updated not to open in a new window.
2583 - File viewers were fixed to honor the theme-defined maximum width/height. The fix ensures that embedded video is scaled to fit within the bounding box of the requested width/height using the same logic as image resizing.
1191 - The breadcrumb on the tags page were using the URL string for tag display rather than the tag as written in the database (such as if lowercase in the URL, being displayed all lowercase in the breadcrumb). SiteUrls.config was updated to identify that URLs containing tags should not be forced to lowercase.
2799 - Anonymous users can no longer access the Invite User page.
2593, 1252 - When code was entered into posts using the HTML source editor, JavaScript was being commented out twice - stopping inline JavaScript from working. HTML comments within a UL tag were generating an extra UL tag. We added support for HTML comments and CDATA elements in the HtmlSanitizer.
2601 - Creating a media gallery post could cause a reset when mousing over an anchor. The method that caused it was removed.
1786 - CS 2.1 attachment links were not resolving when upgrading to 5.5. This was fixed in 5.5 and 5.6.

24 November 2010: 5.6.583.13623 and 2.6.583.13623

373 - (Mobile): ForumService.CreateReply did not set the post subject when creating a reply to a thread. This was corrected.
1134 - Pages created in a non-English language could get duplicate page keys. The pages are now compared and if they have similar names, unique keys are generated.
1038 - Searching for a term could cause the browser to start hanging and generate a script warning. To remedy this, the result body was removed from the JSON word wheel search JSON response.
1183 - When a user changed his/her language to Japanese (JAJP), the date did not change to Japanese. If the language was changed back to ENUS, the date displayed in Japanese with English. This was fixed.
1192 - ATOM feeds had relative URLs instead of absolute URLs in them, causing external ATOM readers not to find the feed. The URL is now absolute.
1210 - If you entered a comment as an anonymous user on a blog post that you could receive the subsequent email notification on, the email version of the comment showed an anonymous user sent the email (instead of the name entered on the comment form). The activity list will not show the name entered on the comment form, it will still show anonymous. The email will show the name entered on the comment form.
1248 - Our locking patterns were updated to only use Monitor locks instead of ReaderWriterLockSlims.
1260 - Japanese strings could be improperly truncated halfway through a single character. Support was added to properly truncate strings that use surrogate pairs to form letter glyphs.
2312 - Configuration settings for valid media file extensions were being ignored, and they were only possible to permit or restrict on a gallery-by-gallery basis. Now only valid file extensions are allowed to be uploaded to media galleries by users who do not possess validation permissions. Remote files are checked for allowed file extensions or file viewers.
2340 - Forum attachment support was corrected to allow attaching remote URLs that don't pass file type validation but do have file viewers.
2422 - Blog attachment support was corrected to allow attaching remote URLs that don't pass file type validation but do have file viewers.
2498 - We improved performance by removing license checks for post and comment counts since these counts were not used.
2553 - It was possible to view future published blog posts if you knew the URL. A date check was added, and only users who can post to the blog can view future-dated posts.
2495 - A blog post remained in RSS and search after its status was changed from published to disabled or draft. The search csmodule was updated to flag blog posts for deletion when they go from a published to unpublished.
2419 - If enable passive mode (for email) was set to yes, email notifications were not sent to group members - whether internal or invoked by the post. You had to set Passive Mode=No in order to send email notifications; and group members could receive duplicate posts. This was introduced by 4787. It has been fixed.
1554 - When you used Customize mode to customize a new tab with widgets, locked widgets could be displayed on the home page. This was fixed.
1541 If a parent group and child group had the same name, updating the parent group would fail. Now if a second group is given the same name as the first, the second one is forced to have a different name (such as group1).
2456 - If a site running with Amazon S3 was upgraded from 5.5 to 5.6, user-uploaded files on S3 appeared missing. This was due to a post attachment folder with upper- and lowercase characters being changed to all-lowercase names (changing the keys). A migration tool has been created to copy and delete all of the files in old (mixed-case) files stores into the lowercase file stores.

1 November 2010: 5.6.583.13179 and 2.6.583.13179

4797 - Mail Gateway failed to log some emails in passive mode. There was a problem in determining which post the email was replying to. This was fixed.
4787 - A passive mailing list was sending mail to the forum, meaning the passive mailing list was not being passive. This was fixed.
631 - You could not use the jQuery Ajax method's cache set to false with REST v2. If you did, the URL generated by the jQuery (which included an underscore) caused an error in REST Console.
675 - The Media Gallery-RSS icon needed to be shifted to the right.
923 - In the communityserver.config files, the mime types needed to have forceDownload="false" so images were not forced to download locally.
1083 - When blogging by email, there is now verification that the email sender has authorization to post to the blog, and the sender is set as the post author.
1020 - Replying to a malformed forum post could lead to content spoofing. We added a class around the forum parent post rendering in the Forum - Create Edit Post widget to prevent content spoofing.
1022 - Theme.config HeaderFragments were using randomly generated IDs that prevented postback events (such as the linkButton_click event) from firing. This was corrected.

Release notes

Jenny Jarrard — Tue, 31 Jan 2012 16:17:26 GMT

Current Revision posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 1/31/2012 10:17:26 AM

This section contains the following subsections and articles:

Use search in a web farm

Jenny Jarrard — Thu, 12 Jan 2012 20:59:49 GMT

Current Revision posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 1/12/2012 2:59:49 PM

This information is only applicable to Telligent Evolution release 5.6, not 5.0, 5.1, or 5.5.

To use search across more than one server, you need to use a master/slave configuration of Solr. For more information of this, refer to the Solr documentation. In this setup, reads can happen from any search server, but writes must be done on the master server. The way to ensure this is that the Job Scheduler interacts directly with the master server, whereas the Telligent Evolution can access any of the search servers through a load balancer.

With two search servers, there are two options (which are equivalent if you only have one community search):

The first setup alternative is:

Server A - Contains master node for all Solr instances
Server B - All Solr instances are slaves of masters on Server A

Note that in this setup, you will need to use a weighted load-balancing algorithm on your load balancer because the master servers have more traffic to deal with given that the Job Scheduler always interacts with the master node.

Second setup alternative:

Server A - Contains master Solr instances for half of your communities and slaves for the other.
Server B - Contains master Solr instances for half of communities with slaves on Server A; contains slave Solr instances for instances with masters on Server A.

With more than two search servers, you can choose whether or not to include the master server in the load balancer used by the community to access the search index. By including the master, you need to pay careful attention to the load-balancing algorithm used by the load balancer to ensure that the load balancer sends more traffic to each of the slaves than to the master in order to compensate for the fact that the master naturally has a higher load due to interacting with the Job Scheduler.

Adjust the schedule of a job in Telligent Job Scheduler

Jenny Jarrard — Mon, 09 Jan 2012 19:55:01 GMT

Current Revision posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 1/9/2012 1:55:01 PM

In previous versions of Telligent Evolution, tasks could be turned off by commenting out the task in the tasks.config file. Due to a change in architecture in release 5.6, commenting out a job in the Telligent Job Scheduler does not prevent the task from running. Instead, the schedule for a job should be set to a date far in the future.

Navigate to the tasks.config file from the Job Scheduler directory.
Open this file in an editor such as WordPad.
Adjust the job as desired by changing its CRON expression.

For example,
```
0 0 0 1 1 ? 2075
```
will schedule a job to run in the year 2075, preventing it from running until then.
Restart the Job Scheduler,

It's recommended that you leave a comment in the tasks.config file to explain any change you make to the schedule. It's also recommended that you log the previous schedule in case the job needs to be run again.

Restart Telligent Job Scheduler

In Windows, navigate to Start > Run.
In the text box, type services.msc and press Enter on the keyboard. The services window appears.
In the Name column,locate Telligent Job Scheduler.
Right-click the job and select Restart.

Tags: 5.6

Set up Mail Gateway with Microsoft Exchange 2007

Trevor Alexander — Tue, 03 Jan 2012 16:26:04 GMT

Current Revision posted to Telligent Evolution Platform and Applications Documentation by Trevor Alexander on 1/3/2012 10:26:04 AM

In order to use addresses with the main domain, the only route is to create accounts for each of the addresses you'll need, and then configure Mail Gateway to download messages from them. You cannot use aliases because Outlook 2007 with often override the alias address with the main account address, causing undesired behavior.

Configure DNS

Within your network, you will need to create a DNS entry for the subdomain on which you will be running Telligent Evolution.

Open the DNS Manager, navigate down to your domain.
From the Action menu, select New Host (A or AAAA).
Enter just the portion of the subdomain before your main domain (so in our example of evodemo1.evodemo.com, we would enter demo).
Under the fully qualified domain name, it will show you the corresponding full name of groups.company.com.
Enter the IP address for the server that will be running Telligent Evolution.
Click Add Host.

top

Configure Exchange 2007

To configuring Exchange 2007, you will need to create an Accepted Domains entry for groups.company.com. Exchange 2007 will automatically route emails based on the DNS for the accepted domain. So in our example, when it will receives an email for users@groups.company.com, it will find groups.company.com in the Accepted Domains list; then look up the DNS entry for groups.company.com, and then forward the message to that server via SMTP.

To add an accepted domain:

Open the Exchange Management Console.
Expand Organization Configuration from the side menu and select Hub Transport.
Go to the Accepted Domains tab to see a list of existing entries.
From the Actions menu or sidebar, select New Accepted Domain.
Pick a name for the entry.
Set the Accepted Domain to the subdomain for Telligent Evolution (groups.company.com in our example).
Select the type of Internal Relay Domain.
Click New for it to be created. The result should resemble the following screen shot.

After updating, the list will refresh with the new entry:

top

Configure SMTP on the Telligent Evolution server

We usually recommend running default IIS Virtual SMTP server on the server where Telligent Evolution will be running in order to receive messages coming from the main Exchange server. By using the built-in SMTP server, it gains additional security options such as supporting SPA, TLS/SSL, and much more.

To install the SMTP server:

Open the Server Manager.
Navigate to Features and choose Add Feature.
Select the SMTP Server feature. To manage the SMTP server, you will also need to ensure you have the IIS 6 Management Console installed from the Role Services for the Web Server (IIS) role.
To configure it:
1. Go to the Start menu.
2. Under Administration Tools, choose Internet Information Services (IIS) 6.0 Manager.
3. Expand the sidebar and you will see SMTP virtual server.
4. Open the server's properties by right-clicking it and navigating to Properties:
  - Ensure it is configured to use the IP address that we previously set up for the domain (groups.company.com in our case).
5. Next, go to the Domains item in the sidebar under the SMTP virtual server. The default entry likely corresponds to the computer's name. If it isn't the subdomain for Telligent Evolution, navigate to Action > New > Domain.
6. Create a new alias entry for the Telligent Evolution subdomain. This will allow it to receive email for both the default name, and the Telligent Evolution subdomain.
7. Finally, open the Options on the default domain entry and take note of the Drop directory setting. This is the location where the SMTP server will write all of the messages it receives, so this will be where Telligent Evolution reads messages.

top

Configure the Mail Gateway service for Telligent Evolution

Install the Telligent Evolution Mail Gateway following the normal instructions for Mail Gateway, but when configuring the mailgateway.config file, add an additional setting for readFromDirectory to the <Sites /> line. The entry should correspond to the drop directory setting that was configured in the SMTP virtual server.

It is also recommended that you adjust the pollMessagesInterval. This will set Mail Gateway to read the messages from the directory more frequently for a speedier response. The setting is in minutes, with the default being 5, but you can lower it to 1.

top

After finishing these steps, continue with the final configuration steps for Mail Gateway.

Remove tags from posts

Jenny Jarrard — Thu, 15 Dec 2011 16:05:44 GMT

Current Revision posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 12/15/2011 10:05:44 AM

As you build your Web site, you may want to separate a post from a tag. There could be many reasons to do this: For example, you might determine that a tag is misleading for the post content. Telligent Evolution gives you the option of separating a single post or multiple posts from a tag without deleting the tag.

To remove tags from posts:

Navigate to Control Panel Dashboard > Forums Moderation > Tags > Moderate Tags. The list of tags and number of posts with the tags are displayed in the workspace.
Click the post in the Posts column to display a tag moderation page.
Select the check box for each post in the list from which you are removing the tag and click Remove from Tag. The item is removed from the list.

Tags: forum

IE9 support for Telligent Evolution 5.5 and 5.6

Alex Crome — Wed, 07 Dec 2011 17:37:02 GMT

Current Revision posted to Telligent Evolution Platform and Applications Documentation by Alex Crome on 12/7/2011 11:37:02 AM

To support IE9 without forcing it into compatibility mode, request the latest hotfix from Telligent Support.

To support Microsoft Windows Internet Explorer 9 on Telligent Enterprise 2.5 or 2.6 sites or Telligent Community 5.5 or 5.6 sites, you need to force the browser to render in Compatibility Mode.

To do this:

Open up each of the following files from your community website in a text editor
- Themes\generic\Common\master.master
- Themes\generic\Common\modal.master
- Themes\Groups\generic\theme.master
- Themes\Blogs\generic\theme.master
To each file, add the following code immediately after the opening <head> tag
```
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" />
```

Media file options

Jenny Jarrard — Mon, 28 Nov 2011 15:08:22 GMT

Current Revision posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 11/28/2011 9:08:22 AM

Access the File Options page to control files properties for the gallery. You can:

Control whether or not users can add files to the gallery.
Enable file and comments moderation.
Control whether or not the gallery owner is notified when there are files and comments to be moderated.
Enable file ratings capability.

To set the file options properties:

Navigate to Control Panel Dashboard > Manage My Media Galleries > [media gallery] > Settings > File Options.
Set the File Options page properties:
1. Moderate Files - Files uploaded to the media gallery must be moderated. This setting will not affect administrators and media gallery owners (or specifically, users who have the Media Gallery - Override Validation permission) because their files do not require moderation.
2. Enable File Notifications - Media gallery owners are notified via email each time a file is uploaded to the media gallery.
3. Enable Ratings - Authenticated users can rate media gallery files. Anonymous users do not have access to the rating functionality.
4. Enable Comments - Users can comment on files in the media gallery.
5. Moderate Comments - Comments posted on the media gallery require moderation. This setting will not affect administrators and media gallery owners (or specifically, users who have the Media Gallery - Override Validation permission) because files their files do not require moderation. (Read more about moderating files.)
6. Enable Comment Notifications - Media gallery owners are notified via email each time a comment is posted on the media gallery.
Click Save to apply the settings.

Related information

Gallery setup - Access the Gallery Setup page to modify the media gallery title and description.
Moderator's Guide - Learn more about moderation.
Presentation - Access the Presentation page to set the View Type default for your gallery files.
RSS options - Access the RSS Options page to set syndication properties for the media gallery.

Tags: comment

Installation Guide

Jenny Jarrard — Thu, 17 Nov 2011 19:38:04 GMT

Current Revision posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 11/17/2011 1:38:04 PM

The Installation Guide walks you step-by-step through a new installation, an upgrade from a previous version of the Telligent Evolution platform, or an upgrade from Community Server 2008+ or Community Server Evolution 1.0. Once you install the platform, you can set up your community using the Community Setup Guide, which includes authentication, integration for LDAP or Active Directory and other common enterprise applications.

Configuring the environment

The Telligent Evolution platform is built on Microsoft's .NET platform. It has both software and hardware requirements to provide optimal experience and performance.

Topology descriptions, layouts, and specifications

The Telligent Evolution platform can scale and grow based on the demands of your community. If you are unsure of what you'll expect in terms of page views/month for your community, we can assist you in a planning/strategy session to recommend a configuration appropriate for you based on your goals and growth expectations. We have outlined recommended topologies and server configurations here based on five ranges of monthly page views (for Telligent Community) or number of employees (for Telligent Enterprise):

Less than one million page views or less than 2,000 employees
One to three million page views or 2,000 to 25,000 employees
Three to eight million page views or 25,000 to 50,000 employees
Eight to 400 million page views or 50,000+ employees
Over 400 million page views

Note: Page views are defined as any URL request for service via the Telligent platform including content (e.g., views to a blog or to a forum thread); files (e.g., files served out of the Telligent media gallery; RSS requests, and Platform API calls.)

Topology for less than 1 million page views/month (or less than 2,000 employees)

Description of this topology

The Telligent Evolution platform resides on a dual cluster behind a load-balancer and a firewall, with a single dedicated database with a cold fail-over strategy.

Search must be running on one of the Telligent platform Web servers.
When greater than one physical application server is used, one of the two servers must be running the Telligent Task service if no dedicated background server is available.

For web and database server specifications and configurations, see [[documentation:Supported disk space, memory, and CPU specifications]].

Topology for 1 million to 3 million page views (2,000 to 25,000 employees)

Description of this topology

This is a highly recommended network topology because Telligent Analytics and Telligent Search and Tasks are isolated for fault tolerance and scalability.

For web and database server specifications and configurations, contact Telligent.

Topology for 3 million to 8 million page views (25,000 to 50,000 employees)

Description of this topology

This configuration adds fault tolerance to the network appliances (load-balancer and firewall) and to the production database for hot fail-overs with SQL Server database clustering. Telligent Tasks and Telligent Search are run on separate dedicated servers.

For web and database server specifications and configurations, contact Telligent.

Topology for 8 million to 400 million page views (50,000+ employees)

Description of this topology

This configuration introduces a content distribution network (CDN), dedicated/distributed file replication for the application servers, distributed search and data caching, and mirrored, clustered for all database activity.

For web and database server specifications and configurations, contact Telligent.

Over 400 million page views

Requires additional hardware and custom configurations. Please contact us to discuss how our system fits your needs.

Now, install or upgrade your community:

Tags: 5.6

Moderator's Guide

Jenny Jarrard — Thu, 17 Nov 2011 16:44:18 GMT

Current Revision posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 11/17/2011 10:44:18 AM

A community moderator is responsible for ensuring that the content within the community is appropriate for all community members. Depending on how your administrator configured your community, you may be responsible for only one forum, for content for a single group, or for content across the entire community. You may need to only moderate content when it is reported by members of the community or may also be responsible for approving content before it is posted. Contact your administrator if you are unsure the level of moderation that you are required to perform.

This guide contains the following sections:

Moderating comments - Set up email notifications of forum comments.
Moderating forums - Specify or change settings for anonymous forum posting; moderation; post merging/moving/splitting; moderate tags, or move a post to a different forum.
Moderating posts - Establish the rules for forum post moderation.
Moderating users - Set the properties for user moderation.

This article explains gallery file moderation setup.

Tags: approve

Blog management settings for users

Jenny Jarrard — Thu, 17 Nov 2011 16:35:38 GMT

Current Revision posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 11/17/2011 10:35:38 AM

As a blog user, you have limited abilities on blogs that are placed in Group-controlled folders (basically post and subscribe). However if a blog is placed at the site root, many management settings are available to you - rights that would otherwise only be available to a blog owner. (Since the blog resides at the site root, you essentially are a co-owner of the blog.) This section lists and describes the management operations you can perform.

This section contains the following articles and subsections:

Editing a tag - Customize the tag(s) by which your blog post is surfaced by SEO (search engine optimization) or how it appears in a tag cloud.
Manage blog feedback - Approve or delete feedback entries.
Manage blog lists/blogrolls - Create, edit, or delete blog lists.
Manage blog posts - Manage feedback, posting, and publication options.
Manage blog snippets - Create or organize bits of text that serve as hyperlinks to other pages/text.
Manage blog spam - At the comment level, elect to delete a comment as spam or de-spam (i.e., validate) it.
Manage blog tags - Add, change, or delete tags.
Manage files uploaded to a blog - Upload or delete stored files, or create new folder(s) to organize them.

Manage a media gallery

Jenny Jarrard — Thu, 17 Nov 2011 16:24:14 GMT

Current Revision posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 11/17/2011 10:24:14 AM

Media gallery management allows you to manage the content contained within an individual media gallery and control additional settings that are not included when you create a file gallery.

The following functions are covered in managing media galleries:

Gallery setup properties - Modify the media gallery title and/or description.
Increase the maximum size of file uploads - Modify the web.config file to increase the file upload capability by increasing the upload runtime.
Manage media gallery files - Edit, delete, publish, or unpublish files.
Manage media gallery tags - Create, edit, or delete tags.
Media file options - Control media gallery upload, comments, moderation, and ratings.
Presentation properties - Choose whether to list media gallery files or show thumbnails of their images.
Quick upload - Upload a file without adding any properties to it. (Long file names will be truncated.)
Required folder permissions - File folder permissions required by Network Service accounts or ASP.NET for proper media gallery access.
RSS Options properties - Enable/disable media file RSS feed capability as well as syndication and tag settings.

Tags: comment

Moderate posts

Jenny Jarrard — Thu, 17 Nov 2011 15:57:51 GMT

Current Revision posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 11/17/2011 9:57:51 AM

Telligent Evolution lists all of the forum posts that require moderation on the Forums to Moderate page.You can enable the moderation notification setting so that you do not have to periodically check the page for posts requiring moderation. Telligent Evolution notifies you via email when posts are queued in moderation list.

To moderate posts:

Navigate to Control Panel Dashboard > Forums Moderation > Posts.
Click the forum you want to moderate in the Forums to Moderate list. The list of forum posts displays in the workspace.
The moderating action buttons appear across the top and bottom of the page.
Specify the moderating action you want to take for the post:
- Approve - Approve the post.
- Approve & View - Approve the post and view the post.
- Delete - Delete the post.
- Join - Merge the threads of multiple posts. The Join functionality displays only if the post has multiple threads or has been previously split. If the thread has been joined, the Split Post button displays instead of the Join button.
- Move - Move the post to a different forum.
- Edit User - Edit the user profile.
- Moderate/Unmoderate User - Change whether the user is moderated or unmoderated. If the Moderate User button displays, the user is currently unmoderated, and vice versa.

Related information

Tags: approve

Media file options

Jenny Jarrard — Thu, 17 Nov 2011 15:56:42 GMT

Revision 15 posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 11/17/2011 9:56:42 AM

Access the File Options page to control files properties for the gallery. You can:

Control whether or not users can add files to the gallery.
Enable file and comments moderation.
Control whether or not the gallery owner is notified when there are files and comments to be moderated.
Enable file ratings capability.

To set the file options properties:

Navigate to Control Panel Dashboard > Manage My Media Galleries > [media gallery] > Settings > File Options.
Set the File Options page properties:
1. Moderate Files - Files uploaded to the media gallery must be moderated. This setting will not affect administrators and media gallery owners because their files do not require moderation.
2. Enable File Notifications - Media gallery owners are notified via email each time a file is uploaded to the media gallery.
3. Enable Ratings - Authenticated users can rate media gallery files. Anonymous users do not have access to the rating functionality.
4. Enable Comments - Users can comment on files in the media gallery.
5. Moderate Comments - Comments posted on the media gallery require moderation. This setting will not affect administrators and media gallery owners because files their files do not require moderation. (Read more about moderating files.)
6. Enable Comment Notifications - Media gallery owners are notified via email each time a comment is posted on the media gallery.
Click Save to apply the settings.

Related information

Gallery setup - Access the Gallery Setup page to modify the media gallery title and description.
Moderator's Guide - Learn more about moderation.
Presentation - Access the Presentation page to set the View Type default for your gallery files.
RSS options - Access the RSS Options page to set syndication properties for the media gallery.

Tags: notification, enable, file, moderate, comment, media gallery, manage

Manage a media gallery

Jenny Jarrard — Thu, 17 Nov 2011 15:53:03 GMT

Revision 13 posted to Telligent Evolution Platform and Applications Documentation by Jenny Jarrard on 11/17/2011 9:53:03 AM

Media gallery management allows you to manage the content contained within an individual media gallery and control additional settings that are not included when you create a file gallery.

The following functions are covered in managing media galleries:

Media file options - Control media gallery upload, comments, moderation, and ratings.
Gallery setup properties - Modify the media gallery title and/or description.
Increase the maximum size of file uploads - Modify the web.config file to increase the file upload capability by increasing the upload runtime.
Manage media gallery files - Edit, delete, publish, or unpublish files.
Manage media gallery tags - Create, edit, or delete tags.
Presentation properties - Choose whether to list media gallery files or show thumbnails of their images.
Quick upload - Upload a file without adding any properties to it. (Long file names will be truncated.)
Required folder permissions - File folder permissions required by Network Service accounts or ASP.NET for proper media gallery access.
RSS Options properties - Enable/disable media file RSS feed capability as well as syndication and tag settings.

Tags: RSS, publish, upload, disable, enable, file, moderate, permission, comment, media gallery, manage

Telligent Evolution Platform and Applications Documentation

Email Templates

In this Article

How to customize an email template:

Global Terms

Account notifications

forgottenpasswordwithtoken.txt message file

newuser_accountcreated.txt messages file

newuser_approved.txt messages file

newuser_generatedpassword.txt messages file

newuser_pending.txt message file

newuser_rejected.txt message file

roleemail.txt message file

user_changedpassword.txt message file

user_forgottenpassword.txt message file

userinvitation.txt message file

userinvitation_withsection.txt message file

Blog notifications

weblog_feedbacknotification.txt message file

weblog_moderationthreshold.txt message file

weblog_newcomment.txt message file

weblog_newpost.txt message file

weblog_subscriptionconfirmation.txt message file

Contact notifications

contactform.txt message file

contactform_usertouser.txt message file

Forum notifications

forumpost_mailgateway.txt message file

forumpost_messageapproved.txt message file

forumpost_messagemoved.txt message file

forumpost_messagemovedandapproved.txt message file

forumpost_messageremoved.txt message file

forumpost_notifymoderators.txt message file

forumpost_notifythreadstarterofanswer.txt message file

forumpost_notifythreadstarterofsuggestedanswer.txt message file

forumpost_postnotification.txt message file

forumpost_threadmovednotracking.txt message file

forumpost_threadmovenotification.txt message file

forumpost_threadnotification.txt message file

Friendship notifications

followers_notification.txt message file

friendship_approved.txt message file

friendship_requested.txt message file

friendship_requested_nomessage.txt message file

Group notifications

group_accessaccepted.txt message file

group_accessrequest.txt message file

group_accessrequestdenied.txt message file

group_useradded.txt message file

Media Gallery notifications

mediagallerypost_commentnotification.txt message file

mediagallerypost_newcomment.txt message file

Message notifications

group_messages_also_replied.txt message file

group_messages_reply.txt messages file

messages_also_replied.txt message file

messages_newconversationmessage.txt messages file

messages_newprofilecomment.txt messages file

messages_reply.txt messages file

messages_spam.txt messages file

messages_spam_deleted.txt messages file

messages_spam_deleted_user.txt messages file

Wiki notifications

wikis_definitespam.txt message file

wikis_pageupdated.txt message file

wikis_possiblespam.txt message file

Customizing email replies to reply to the entire group whether you click Reply or Reply All

Email Templates

In this Article

How to customize an email template:

Global Terms

Account notifications

forgottenpasswordwithtoken.txt message file

newuser_accountcreated.txt messages file

newuser_approved.txt messages file

newuser_generatedpassword.txt messages file

newuser_pending.txt message file

newuser_rejected.txt message file

roleemail.txt message file

user_changedpassword.txt message file