For all users
- On browsers with support for notifications (Microsoft Edge, Firefox, Chrome) you can now receive on-screen notifications of new tasks that you need to carry out in the system, new responses to discussion messages you have sent and new updates to knowledge entries that you have authored.
- Browser notifications will only be sent when you have the Radar page open. The first time that you visit the page you will be asked by your browser whether to give permission to receive notifications. If you choose to do so then you can later control what you receive through the Notifications preferences page. If you choose not to do so then you can later give your permission through your browser preferences.
- The ‘Delivery’ preferences page has now been split into three separate pages:
- ‘Discussion e-mail’ controls what discussion messages you receive from the collaboration spaces that you are a member of.
- ‘Newsletters’ controls what newsletters you receive from each blog, monitor or space that you are a member of, whether you receive the daily summary newsletter and in what format you want newsletters.
- ‘Notifications’ controls whether you receive browser or e-mail notifications of tasks and contribution updates. You can also set which groups you wish to receive task notifications from.
- A small number of other minor issues have been fixed.
For group administrators
- Member profile headings can now be set to be editable only by an administrator. These headings will not appear on the preferences profile page, only on the profile edit page available to administrators from the member index.
- Member profile headings can now be set to be shown on the member index when a profile search is carried out. Only single text line and multiple choice headings can be used in this way.
- The size of the icon that can be uploaded for a blog or space on the banner images system settings page has changed to 128 x 128 pixels. This will now be used for browser bookmarks, feeds and browser notifications for the blog or space. Note that older browsers will continue to use the default Jiglu icon for bookmarks.
- The Jiglu tagging widget, which enables content on external sites to be indexed and users of that site to explore using tags that the system has generated, has been refreshed for the current product architecture, features and styling.
- You can now change the base URL of a spidered site after it has been downloaded. Pages that no longer match will be removed when the source is re-spidered, either initiated manually or as part of a regular spidering schedule.
For system administrators
- User profile headings can now be set to be editable only by an administrator. These headings will not appear on the preferences profile page, only on the profile edit page available to administrators from the user index.
- User profile headings can now be set to be shown on the user index when a profile search is carried out. Only single text line and multiple choice headings can be used in this way.
- In the user workflow system settings page you can now set a list of domain names which will bypass the need for a new user to be approved by an administrator when approval is turned on.
- If an invitation to join a group is sent to someone by a user that has permission to activate users then when that user registers their user will not need to be approved when approval is turned on. (Note that this was added in a later build of 10.0.)
- There are two new theme colours available in red and green, with striped variations of both.
- You can now enable or disable themes on the new system settings Themes page.
- On the banner images system settings page you can now upload an icon for the system. This will be used for browser bookmarks, feeds and browser notifications when there is not a specific icon uploaded for a blog or space. Note that older browsers will continue to use the default Jiglu icon for bookmarks.
- You can now set whether a role is to be available only at system level, group level or both.
- A change has been made to Content Security Policy sent by the server as this was preventing the HTML editor from working properly in Microsoft Edge 38 and earlier. Inline scripts have now had to be re-enabled in order to support this browser.