FrogLMS Community

What's new in this release?

BUG FIXES

This release includes the following bug fixes:

Event Widget

• JIRA# NFC-3652 - Based on customer feedback, the Event widget has been enhanced to simplify the management of session enrolments. Administrators can now bulk import users directly into a session and set their attendance status at the same time, removing the need to first enrol users before updating their attendance. This significantly reduces the time and effort required to manage session attendance.
  
  When importing users, the CSV file now requires only the following columns: 
  • Username  
  • Attendance Status

Administrators can also continue to use the existing export/import process for users who have already self-enrolled. Please note, however, that the exported CSV file now uses the new format required by the updated import process.

Modules

• JIRA# NFC-3653 - When configuring the Site widget within a module, the site selection window now includes a search field to help you quickly find the required site. In addition, the site selection panel has been widened to improve the visibility of available sites.

Reporting Application

• JIRA# NFC-3665 - The Module Compliance Report, when exported to CSV, now includes additional fields to ensure the data matches what is displayed within the interface. The three new fields are:
  • Date Started
  • Date Completed
  • Date of Renewal

An example of how the Module Compliance Report data is displayed when exported to CSV is shown below.

• JIRA# NFC-3664 - Improved the Module Compliance Report to ensure that, when no identity is selected, all relevant learners are included in the report. This now includes:
  • Learners currently allocated to the module, regardless of their module status.
  • Learners who are no longer allocated to the module but have an “In Progress” record for the selected module.
  • Learners who are no longer allocated to the module but have a “Completed” record for the selected module.

Sites

• JIRA# NFC-3663 - Resolved an issue where custom site themes were not displayed correctly. This issue only affected sites where the main site theme used a custom theme, but the landing page was configured to use a different custom theme. Custom themes will now display as expected.