-
Hi, I'm developing h5p app with H5P-Nodejs-library and I need to save answer data after user try any content and I need to view those data in another h5p player. Any tips to achieve this? I saw "storing user state in the player" is not finished yet according to Project Status page. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 7 replies
-
This feature is indeed not implemented yet. It shouldn't be terribly complex, but we haven't found time for it yet. We might get funding for it at the end of the year, bit that's still uncertain. You can always work on the feature yourself if it's urgent. We can provide some tips. |
Beta Was this translation helpful? Give feedback.
-
Hello, could you tell me if you plan to develop this feature, if not, could you provide me with some tips to develop it myself please? Thank you in advance. |
Beta Was this translation helpful? Give feedback.
-
The feature is now part of 9.2.0. See the docs here: https://docs.lumi.education/advanced-usage/user-content-state https://docs.lumi.education/advanced-usage/completion-tracking |
Beta Was this translation helpful? Give feedback.
-
I have enabled the option to save user content state, it works fine. I see that by default the state is saved to the database with the option preload = true, however, how can I set this option to false to load the state with a second AJAX request from the browser? I tried to set the preload value from the options of the H5P.setUserData function defined in the h5p.js file but it doesn't work I am trying to use this option to change the functionality a bit because according to the project requirements it is necessary that the admin can reuse the H5P content in different sections, however, when the user responds the content and the state is saved , the state will be restored in all sections where that content is used. Could you advise me please? Thank you in advance. |
Beta Was this translation helpful? Give feedback.
This feature is indeed not implemented yet. It shouldn't be terribly complex, but we haven't found time for it yet. We might get funding for it at the end of the year, bit that's still uncertain.
You can always work on the feature yourself if it's urgent. We can provide some tips.