Coding error message: H5P saga continues

Coding error message: H5P saga continues

by Four Buckets Design -
Number of replies: 4

Hello Community,

Using Moodle 3.11, Boost theme, own server.

The H5P saga continues (at least for us).

This post follows our previous 'missing H5P interactive plugin...' post below which may be helpful to read prior to reading the following. That post was about the black icon H5P plugin; since that post, we are now using the core (blue) H5P plugin. (We used the black H5P plugin because the blue plugin wouldn't allow us to add the question set activity to our sites; the 'spinning wheel' occurred and could not be resolved).

This post relates to another, new and different problem with the core H5P plugin, occurring in another of our course sites, after we upgraded to 3.11.

Two question set activities are in the Content bank of course site #2; when clicking the '+ activity or resource' to add the H5P to a topic area, this new message now appears:


After clicking the 'More information...'link, takes the user to https://docs.moodle.org/311/en/error/debug/codingerror which is only a description, not a solution; it reads:

error/debug/codingerror

Coding errors (or coding_exceptions) are problems that are probably caused by incorrect code. For example a plugin that does not communicate correctly with Moodle core.

These errors are normally not caused by incorrect user input or temporary problems like the connection to the database server being down.

As with all error messages, it's a good idea to search moodle.org and the tracker to see if anyone else has reported the problem.

One user posted that sometimes, if you purge all caches the error message might disappear!

-------

Emphasis on 'might' above.

So...why does the new message and error appear in this 2nd site, when it didn't appear in course site #1 where our original problems with the (black) H5P plugin occurred which is now also using the (blue) core H5P ok? Incidentally, the Content bank in course site #1 was empty...had to re-create them, which is different again from what happened to the Content bank in course site #2.

The purge all caches link above reads:

Purge all caches

Administration > Site administration > Development > Purge all caches

Moodle can cache themes, language strings, filters and other bits of information that have been calculated and stored by the web browser. This link forces all user web browsers to refresh their screens of any information that Moodle has cached. Several modules that use cache have settings which will turn off caching for that module. Eliminating or purging caches slows performance.

---------

Have not purged all caches, given the end comment, '...slows performance'.

So...due to the all of the above, we can't add the H5P to course site #2, even though the activities appear in the Content bank and were in the topic area ok prior to installing 3.11, then they disappeared from the topic area after 3.11 install.

In our previous post, we suggested that the elimination of our H5P activities from both sites occurred because the black H5P plugin has not been updated by the developers to work with 3.11; its most recent version is 3.10; see https://moodle.org/plugins/mod_hvp/versions Plan to post this question on their plugin site. If correct, this suggests a serious disconnect between the currency of third-party plugin developers and Moodle releases...they need to be on the same 'virtual' page at the same time.

The H5P plugin (core or third party) has been a horrible experience for us; we're lucky students haven't been enrolled in our sites yet or were mid-point in doing the H5P related-activities. However, we're expecting users to be enrolled next week and really need to have confidence in whichever H5P plugin we use (or other plugins go-forward).

Further, this doesn't reflect well on Moodle as an LMS and only perpetuates the bad wrap reputation of online learning that is so prevalent now.

Suggested fix for this coding error message?

Thanks,

Average of ratings: -
In reply to Four Buckets Design

Re: Coding error message: H5P saga continues

by Gemma Lesterhuis -
Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers
Hi,

I can imagine the frustration you are feeling.

Could you turn the debugging (Site administration > Development > Debugging ) on the site that has this error, that could give more insight on what is going wrong.


Gemma
In reply to Gemma Lesterhuis

Re: Coding error message: H5P saga continues

by Four Buckets Design -
Hi Gemma,

Thankyou for your reply.

Yes, experience with Moodle has been very frustrating and further complicated:

I couldn't log into the forum to reply to you, which has never happened before, )tried different browsers, same issue, then bizarre, back to original browser, could login), so replied to you via email; part of that email read:

Below is a screenprint of another error message I received when trying to log in to the Community forum; further, when searching for more info about this error, screenprint #2 is what is returned; very unhelpful.

Do you know what this error message means and how to fix? See screenprints below. Or suggest another forum I should post this?

How does one post to a forum seeking assistance when you can't log into the forum? 

---------------

2nd, about the debugging, did as you suggested, here's how it appears:




Thanks,


Attachment Screen Shot 2021-05-20 at 11.40.52 AM.png
Attachment Screen Shot 2021-05-20 at 11.42.32 AM.png
In reply to Four Buckets Design

Re: Coding error message: H5P saga continues

by Leon Stringer -
Picture of Core developers Picture of Particularly helpful Moodlers

This reply might be too late to be useful, but to enable debugging you need to ensure both Debug messages is DEVELOPER and Display debug messages is Yes. With that setting you should get more information with the Could not upgrade OAuth 2 token error.

In reply to Four Buckets Design

Re: Coding error message: H5P saga continues

by Sara Arjona Téllez -
Picture of Core developers Picture of Moodle HQ Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers Picture of Testers
Hi!
I think purging caches might help you to fix this error. Although it mentions the "slows performance", it only will affect the next time you'll access your site (because cache needs to be rebuilt).
Kind regards!
Average of ratings: Useful (1)