white screen on moodle 3.1.3 mod installation

I tried h5p mod on local moodle installation (on my local computer) and it worked good.

Later I tried to install h5p on server moodle installation (moodle data localted on another server in network and moodle configured correctly to work with this network folder) but all I get is white screen on installation. Checked server permissions and it seems ok. Web server user account can read and write moodledata folder.

Thankful for any ideas to try and check.

fnoks's picture


You should check your web server's error.log. If you find anything there, please paste it here!

checked my php log - no errors. On my local development computer installation goes well. On remote server I get blank screen after I press "Upgrade moodle" button

icc's picture

If you temporarily enable some debug options the error messages should be printed.
Without any error message, it's very difficult to tell what could be going wrong.
To enable debugging insert the following into the config.php file:

@error_reporting(E_ALL | E_STRICT);   // NOT FOR PRODUCTION SERVERS!
@ini_set('display_errors', '1');         // NOT FOR PRODUCTION SERVERS!
$CFG->debugdisplay = 1;              // NOT FOR PRODUCTION SERVERS!

Right before this line:

require_once(__DIR__ . '/lib/setup.php');

Now, try the upgrade again.

john.rickard's picture

Hi All,

I have been having these issues too!

I enabled the settings your recommended and when trying to install I got the response below.


Upgrading to new version


Warning: require_once(/var/www/main-moodle/moodle/mod/hvp/library/h5p.classes.php): failed to open stream: No such file or directory in /var/www/main-moodle/moodle/mod/hvp/autoloader.php on line 68

Fatal error: require_once(): Failed opening required '/var/www/main-moodle/moodle/mod/hvp/library/h5p.classes.php' (include_path='/var/www/main-moodle/moodle/lib/pear:.:/usr/share/php') in /var/www/main-moodle/moodle/mod/hvp/autoloader.php on line 68


john.rickard's picture


I have been getting this same issue as well - I have done as you suggested above and tried the install again. The following PHP debug is shown on the page when it errors :(


Upgrading to new version


Warning: require_once(/var/www/main-moodle/moodle/mod/hvp/library/h5p.classes.php): failed to open stream: No such file or directory in /var/www/main-moodle/moodle/mod/hvp/autoloader.php on line 68

Fatal error: require_once(): Failed opening required '/var/www/main-moodle/moodle/mod/hvp/library/h5p.classes.php' (include_path='/var/www/main-moodle/moodle/lib/pear:.:/usr/share/php') in /var/www/main-moodle/moodle/mod/hvp/autoloader.php on line 68
icc's picture

I'm sorry to hear that you're having issues. Where did you download the plugin, was it from the Moodle plugin directory or GitHub? If it's the latter I'm guessing you forgot to download the submodules(/library, /editor /reporting) as well. Unless you plan on doing development it's often easiest to stick with the version from moodle.org.

john.rickard's picture


No I used github, as its the standard way for most moodle plugins. We do all of our other plugins via the github repos.  Would you be able to publicise not to use github? - I expect a lot of administrators would look to use it as it makes updating easier for large sites.

I will try the plugin download and see if that works. 



having the same problem here and this is the first time I see an incomplete github moodle plugin distribution (I maybe installed 30 different plugins during the last few years). The plugin description on the moodle site doesn't give any piece of information about this, nor does the "Set up H5P for Moodle" on your site. So the best solution here is to download the plugin via web, version it by hand, and deploy it. If a new version is released, we have to start over again...

icc's picture

I understand the confusion. It is mentioned in the readme file but it's not very clear.

You should be able to use Git if you wish too – but stick to the stable branch or a version tag. You always have to run git submodule update --init --recursive after checking out a new tag or pulling a branch to make sure you get the correct version of the third-party libraries.