Tim Hunt

Thanks for clarifying.

When you say "There will be no weekly release next week (23-27 Dec)."

Does that mean all integration work will stop, or something else?

Thanks, that is useful information, which I have added to MDL-61267, which still seems to be the place to fix this.

Thanks for the explanation Katalin.

So, if the problem is restore, then I wonder if we can fix this by adding code in restore, to just create random qustions in the database, even if they exist in the backup file. (And then write db upgrade code to clean up the database.)

Can you tell me, when you get these unwanted random questoins in the mdl_question table, do you also get related rows in question_versions and question_bank_entries?

Note that LTI is a standard that can be used to launch a tool from any LMS. So, you should not ask "Does Moodle ...", you should ask "Does the tool consumer ...".

Of course, Moodle is free, so I guess it is a useful option to test the tool you are developing with.

The whole point of LTI is that the user will not be prompted again to log in. I should appear seamless.

My suggestion to help you understand this is to find a existing (free) LTI tool, and connect it to a test Moodle install (you could use the test site at https://sandbox.moodledemo.net/). Then go in as a student and launch the tool, while watching the Network tab in the web browser developer tools. That will show you what then launch is.

I don't know of a good free LTI tool to recommend for testing this, but while I was searching for one, I fould this, which might be helpful: https://github.com/SanDiegoCodeSchool/lti-node-example