Jiglu 11.1 release notes

For end users

Contribution viewing

• You can now view a list of knowledge entries that are referenced in inline links in other entries but have not yet been written. This is available by going to the knowledge entry index page and choosing the ‘View knowledge entries that have not yet been written’ option from the sidebar.
• The list of attachments shown underneath a contribution no longer includes images, videos or audio used inline in the main text of the contribution.
• Some issues with incorrectly processing and displaying attachments to messages that have been forwarded as an attachment have been resolved.
• Blog posts on a blog home page now include the date that the post was published.
• The count of the number of comments for a blog post no longer includes withdrawn comments.

Contribution entry

• HTML 5 <audio> and <video> elements are now supported in the text of blog posts, discussion messages and knowledge entries.
• If you include a link in a contribution that matches an embedded site (such as a YouTube video) then the external content will now automatically be embedded in the page.
• Changes have been made to handling the entry of manual tags for blog posts and knowledge entries which should make their processing and communication with the server more resilient, particularly on Internet Explorer.

Other changes

• Group newsletters and user summary newsletters in plain text format are no longer available. These were little used and difficult to maintain. All users who opt for newsletters will now receive them in HTML format.
• There is now a limit on the number of sessions that you can have open at the same time, for example by logging on from different devices. If you try and log-on more than five times without logging off from an existing session then you will be prevented from logging on until you have logged off one of the existing sessions or it has timed-out due to inactivity.
• Changes to the way users join and leave groups that were made in the last release introduced a number of issues, most notably making it no longer possible to request to join a private group. These have now all been resolved.
• When using the US English locale some messages still appeared in UK English. This has been resolved.
• A number of other minor issues have been fixed.

For group administrators

• You can now reset notifications to their defaults for the chosen locale on the group appearance settings page.

For system administrators

System settings

• You can now configure LDAP user authentication through a new ‘LDAP directory’ system settings category. Previously configuring LDAP required changes to the external bootstrap.properties configuration file.
• Settings controlling the processing of email bounces (non-delivery notifications) are now in their own ‘Bounce processing’ category in system settings. Some settings that were previously in the bootstrap.properties external configuration file can also now be changed on this page. Other email processing settings are now in the ‘Other processing’ category under ‘Email’.
• You can control whether or not automatic conversion of URLs to embedded sites is allowed using the ‘Automatic content embedding’ setting on the ‘Content filtering’ system settings page.
• The ‘Group limits’ system settings page has a new setting for after how long to expire links and domains that no longer have any references. This was previously in the bootstrap.properties external configuration file.
• You can now edit the name and description of a group template. Simply select the template on the group templates page in system settings and you will be taken to an edit page where you can make the changes.
• You can no longer set whether a media type can be used inline or not. The system now determines this internally based on common browser support.
• You can now reset notifications to their locale defaults on the appearance system settings page.

System architecture

• Due to a change in a third-party library, Jiglu no longer has native support for replicating its caches when used in a distributed server configuration. The new configuration process for cache clustering will be documented on the Jiglu installation support space shortly.
• System performance in creating, updating and submitting contributions has been substantially improved. User intervention due to concurrency issues when carrying out these operations is also now less likely. There have additionally been improvements across the product to make transaction and concurrency handling simpler and more stable.

Security

• As described earlier, there is now a limit on how many concurrent sessions a user may have at the same time. This eliminates a denial-of-service attack vector, where by crafting a URL to repeatedly log on it was possible to log off all the other users of the system.
• A third-party user interface framework library used in the product has fixed a remote code execution vulnerability, although it is not believed that this was exploitable in the configuration that Jiglu uses.