This is the weekly roundup of features that have been implemented this week:
One of the features that we have added this week is in relation to widgets.
The feature that we have added is profile completion widget. Now when a user with the select permissions adds this widget to content of their choosing. Users will now be able to see and participate in a number of steps in order to 'complete' their profile.
For more information, please see our documentation:
This is the weekly roundup of bug fixes that have been implemented this week:
Another bug fix that we have implemented this week is in relation to content revisions.
The problem that was occurring was that when a user with the select permissions edits either an image or file attachment then two revisions are made. As a result of this it has been causing uneccessary duplicates of revisions which can confuse users. This issue has since been resolved and is no longer occurring.
For more information, please see our documentation:
One of the problems that we have resolved this week is in relation to the admin menu.
The problem that was occurring was that site admins were unable to see the workflow options when creating a menu item. As a result this was causing some confusion for users. This issue has since been resolved and is no longer occurring.
For more information, please see our documentation:
One of the bug fixes that we have resolved this week is in relation to widgets
The problem that was occurring was that when a user with the select permissions navigates to the all content widget and selects the blogs option. Then they should be able to select multiple authors however there was only an option. This issue has since been resolved and is no longer occurring. Now a user can add multiple authors.
For more information, please see our documentation:
This is the weekly roundup of features that have been implemented this week:
Another feature that we have added this week is in relation to teams.
The feature that we have added is that a team administrator is now able to add and admend details of their team so that the policy merge tags will be personalised to include the correct team information. This feature is possible when the franchise settings have been enabled in admin.
For more information, please see our documentation:
One of the features that we have added this week is in relation to widgets.
The feature that we have added is that now if a user is in multiple teams; they can use the team switcher widget to be able to navigate between the policies for each team. By adding this feature it will help save time for the user and provide clarity for what policy belongs to which team.
For more information, please see our documentation:
Another feature that we have implemented this week is in relation Matomo.
We have added the Matomo event tracker. This means that Matomo now runs on all pages of the intranet and tracks the UUID. This feature can be paired with your Matomo api to be able to receive insightful information. By adding this feature we believe that it will help provide our users with important information.
For more information, please see our documentation:
This is the weekly roundup of bug fixes that have been implemented this week:
Another bug fix that we have implemented this week is in relation to image display across all content types.
The problem that was occurring was that images would not display correctly when added via the File library or the Embed functionality in the WYSIWYG editor. The editor would display an error in place of the the images. This issue has since been resolved and is no longer occurring.
For more information, please see our documentation:
Another bug fix that we have implemented this week is the external user role access in relation to Manage content.
The problem that was occurring was that when a user with external user permissions would navigate to the Manage content screen, they would see an 'access denied' error. This should not be the case. Users with external user permissions should be able to access the Manage content screen, but be able to view only content they have followed or bookmarked and comments they have added. This issue has since been resolved and is no longer occurring.
For more information, please see our documentation:
Another bug fix that we have implemented this week is in relation to content.
The problem that was occurring was that mentions and hashtags were behaving in a strange way. When a user would add a mention or hashtag, they would appear as plain text after saving, or they would disappear when editing. This affected all types of content editors and caused a lot of frustration amongst users. The issue has since been resolved and is no longer occurring.
For more information, please see our documentation:
This is the weekly roundup of bug fixes that have been implemented this week:
Another bug fix that we have implemented this week is in relation to widgets.
The problem that was occurring was that when a user with the select permissions would interact with a latest comments widget and select a specific author for the comments then save. The author would not be retained after the user had selected save. As a result this was causing issues for some users. This issue has since been resolved and is no longer occurring.
For more information, please see our documentation:
Another bug fix that we have implemented this week is in relation to manage content.
The problem that was occurring was that when a user with the select permissions would navigate to Manage content an error would occur with the filters. This is because on the left-hand side (LHS) the options should be limited based on the user role that has accessed it. Instead, all user roles were seeing the same number of options. This was causing a lot of confusion. This issue has since been resolved and is no longer occurring.
For more information, please see our documentation:
One of the bug fixes that we have implemented this week is in relation to menus, manuals and manual pages.
The problem that was occurring was that when a user with the select permissions would navigate to one of these areas, try to either like or bookmark a chosen piece of content, an error occurs. As a result the action does not go ahead. This problem has since been resolved and is no longer occurring.
For more information, please see our documentation
