Posts made by Visvanath Ratnaweera

Picture of Particularly helpful Moodlers Picture of Translators

Getting:

api-version-unsupported : The system was unable to install the Column component from the package, as it requires a newer version of the H5P plugin. This site is currently running version 1.24, whereas the required version is 1.27 or higher

opening an activity mysite/mod/h5pactivity/view.php?id=N (blue)

The package file is of type .h5p. I don't know from where.

Moodle 4.1.14, PHP 7.4, mod_h5pactivity 2022112801. Plugins overview > Available updates doesn't show anything related to h5pactivity as "New version available"? (Ran the plugin check fresh.)

Am I supposed to manually replace something? We've disabled \core\task\h5p_get_content_types_task earlier since it started breaking things.

Average of ratings: -
Picture of Particularly helpful Moodlers Picture of Translators
It is always the same client computer, right? Did you try from another computer, preferably another OS, different browsers incl. Chrome?

I thought you checked the quality of your TLS cert. Still, how about getting a new certificate?
 
There's no CDN in the middle, right?
Picture of Particularly helpful Moodlers Picture of Translators

Hi Justin

Thanks for the insights.

i) the best people to fix the plugins are the developers of them

Good and bad. Good that the plug-in developers are autonomous. Bad is that the versioning of each plug-in could be different.

ii) if you can stay on PHP 8.1 you might minimize warning and errors from plugins

You have a point. But on the other hand when one goes from LTS to LTS, PHP long jumps can not be avoided.

 iii) 100 is too many, don't you think?

There are "plug-in happy" people. Incidentally they are the most enthusiastic on-line teachers. wink

iv) Its very hard to test

That is where I am now. See the discussion with Ken.

Picture of Particularly helpful Moodlers Picture of Translators

Ken

That *is* definitely a strategy. wink

You wrote:

I do full site clones ... plugins and all.   I march core via git and if that is successful, I login and go immediately to Notifications ... update.   That's when Moodle should tell me there are plugins that need attention.   Click that and there's a list of plugins that site has figured out needs updating/upgrading.

Different from mine. But I am looking at yours.

Now before I do a site upgrade, I run that checkaddons script and note which ones do NOT have a version same as core.  

So you let the Plugins > Plugin overview > Check for available updates to report to you. The assumption is that Moodle doesn't just say, there's a newer version but makes sure that the version matches, say 4.5 LTS.

Yes, I could find source site and inquire with maker or check their git site to see if there is one available that just didn't make into moodle.org plugins.

OK. The Not OK plug-ins sends you on a journey.

Putting that info into a sheet is more work that I don't wanna do!

Looks like the accounting part could be avoided.

I'll give your method a try.

Picture of Particularly helpful Moodlers Picture of Translators
No prob.

The good news is that you can develop the course in "localhost" and transfer it to the "host" later. See Migrating Moodle from a Local XAMPP to live web server. Or, if it is just course content, then Course backup > Course restore.