API version 1.28

We are currently experiencing a problem where we receive an error message when we try to upload downloaded H5P files (content from H5p.com) to the Moodle content repository. According to our research, the error message indicates that only content types with Core API version 1.28 can be used. It literally states that plugin 1.28 is required, but version 1.27 is installed on the Moodle website. However, plugin 1.28 does not yet exist, which is why we cannot update the Moodle plugin to this version, and our research has shown that API version 1.28 is actually meant. Does anyone here have any tips on how to solve this problem? 

otacke's picture

That analysis is correct. An update of the H5P plugin for Moodle (1.27.3 (2026012200)) was released today which ships with version H5P's core in version 1.28.

If you are using Moodle's own H5P integration (the one with the content bank and the blue H5P symbol), then you'll have to wait until MoodleHQ releases an update.

papi Jo's picture

Yesterday you wrote "An update of the H5P plugin for Moodle (1.27.3 (2026012200)) was released today which ships with version H5P's core in version 1.28.".

I have just downloaded that H5P plugin for Moodle latest version (1.27.3 (2026012200)) and I confirm the OP's problem. Whenever I try to install an H5P content I get error:

Validating h5p package failed.

The system was unable to install the Audio component from the package, it requires a newer version of the H5P plugin. This site is currently running version 1.27, whereas the required version is 1.28 or higher. You should consider upgrading and then try again.

It would be surprising that that plugin named 1.27.3 would contain the 1.28 library!

I suppose you meant https://github.com/h5p/moodle-mod_hvp/tree/feature/redesign. But that branch needs to be merged/committed/... to a stable or release branch before it can be available on the Moodle plugins directory...

 

 

otacke's picture

My bad. You're correct, of course. Then the update for the Moodle plugin is in fact still to be released.

This is not contained to just Moodle. I maintain a Drupal site that mostly utilizes files created on h5p.com, and I'm getting the same issue. I tried to just composer update h5p/h5p-core, but version 1.28 doesn't yet exist on packagist. It seems like this same thing happened with the release of 1.27: https://h5p.org/node/1506033. Should we expect to need to wait like 10 days until we can use files created yesterday?

otacke's picture

Yes, this will prevent sharing of many files created on H5P.com with any other H5P integration, because none supports version 1.28 of H5P's core yet.

I am happy to submit a patch to the drupal module, but it seems like h5p core version 1.28 isn't available anywhere yet (or at least not on packagist). Is this expected? Are the module maintainers privy to a private repo or something that I'm not aware of? Is this a question for h5p.com support? Thank you!

otacke's picture

That's a question that only H5P Group can answer. If I had to speculate, I'd assume that updating packagist is not on their radar.

otacke's picture

And an addendum: Even if packagist already served version 1.28 of H5P's core, installing it would not be enough. Using it requires changes to the H5P integration (e. g. the Drupal plugin, too).

BV52's picture

Hi All,

I am checking with the devs regarding the recent issues with the plugins. However, they are already on their weekends so I won't be able to provide any information until next week.

-BV

BV52's picture

Hi All,

A new version (1.17.2) of the WP plugin has been release today, hopefully this resolves the ongoing issues. Please inform us if the issue persists.

-BV

otacke's picture

It should work if you have not touched anything after updating the plugin, but then you would probably not have ended up here to begin with. You may still need to rename library folders, remove H5P cache files and ensure that files are not cached elsewhere.

Unfortunately, the 1.17.2 update does not perform these things, even though it could have in an update hook.

As already mentioned by other users, I also want to highlight that this problem occurs fairly regularly. Please ensure that new core versions are released on Packagist in a timely manner, so that those of us maintaining H5P integrations do not run into this issue every time a new API version is required.

otacke's picture

I don't think H5P Group will mind if you use the github repositories to forge your own and provide these via packagist to others.

It looks like 1.28.0 has started to percolate out, so I'll be updating everything on my side to see if that solves the problem (I'm assuming it will).

In the future, I'm happy to help with this effort as I noted above, but it has been challenging to disentangle what lives where. For example, the Drupal module requires h5p/h5p-core, which it finds at packagist. However there is nothing at github.com/h5p called "h5p-core". It seems to be the same thing as github.com/h5p/h5p-php-library. The 1.28.0 Release on github for that package was not tagged until today, so even if I'd been able to figure out where to look for it on github, I wouldn't have been able to forge my own.

otacke's picture

The core of H5P consists of different components that can be used as needed. People may not need everything. For instance, the h5p-standalone project is not concerned with editing. Other H5P integrations such as Moodle's own H5P integration or the plugin for Stud.IP do not use the Hub client but have their own way of choosing content types to create. So, there are:

  1. The view core: https://github.com/h5p/h5p-php-library
  2. The editor core: https://github.com/h5p/h5p-editor-php-library
  3. H5P Hub client (needs to be baked into the editor core): https://github.com/h5p/h5p-hub-client

Those translate to

  1. The view core on packgist: https://packagist.org/packages/h5p/h5p-core
  2. The editor core on packagist: https://packagist.org/packages/h5p/h5p-editor (including the Hub client)

packagist.org lists the source repository by the way, see screenshot. And version 1.28 of the view core seems to have been published on packagist last week.