H5P + Moodle: Update content types

rexj's picture

tldr; What is the best way/workflow to maintain/update the content types in the Moodle plugin?

I assume that updating the plugin is different than updating the content types. When I am in a course looking at the list of content types I see "Update available". I can then click into the details and click the "Update button". That seems to follow the documentation I found here

What is confusing to me is that there are also settings in Site Administration > Plugins > Activity Modules > H5P > H5P Libraries to update content types. Once I update a content type in the Hub, it appears that the update icon becomes available on the admin page. Does the content type have to be updated in both places? It would seem innefficient to have to do so.

Thanks for your help.

0
0
Supporter votes Members of the Supporter Network can vote for feature requests. When the supporter network has generated sufficient funding for the top voted feature request it will normally be implemented and released. More about the H5P Supporter Network
BV52's picture

Hi rexj,

There are 3 places where you need to update H5P.

  1. The core files which can be updated in Site Administration > Plugins > Plugins Overview
  2. The Libraries which can be updated through the Hub
  3. Old content libraries which you mentioned above. You need to do this so that the contents created prior to the update will start using the new libraries.

Afaik the reason behind the the core files and libraries updates are different is that the core files are different for Drupal, Wordpress and Moodle but uses the same libraries. For the 2nd and 3rd items above I really don't know the reason why but I agree that it is inefficient way of updating.

I have moved this post to the feature request forum. My suggestion is either we have a single button to updated all libraries for older contents or it will automatically be updated once the library is updated in the hub, what do you think?

 

-BV52 

 

rexj's picture

Thanks BV52.

I can understand how/why updating the plugin files and content libraries are separate and different. 

I agree that there is room for improvement for the library updating workflow. Currently having to update each content type in the hub and then on the admin side of things is tedious and confusing.

It would be nice if there were an "Update all" function on either or both sides of things. I liked what you said about older versions being automatically updated. That would save some time/confusion.

Thanks

rexj's picture

Your reply brings up another question for me.

Multiple versions of the certain content types appear in the libraries list in Plugins > Activity Modules > H5P > H5P Libraries. I have attached a screenshot of an example. I currently have selected "Restricted" for the older versions of the content types.

Will this create any problems? Should I not do this? Does it matter?

 

Attachments: 
BV52's picture

Hi rexj,

They are restricted automatically so that there wouln't be any conflicts when creating contents. When a content library is restricted non-admin authors will not have access to them. In effect this forces everyone to use the most recent version.

-BV52

It might feel strange that you have to update libraries and content. But if you think about it, it actually makes a lot of sense:

Updating libraries to the newest version eliminates bugs and adds new functionality.

Updating your content, makes it availabe within the new context.

BUT, what if some of the new features cause problems with an older version: In this case, updating your content can lead to problems. Therefore having the choice whether to update your content or not actually is a very user-friendly decision.

Of course, when you only create content once in a while, this is not a problem. But if you create a lot of content, you don't want to have to go back and check whether all existing content is still working and if not, you have to adapt them every time something goes wrong.

BV52's picture

Hi mattgig,

Thank you for the input and you are right having about the option. I guess what can make this better is an easier way of updating the libraries of the "old" contents without having to go to the libraries screen. Probably a button in the Hub could help a great deal.

-BV52

There may be a more recent forum discussion about this workflow, but this is the one I've discovered today. As a Moodle Admin with multiple sites with moderate to heavy usage of H5P, I'm uncertain if we should be updating old content libraries. Is there some where we can reference to know if a library update is likely to cause a problem? There are so many elements within a single content type that I don't think I could create a comprehensive testing of each content type.

In our case with a large university, should we opt to not update prior content?