Moodle 3.1.1+ | H5P | can't update library - getting red squares
I'm new to moodle and H5P in general.
I've just finished to set-up a Ubuntu 16.04.1 Server + LAMP + moodle
I've added the H5P Plugin manually because the /var/www/html/moodle folder is writeable only by the root user - all other users (www-data included - can only read from that location - that is the recommended way to install moodle by the following resource
When i'm trying to upload H5P Library - it fails without an error message - I've added a gif the illustrates the actions that i've made.
Update #1: even after updating write permissions for the path - /var/www/html/moodle/ - still the same result.
Is there another way to install the H5P Library by using the Terminal only?
Mon, 08/08/2016 - 09:55
I was not able to reproduce with the provided .h5p file.
Can you open your console and check for any irregularities and paste your server log here ?
It seems like something might be wrong with the installation and validation. Make sure all the correct permissions are set, also for your moodle data and temporary data folder. Check that you are allowed to upload the size of the .h5p file. I would suggest trying again with a fresh H5P plugin following https://h5p.org/moodle.
Could you provide some more information on your system if this issue continues to persist ? php, mysql version, etc. ?
Tue, 08/09/2016 - 07:22
Server Operating System name (version also if possible): Ubuntu Server 16.04.1
PHP version: PHP 7.0
Database server type and version: MySQL 5.7.13-0ubuntu0.16.04.2
Browser and version: IE11, Edge
Moodle version: 3.1.1+ (MOODLE_31_STABLE)
Moodle install type? New
Moodle config.php attached (please remove passwords): YES
Phpinfo attached?: YES
Tue, 08/09/2016 - 10:59
I will have a look and verify our compatability with PHP 7.0.
In the meantime, could you paste your server log ? It should give some insight into what is wrong.
Sat, 08/13/2016 - 13:31
Do you mean the error_log file?
Like i've said i'm new in all of this subject - I've attached the steps that i've made to locate where my error_log is and it's empty...
What configuration are you using for working with H5P?
Mon, 08/15/2016 - 09:34
Ok, we'll get back to this
Ok, we'll get back to this thread after doing some extra PHP 7 testing. We use all kinds of setups, but many of them have old versions of PHP since we often develop for the quite old Drupal 7.
Sat, 09/24/2016 - 21:08
Is there any follow-up?
Is there any follow-up?
Mon, 09/26/2016 - 10:16
I don't think this has been tested yet, there has been created an issue for the next H5P release for this. How has your progress been with this? Have you found any valuable info that could speed this along ?
Wed, 01/25/2017 - 20:42
Moodle Environment Page
I had the same issue. I checked /admin/environment.php and I was missing the SOAP extension. I added it a few minutes ago, and it appears the problem is solved. I am using php7.
Thu, 01/26/2017 - 10:37
Thanks, hopefully others can
Thanks, hopefully others can find this usefull as well!
Sat, 08/13/2016 - 13:50
I've also found the access.log file - I've attached it as a zip
Sat, 08/13/2016 - 01:27
I have just installed H5P in my Moodle, but when trying to create activities it shows me this: Error, unable to load libraries.
Thanks so much
Mon, 08/15/2016 - 09:40
Hi,I'm sorry to hear that. Do
I'm sorry to hear that. Do you get any extra error message in the console? You may open the console with CTRL + SHIFT + J.
Sun, 12/04/2016 - 21:05
H5P in Moodle
This is the additional error:
http://aurelianosanchez.com/saber11/mod/hvp/ajax.php?contextId=3263&toke... Failed to load resource: the server responded with a status of 500 (Internal Server Error)
iolib.js:1 Connected to wss://722454757230.vidya.io
iolib.js:1 New user join room [object Object]
widget_lessons_v:1 Error in event handler for (unknown): TypeError: Cannot read property 'blocked' of undefined
Thanks so much
Tue, 12/06/2016 - 09:46
Hi,You are getting an
You are getting an Internal Server Error (HTTP code 500) from the web server, which probably mean you have a trace of the problem in your web server's error log. Please look there :)