Attempt tracking not working since today (1stJune2022)

Attempt tracking was working for most Content Types till 31st May 2022.

 

From today i.e. 1st June 2022, Attempt tracking is working for Flashcards and Drag the Words.

But it is not working for Column with Find the Hotspots.

It is not working on

(a) Moodle and on

(b) H5P.com

BV52's picture

Hi chaavi,

I would suggest that you reach out to H5P.com support by sending an email to [email protected].

-BV

Thanks BV52. Will be doing that.

But the issue is there on Moodle when I directly upload H5P files too, which has nothing to do with H5P.com

It was working fine till 31st May. did the 1st June release cause some issues. But why should the Moodle plugin be affected by H5P release? I haven't updated any software.

To be specific I am facing issue on Moodle 4.0 with the H5P plugin. Direct H5P file upload. Content Type is Column with Text, Audio and Find the Hotspot.

BV52's picture

Hi chaavi,

Sorry I thought you mentioned that it is also an issue with H5P.com. This looks like an issue with the Moodle core integration of H5P. I suggest that you post this question in Moodle's forum.

-BV

Please ignore the H5P.com issue. I will take it up separately as needed. It might have been for a different reason.

Coming to Moodle, have posted on Moodle forum too: https://moodle.org/mod/forum/discuss.php?d=435187

However there was a Content type scheduled update on my Moodle site on 1st June. So in some ways it is related to H5P.org i think...

BV52's picture

Hi chaavi,

It might be related to it, however I have tested the attempt tracking using the H5P plugin as well as H5P.com integration with Moodle and it is working as expected.

-BV

otacke's picture

Hi all!

It seems the result part of the xAPI statement was accidentally removed from Find the Hotspot recently. Pull request to fix the issue is pending ...

Best,
Oliver

This might be it. Was quite surprised that something that was working on Moodle till 31st May suddenly stopped working on 1st June.

This was a showstopper for us. If the system was live and this had happened might have frozen all our content for our learners. Luckily we haven't gone live.

Hope this gets resolved soon...

Thanks for the response...

otacke's picture

Hi Chaavi!

I am not sure why content would freeze caused by the missing xAPI statement, but if you have some custom dependency to the xAPI statements being sent, then some data points might miss information.

Deploying things automatically is always risky without testing, but given that you're mentioning a live system, I assume that I don't need to tell you that :-) Maybe moodle should have issued a warning when they introduced that service.

Hope the H5P core team will find some time to have a look at the pull request soon.

Cheers,
Oliver

Yes I do realise that the automatic update is proving risky. But it is based on the trust that any new update will add benefits without costs. Benefits as in, bugs fixed, features added etc. Realise now that if some such bug is introduced into the Content Type by the update, then maybe it is better to switch off the Automatic H5P update.

Hope the H5P pull request will go through soon.

 

Thanks much... You have been the biggest source of information and enthusiasm surrounding H5P in the last year... I follow your response/posts closely...

otacke's picture

Hi chaavi!

Sure, that's what updates are supposed to do: bring new features or bugfixes :-) Unfortunately, despite testing, some new bugs can get introduced as well as in this case. That's not only true for H5P, but for any software. Therefore, like you seem to do but others may learn, it's advisable to have some staging platform first where software updates are tested first before rolling them out to a production system.

And thanks for your kind words. Reading and posting on this forum is what lets me know about new issues, learn about things H5P needs and also improve my own overall knowledge of H5P, so it's a win-win :-)

Best,
Oliver

Yes, the staging platform is the way to go. Little bit of work there, but provides a buffer zone of safety in the end. Will have to set it up...