Overview

In some rolled over units, Echo360 videos embedded using the Atto editor button show a unit page embedded in the frame where the video should appear. 

This seems to only affect students viewing videos, not lecturers.

Expected function

Echo360 videos embedded in units should continue to function in units made from a copy of the previous unit.

Current issue

A variable in the video embed code is attempting to reference back to the original unit where the video was first added. As students are not enrolled in previous units, they cannot view the video.

Impact

Students are unable to view Echo360 media. Staff are required to use the workaround detailed below or replace the video. 

Alternatives and Workarounds

An update to the Echo360 plugin for LEO should resolve this issue. If not:

And then the solution.

Status of fix for this issue

Resolution in progress. Please use the solution outlined above until a fix is implemented.

This issue has been resolved with the LEO 3.9 upgrade.

Please contact LEO Support if you are still experiencing this issue.

Overview

Security settings in some modern web browsers may prevent systems connected to LEO. This may affect users in several ways, such as:

• Users may not be able to load content from Echo360, H5P, Equella or Kaltura, or add them into their units, and may be logged out of LEO upon attempting to.
• When connecting to systems from LEO, users may be denied access or be unexpectedly logged out of LEO and returned to the SSO login page.
• When adding H5P or Equella content in LEO, the interface for these systems may not load in an overlay window, preventing users from the ability to create and select content from these systems to interact with and add to LEO units.

These browsers may need to have their security settings be customised to allow access.

Alternatives and Workarounds

The best solution for this issue is to try using a different browser, such as Firefox or Brave.

When using Safari, you may need to configure your security settings. Please see Echo360 Guides: Safari Recommended Browser Configuration for more information.

If you are redirected to the LEO Single Sign On (SSO) page in the middle of creating, viewing, or accessing resources or learning activities in your LEO unit, you may need to enable "cookies" in your Safari or Chrome web browser.

Enable cookies for LEO in Safari

Web browser cookies in Safari are either enabled or completely blocked for all sites. For instructions to enable cookies in Safari, visit the Safari User Guide from Apple Support.

Enable cookies for LEO in Chrome

Chrome allows you to select which web sites can have cookies enabled. If you want to block cookies by default on your web browser, you’ll need to create "exceptions" for LEO sites. Chrome allows exceptions for entire domains with the prefix: [*.] We recommend that you allow exceptions for the following domains in LEO:

• [*.]acu.edu.au
• [*.]kaltura.com
• [*.]echo360.org.au
• [*.]echo360.com
• [*.]h5p.com

For instructions to enable cookies in Chrome, visit this Google Chrome Help page and navigate to the section Change your cookie settings > Allow or block cookies for a specific site.

Status of fix for this issue

Currently unresolved. Please see relevant links above to access support pages.

Overview

ACU Library has reported that some LEO units have an extra "-1" or "-2" in their unit's LEO Unit ID. This creates problems when Editing Lecturers are trying to connect to Leganto or trying to associate a Reading List with a LEO unit.

Expected function

When a unit is created and linked to a Banner student cohort, the unit ID should be the term code followed by the CRN, such as "201960-2978" (where "2019' is the year, "60" is the term reference, and "2978" is the unit CRN). LEO unit IDs are not meant to have suffixes with "-1", "-2", etc.

Current issue

Disabling the "Create" button has prevented a lot of these cases from reappearing. However, Editing Lecturers self-reported to ACU Library staff that they refreshed the page if the Unit Creation process took some time to complete (i.e., more than 5-10 seconds). This action created a second (or third) version of the LEO unit to the one invoked by clicking the "Create" button.

Impact

If the LEO Unit ID is incorrect because of the added suffix, Editing Lecturers will not be able to connect to their Reading Lists in Leganto. There may be other issues with connected systems that reference that ID such as Equella. 

Alternatives and Workarounds

The LTC and ACU Library advise staff to go to LEO Support when it is determined that their LEO units have suffixes in their LEO Unit IDs. The LEO Support Team will be able to delete the original (unused) LEO unit and assign the correct Unit ID to the one that the Editing Lecturer is actively working in.

Status of fix for this issue

"Create" button fix already implemented. LEO Support can address concerns for the small number of incidences where this issue occurs (approx. 10-15 per semester, as reported by ACU Library).