The release notes provide information on the features and improvements in the specified version. The release dates that are related to the version of the release are published in the Study guide release schedule.
Improvements
The issues in release mentioned under the section improvements are considered as new functionality, user experience improvements or bug fixes. Issues marked as hotfix are developed in this sprint but applied to the previous release or directly to production, depending on impact.
Upgrade UI foundation component fixes - SG-619, ..., SG-649 (Hotfix in 2.65)
In the previous release and update of the underlying UI foundation layer (framework) was performed. This is a merely technical task that is performed to stay up to date with all front-end security issues and enable access to new options. The change was tested, but on test it was found that a number of 'small' and/or 'annoying' front-end issues popped-up. During this sprint all the found and reported issues have been hotfixed. This means that the list of fixes mention below is not in the 2.66 release, but in the 2.65 (production) release.
- iFrame embedding of the studyguide was not working due to the standard restrictions in the new framework. This has been adjusted, and iFrame embedding is available again.
- Navigation to a module in the study structure was re-opening the study, instead of the module
- Mobile filter and sorting was not working correctly
- Admin filtering on references was not working
- Selecting 'Hide' on widget deletes the defined fields
- Different layout issues are addressed
- Tabs with spaces in the name should be clickable
- Not all labels are using the correct translation
Import studies from Curriculum should use the defined study filter - SG-631
It was found the study import was not using the study filter, but the module filter. This has been fixed and when importing the correct filter for the imported object is used. Next to that the filter can be emptied again.
Markdown based description display changed - SG-628, 634
When using Markdown in descriptions, there was quit a lot of white-space between lines, paragraphs and lists, reducing the readability of the information. The white-space is changed and the readability is improved. Next to the white-space change also the different headers were slightly restyled to make them stand-out more against the standard text. Especially the smaller headers (h3, h4) were too close to the standard text display format.
Security
An integral part of our development and build process is automatic scanning for known security vulnerabilities. The vulnerabilities will be fixed based on their impact, which means that in some cases an immediate hot-fix will be applied, and in other cases the vulnerability will be fixed in the current or next Sprint (release). The security section provides an overview of the vulnerabilities mitigated.
For more information on reported vulnerabilities, see the central database of vulnerabilities.
No security vulnerabilities have been reported that require mitigation.
For more guidance on configuration and setup of Study Guide, use the relevant Study Guide manual.