­­The 15.8 Release provides a few targeted improvements for image upload quota rules and the Posts & Topics authentication setting. On the API side, we’ve added a new Message resource field and FreeMarker object.

New features and enhancements

• Improved image upload quota rules
• Enhancement to the Posts & Topics authentication setting
• New field on the Message resource
• New FreeMarker context object

Improved image upload quota rules

We’ve made several improvements to the image upload experience, including:

• Increased the maximum number of images users can upload: You can now set the Maximum number of uploaded images per user to 10,000. The default value (1000) has not changed.
• Ability to cap the number of images users can upload within a 24-hour period: You can now limit the number of images users can upload within a 24-hour period. By default, this value is set to 1000, but can be set up to 10,000.
  Note: This setting applies to a 24-hour rolling window, not a "daily" cap.

You can set these options under Community Admin > Features > Images:

 

 

 

New permission to enable users to bypass image upload restrictions

In conjunction with the new image upload changes listed above, we’ve added a new permission to enable you to control which users or roles can ignore these image upload restrictions.

 

To set the default image upload limit permission for all users:

1. Go to Community Admin > Users > Permissions.
2. Scroll down to the Images group.
   
3. Set the Bypass image upload limit permission as needed.
   
   
4. Click Save.

 

To set the image upload limit for specific roles:

1. Go to Community Admin > Users > Permissions.
2. Click the Roles
3. Click Edit for the role you want to modify.
4. Scroll down to the Images group.
   
5. Set the Bypass image upload limit permission as needed.
   
   
6. Click Save.

Enhancement to the Posts & Topics authentication setting

We have enhanced the authentication setting for posts and topics. Previously, we had the Authenticate visitors when they post setting, which controlled whether you required users to sign in before creating a new post.

 

We have relabeled this setting and extended its functionality. Now, the setting is labeled Authenticate users and has these options:

• Before they can write their post
• When they submit their post

In addition to the authentication for new posts, this setting now also applies to forum replies and comments on Ideas.

 

To change the Posts & Topics authentication settings:

1. Go to Community Admin > Posts & Topics > Settings.
2. Scroll down to the Authenticate users and click the appropriate setting.
   
   
3. Click Save.

New field on the Message resource 

We have added the “winner” field to the Community API v2 Message resource, used with the contest conversation style. This Boolean field indicates whether or not the message is the winner of a contest. It is supported in the SELECT clause. It is not supported in the WHERE clause.

 

Example: SELECT id, subject, author, winner from messages WHERE board.id = ‘myContest’.

New FreeMarker context object

We’ve added a new FreeMarker context object: restadmind. This context object has the same calls as the restd context object, but enables you to make the calls with Administrator permissions on behalf of the user.

For full details see restadmind FreeMarker context object.

You Found It. We Fixed It.

• Sending private messages with the group private messaging option no longer results in an error and now delivers the messages properly.
• We have fixed the issue where imported images were appearing distorted (stretched) due to some specific element styles.
• When uploading an attachment that slightly exceeded the size limit set in the community config, the community used to throw an exception error. This issue is now fixed, and when an attachment exceeds the size limit, the correct “attachment is too large” message is displayed.
• Clicking the Compare button when editing a TKB article that does not include teaser text no longer throws an error message.
• We have fixed the issue where having Visual Studio installed on your machine was preventing .cs files from being uploaded. Now, .cs files upload correctly.
• We have fixed the issue where the time zone value for Russia was out of date in Community Admin and the User Profile. Selecting Russia from the time zone menu now displays the correct information: GMT +03:00 Russia.