Warning : require_once(/var/www/html/wp-content/plugins/h5p/h5p-php-library/h5p.classes.php): failed to open stream: No such file or directory in /var/www/html/wp-content/plugins/h5p/autoloader.php on line 49
Fatal error : require_once(): Failed opening required ‘/var/www/html/wp-content/plugins/h5p/h5p-php-library/h5p.classes.php’ (include_path=’.:/usr/share/php’) in /var/www/html/wp-content/plugins/h5p/autoloader.php on line 49
The site is experiencing technical difficulties. Please check your site admin email inbox for instructions.
I was able to fix this issue. This is a bug with the version of H5P that is uploaded to wordpress and is installed when you click upgrade.
From what I can understand, H5P has a folder inside it called /h5p-php-library
This folder is its own github folder/project that is only linked to from the primary H5P Wordpress Github. When they created the most recent Wordpress version that you can upgrade to, they forgot to include the h5p-php-library folder. The developers probably didn’t even notice because they probably upgrade from the command line using git, not the easy way from the web interface novices like me use.
I wondered if the problems we all had was due to the github updater plugin. When I downloaded the folder directly from Wordpress.org it had all the required folders.
Does anyone who has more experience with the github updater plugin know if this makes sense as a problem. Is there a way to deactivate the github updater plugin just for H5P to force it to use the Wordpress.org version?
The package it is downloading from GitHub don’t contain the submodule folders. Since H5P isn’t actually packaging anything, those files are simply automatically generated by GitHub when a tag is made, this is entirely normal.