Please see the current issues documents below. If you encounter an issue in LEO, please contact LEO Support, who will attempt to fix your problem or escalate to the appropriate area of ACU to assist you.

Overview

When connecting to connected systems from LEO, users may be unexpectedly logged out of LEO and returned to the SSO login page:

Single sign-on login page

When adding Kaltura, H5P or Equella content in LEO, the interface for these systems should load in an overlay window, allowing users to create and select content from these systems to interact with and add to LEO units. Security settings in web browsers may prevent systems connected to LEO and may need to be customised to allow access. Users may not be able to load content from these system or add them into their units, and may be logged out of LEO upon attempting to.

Alternatives and Workarounds

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

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.

LEO systems that may be affected include:

  • Kaltura
  • Equella
  • Echo360
  • H5P

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.

Overview

Kaltura Capture can sometimes fail to correctly upload a video made using the software to My Media in LEO, resulting in the video being lost and irretrievable.

Expected function

After recording a video using the Kaltura Capture software, users are able to save and upload their video to My Media. In some cases, due to issues with the media server or with the client's internet connection, the upload does not complete, or does not complete processing after upload has finished.

Resolution

There is currently no function available in the Kaltura Capture software to re-upload a video that fails to upload and process correctly. Kaltura developers are working on adding the function back into the software, however it is not available as yet.

The re-upload function has been added to Kaltura Capture, meaning users may now re-upload videos from Kaltura Capture if they fail to load correctly.

To access this new function, please download and install the latest version of Kaltura Capture. Navigate to My Media > Add New > Kaltura Capture, then use the Download for Windows or Download for Mac links to download and install the latest version. Close Kaltura Capture and reload it after install.

In this list of recorded media in Kaltura Capture, the Re-upload button should now be visible for any existing videos:

kalturareupload

Impact

Users may experience a loss of data and time spent creating media if they are impacted by this issue.

Alternatives and Workarounds

  • Download the latest version of Kaltura Capture to access the re-upload function as described above.
  • Echo360 Universal Capture is another free application that can be used to make screen and webcam recordings.
  • Uploading videos files to Kaltura that have been created in another program using the Add New > Media Upload option is still possible.

Status of fix for this issue

Resolved with software update.

Overview

Some LEO users may not be able to access Adobe Connect meeting rooms or recordings using the Join button or when clicking on meeting room recordings.

Expected function

Users who access Adobe Connect through the External Tool in LEO should be able to access all meetings and recordings.

Current issue

Users who click the Join button or a recording link receive an error message similar to the example below:

Error message text

Impact

The user is unable to access any content through the External Activity tool.

Alternatives and Workarounds

Users are still able to access meeting rooms and recordings using the direct web address. Lecturers may retrieve direct links to meeting rooms and recordings by following the information in the retrieving the direct URL to a meeting room section of the Adobe Connect LEO Guides. Direct links to recordings can be retrieved by accessing recordings in the external tool activity and using the Share option under the Actions menu. Lecturers can provide these links to student via email or as a link in the unit.

Status of fix for this issue

Currently unknown.

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).

Overview

Some LEO users may not be able to access Adobe Connect content and activities.

Expected function

Users who access Adobe Connect through the External Tool in LEO should be able to access all meetings and recordings.

Current issue

Users who have a period (".") as their First Name in their LEO account may not be able to access Adobe Connect content and activities, receiving a "user not authorised" error when attempting to join meetings or watch recordings.

Impact

The user is unable to access any content through the External Activity and URL links must be provided to students by the tutor.

Alternatives and Workarounds

Please see our Adobe Connect Issue Workaround.

Status of fix for this issue

Currently unknown.

Overview

Customising the participants for a specific meeting room is being overwritten on a nightly basis.

Expected function

Upon creating a meeting room in Adobe Connect using the External Tool activity, all users in a unit are added as Participants (Students) or Hosts (Lecturers and Editing Lecturers) to the new room by default. Editing Lecturers may then add and remove users who have access to this meeting room using the "Participants" function, meaning only those users assigned to the room with the Participant, Presenter or Host role can access the meeting room or view recordings of that room.

Current issue

The overnight synchronisation of users to LEO units removes any customisations made by Editing Lecturers to the list of users who can access the room, restoring all users in the unit to their default role in all meeting rooms, regardless of previous customisations.

Impact

This issue means that all users in a unit can access all meeting rooms created using the External Tool activity. It is therefore technically impossible to restrict the students or lecturers in Group A, for example, from entering the meeting room or watching a recording of Group B, and vice versa. In cases where it is necessary to restrict groups from accessing the information of other groups, this may be a problem.

Alternatives and Workarounds

If the privacy of group meeting rooms is a priority, a meeting room can be created and customised directly in the Adobe Connect Web Manager, with the link to the room provided directly to students. See the Adobe Web Manager LEO Guide.

Status of fix for this issue

Currently unknown.

Page last updated on 30/09/2020

Learning & teaching

Please contact the Learning and Teaching Centre for professional development, resources and advice for your learning and teaching needs at ACU.

LEO support

Available 8am-10pm Sydney time, Mon to Fri,
9am-5pm Weekends and public holidays
Closed Good Friday and Christmas


LEO Guides
LEO Guides feedback