-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Playback issue on Moodle Mobile App #73
Comments
Hello, we are launching an app directly with the Moodle Mobile team, and we also have that same error. We have all the videos on Vimeo, and we have already installed the latest available version 1.8.1 (VideoTime free and PRO) in our Moodle 4.1.10. |
Hi @stefanscholz , I encountered this issue here as well today. Running version 2024050601 of mod_videotime (the version which is listed as compatible with Moodle 4.1 on https://moodle.org/plugins/mod_videotime/versions), I had to see that playing Vimeo videos in videotime in the Moodle Mobile App is completely broken, I got the same error message as the issue author. Digging into the details, I saw that you obviously ported a library change by mistake from the release which targets Moodle 4.2 and upwards to the release which targets Moodle up to 4.1 This class Here's my hotfix which allowed Vimeo videos to be played again in videotime in the Mobile App:
I would be grateful if you could fix the official release for Moodle up to 4.1 likewise. Cheers, |
We have already fixed this in https://github.com/bdecentgmbh/moodle-mod_videotime/commits/VID-820/, which is supposed to be released this week. Sorry for that! (we accidentally applied the fix which was intended only for M42+ also to M41 and below) |
When my client tries to play back a video on the Moodle Mobile app (latest version), they encounter the following error:
[Class "core_external\util" not found].
The URL in the settings in Video Time will not save. All videos are hosted on YouTube.
Client is using the free version of Video Time 1.8 (2024050600) on Moodle 4.0.12 (Build: 20231211)
The text was updated successfully, but these errors were encountered: