Jiglu 13.0 release notes

Highlights

  • Better support for open Internet communities, including the automatic moderation of new group members, an optional delay before new users can participate, temporarily suspending group members and the ability for users to flag inappropriate content for checking by moderators.
  • Improvements to onboarding new users, with a new quick tour of the main radar and navigation features when they first log on and configurable ‘Get started’ information to help direct them to important local content.
  • Navigation improvements, including simpler links back a user’s radar home page and quick switching to the most-recently-visited groups.
  • Easier control of what sections are available in blogs and spaces so group members only see the navigation options that are right for the group.
  • Lots of smaller improvements – many customer-requested – designed to make users’ lives easier.

For end users

Navigation

  • On the links under your name on the top right of each page, the ‘Log off’ link has been removed and within groups a new ‘My radar’ link added instead. To log off please instead choose the option from the dropdown menu that opens when you click on your name.
  • When you select the Switch groups link at the top right of each page the dropdown list of groups now begins with the five groups that you most recently visited.

Introductory tour

  • When a user first joins the system and visits the Radar page, they will be shown a brief tour of what features are available. This can be skipped if required and once complete will not be shown to the user again.

Blogs and spaces

  • You can now flag inappropriate blog comments, discussion messages and knowledge entries for checking by a moderator. A new Flag button will be found underneath contributions of these types. You will be required to enter a reason for flagging the contribution. If it has already been flagged by another user or if a moderator has already decided there is not a problem with it then you will be told.
  • When viewing a discussion message, if it was sent via email but the authenticity of the message could not be verified through its DKIM signature and a moderator has not approved the message then a red warning icon will be placed after the sender’s details.
  • An issue where when adding an instant message containing a link which had already been seen in the space resulted in the link’s details not appearing beneath the message has been fixed.
  • An intermittent issue in the blog post and knowledge entry editors that resulted in the inability to add more manual tags has been fixed.

Other changes

  • In some circumstances raw HTML entities would appear in the matches shown in search results or tags would be created for HTML entities, due to a bug in the content analysis system. This has been resolved. Because the content analysis needs to be redone as part of this fix you may notice some automatic tags appearing as new even when they existed before and there may be some other differences to before in the available tags.
  • An issue causing user newsletters to break when the user receiving the newsletter had posted a blog post and someone else had immediately responded to it has been fixed.
  • Issues that caused a failure to process pages with invalid HTML when getting metadata for links in contributions or pages for a spidered source have been resolved.
  • Extracting content from some document formats for searching and tagging has been improved, most notably for the EPUB format.
  • A number of minor issues have been fixed.

For group administrators

Blogs

  • You can now have blog posts automatically close to new comments after a certain number of days have passed. This can be changed by going to the Comments workflow settings category and changing the Automatically close to new comments after setting to the required number of days. If you later reopen the post to comments it will not be automatically closed again.
  • If you do not want to allow comments in a blog then you can now turn off the comments section from the Access and membership settings category rather than going to the Resource permissions advanced settings category. The Access to sections part of the form lets you select if this section is available or not.
  • You can now have comments from new members automatically sent for moderation for a period of time. In the Comments workflow category change the Moderate new member setting to how many days you wish to have comments moderated. After this time has passed then comments from the member will no longer be moderated.
  • Inappropriate comments may now be flagged for checking by moderators. When this happens, you will be sent a task for the comment with the reason that the person who flagged it gave for why it should be looked at. You can then choose to either withdraw the comment or ignore it, in which case it cannot be flagged again.

Spaces

  • You can now have discussion threads automatically close to new messages after a certain number of days have passed. This can be changed by going to the Thread workflow settings category and changing the Automatically close to new messages after setting to the required number of days. If you later reopen the thread to messages it will not be automatically closed again.
  • If you do not want to allow certain sections in a space then you can now turn them off from the Access and membership settings category rather than going to the Resource permissions advanced category. The Access to sections part of the form lets you select if the Sources, Talk, Discussion and Knowledge sections are available or not.
  • You can now have discussion messages, new discussion threads, polls and knowledge entries from new members automatically sent for moderation for a period of time. In the appropriate workflow settings category for the type change the Moderate new member setting to how many days you wish to have these contributions moderated. After this time has passed then contributions from the member will no longer be moderated.
  • Inappropriate discussion messages and knowledge entries may now be flagged for checking by moderators. When this happens, you will be sent a task for the message or entry with the reason that the person who flagged it gave for why it should be looked at. You can then choose to either withdraw the contribution or ignore it, in which case it cannot be flagged again.

