The 14.8 Release includes a variety of fixes to customer-found issues as well as a couple of enhancements. We have also added two new API calls to remove a user’s email from the notification email list and to find a message’s position within its thread.

New features and enhancements

• Bump topic to top of board when merging articles
• Ability to export the Audit Log
• API changes

Bump topic to top of board when merging articles

From time to time, you might need to merge one forum topic into another. When you do this, you might want to have the merged topic display at the top of the board list, to indicate that an update has been made, even if the content isn’t new.

 

You now have the option to “bump” a topic to the top of the list when you merge a forum topic.

 

To bump a merged topic to the top of the list:

1. Sign in to the Community as a user with permission to move posts.
2. Find the topic you want to move and merge.
3. Open the Article Options menu and click Move Article.
   
4. Under Destination Action, select Merge with an existing topic, article, idea, or entry.
   
5. Enter the Destination Post ID of the topic you want to merge with.
6. Click Bump topic to top of list (Forum only) to have the merged topic display at the top of the board’s list.
7. Click Move Post.

Ability to export the Audit Log

The Audit Log is one of the most effective forms of tracking information. The idea is that any time something significant happens, we record it and capture what happened, when it happened, and who did it. In Audit log, you can find most of the actions that an Admin takes.

Some of the actions captured in the audit log include deleted or moved posts, added or changed roles, added or changed custom content, and much more.

Sometimes, the Audit Log can be quite large. Instead of clicking through pages of log entries, you can now export the log to Excel, where you can more easily search for the entry you want to find.

 

To export an audit log:

1. Sign in to the community as an Administrator or Moderator.
2. Go to Community Admin > Mod Tools.
3. Click Audit Logs.
   
4. Set the date range you want and click Refresh.
5. Click Export.
6. Open the generated Excel file.
   

Note: The audit log is capped at 500,000 line items. If your log exceeds that limit, narrow your date range.

API changes

With 14.8, we have added two new calls to remove a user’s email from the notification email list and to find a message’s position within its thread. In addition, we have made improvements to filters used to retrieve topic messages from boards.

Remove a user’s email address from an email list

/users/email/{email}/do_not_email

 

Pass in a user’s email address to remove them from the community notification email list. Other community notifications, such as pop-ups and the notification feed still must be enabled for the user.

 

The call works on a per-user basis. Customers must iterate through lists of users and make repeated calls for multiple users who should not receive email notifications.

Retrieve a message’s position in a thread

/messages/id/{id}/position_in_thread  

 

Pass in the message ID to find its position in its thread. The root/topic message is message “1”, and the call assumes that the thread is sorted in Linear view by ascending date. This example shows a successful response indicating that the message is the 19th message in the thread:

 

<response status=“success”>

     <value type=“int”>19</value>

</response>

Improvements to Boards/topics/recent

This call now supports the value “drafts” in addition to “moderator” and “public” for the visibility.scope parameter. In addition, the call can now take the revision.state parameter to filter the topics returned. The revision.state parameter currently accepts only “any” as the value.

You Found It. We Fixed It

• Users subscribed to a particular board were mistakenly receiving notifications for messages in that board that were flagged as spam. This issue has been fixed.
• Previously, when the Spam Quarantine service was down for 30 minutes or more, subscription notifications were not being published. Moreover, when the Spam Quarantine service was restored, additional subscription notifications were sent out. Both of these issues have been fixed.
• Filtering for different “star” ratings in reviews now displays the correct list of reviews that match the selected star rating (for example, all 3-star or 4-star ratings).
• Previously, when a user with administrator permissions used the Private Support Manager to create a support case from a thread, non-admin users received an error and could not view the thread. This issue has been fixed.
• When drafts are enabled for Blogs, any added tags are now saved when you save the draft.
• Some Ratings and Reviews sort orders (highest rating, lowest rating, and helpfulness) were not being sorted correctly. All Ratings and Reviews sort orders are now performing as expected.
• When someone edited a label in Community Admin > Features > Labels and left the label value blank, it used to cause an unexpected error on the posts that included the now-blank label. Furthermore, if this occurred on a node where labels are displayed on the landing page (for example, on a blog or TKB page), the page also returned an error. These errors no longer appear.
• When sending bulk private messages with Private Messenger, the message body was not being included in the notification email, even when the Show Private Message body in the email under Community Admin >Features > Private Messages was enabled. This behavior has been fixed.
• When inserting a URL in the Insert link field while creating a post, you can choose whether the URL opens on the page you’re on or in a new page. Previously, no matter which option you chose, the link always opened in a new window. This behavior has been fixed, and the URL now opens in the way set from the Target drop-down menu in the Insert link
• Previously, if you sent a Private Message to 2 or more users and one of those users had email notification enabled for private messages, the following happened:
  • an unexpected error occurred
  • the private messages were sent, but not the email notification
  • the person sending the message was returned to the private message edit screen, giving the impression that the message was not sent.

These issues have been fixed, and now the user is taken to the Sent Messages page, the private message and email notifications are both sent, and no error is produced.

 

Refer to the attached Known Issues list for an update on open issues that we’re currently investigating.