Member suspension

  • You can now temporarily suspend members from contributing to a group when they have been acting inappropriately. On the member’s profile page, you will find a new Suspend Selecting this opens a dialog where you can enter how many days you wish to suspend them for and the reason. They will then be sent an email with the reason and when they are allowed to contribute to the group again. This information will also be shown on an alert when the member visits the group’s home page and to group administrators visiting the member’s profile page.

Suspended members will be able to continue to read but not contribute any content or change their profiles. They will still be able to leave the group or change their group preferences. If they leave and re-join the group then they will remain suspended. The suspension will be revoked at 9am in the groups’ local time zone on the chosen day. It can also be manually removed by an administrator by selecting the Unsuspend button on the member’s profile page. You can search for suspended members using a new filter on the member index page.

Other changes

  • An issue that caused the tag task form to break when there were a larger number of suggestions has been resolved.
  • An issue that could cause feeds to fail due to an excessively long image URL in a feed entry has been resolved.
  • An issue with incorrect permissions checking when downloading a group activity log has been resolved.

For system administrators

  • There is a new system setting which allows you to block a new user from adding or editing any content until after a certain number of hours have passed. When the product is used for Internet communities this can be useful to enforce a cooling-down period for new users and reduce the potential for abusive behaviour. On the User limits settings category change the New user action delay setting to the number of hours before they are allowed to contribute.
  • Users to whom email cannot be successfully delivered can now have their accounts automatically deactivated. On the User workflow settings category there is a new Deactivate user if email deactivated for setting, which determines after how many days since messages started bouncing the user account should be deactivated. If the user logs on before that time and reactivates their email then the user account will not be deactivated.
  • You can now configure what content is used for the Get started section for new users. On the system settings Notices category there is a new Radar introduction setting where you can enter the text to be used.
  • Users who have access to edit groups and users but do not have the system administrator role are now able to view help pages and content relating to this functionality, which was previously not shown.
  • On the External content lookup settings category, the Connection blacklist setting has been renamed to Connection block list.
  • On the Group content filtering settings category, the External content whitelisting setting has been renamed to Block media from unknown external sites.
  • The Licence key system settings page now shows whether the licence key allows system components to be split onto multiple servers.
  • On some system settings pages selecting the Apply button previously did not return you to the same page. This has been resolved.
  • You can now close the Get started section on My radar without needing to have elevated system administrator privileges first.

For operations engineers

Upgrade

Other changes

  • When interoperating with sendmail, email messages were previously always converted to 7-bit format before being ingested by Jiglu, which when receiving from some systems that were not properly compliant with the DKIM standard could cause DKIM verification to fail. They will now always remain in the original format they were received as.
  • When there was a failure to successfully deliver an outgoing email message to the mail server it would be requeued faster than it should have been. This has been resolved.
  • The webapp RPM package now obsoletes any earlier webapp package.
  • Third-party libraries have all been updated to their latest recommended versions.

Security

  • Potential denial-of-service attack vectors in the parsing of documents have been closed, which could have resulted in excess memory consumption or infinite loops. These could be exploited by uploading or emailing attachments in MP3, MP4 and PSD file formats.
  • A small memory leak in a third-party search library could cause the system to eventually exhaust all memory following a very large number of text search requests.
  • Two potential cross-site scripting vulnerabilities have been fixed in third-party JavaScript components, although these should not have been exploitable in Jiglu.
Jiglu 13.0 - Changes in the September 2020 release.pdf
Written by Stephen Hebditch. Published on .
Release notes, Discussion message, settings category, dropdown menu, operations engineers
2.0.0
Product changes in version 13.0.