Повідомлення, що надісла(ла)в Visvanath Ratnaweera

Фото Particularly helpful Moodlers Фото Translators
@Howard

> At best, a catchall for computing power that's not yours.

Then why do people buy them, for example the monster contracts the US govt. made with Amazon and Microsoft?

@James

> I don't know the location of the hosting server, the OS and hypervisor used, or ..

There must be idiots in the sovereign states who by these "nebulous" things. When I think of it, no wonder that the European governments are suddenly in a great hurry to shake off Microsoft, etc. DT's tariff wars must have awakened them.
Фото Particularly helpful Moodlers Фото Translators

To the SCORM people

This is not strictly a Moodle-SCORM question. It came up in a Moodle-based team and I think the technology needed is very much that of SCORM.

Here's the deal:

A team produces reports in the form of mini-sites. We know that mini-sites can be nicely embedded in Moodle. But the problem is that the recipients are not in a Moodle site. The initial thought was to host the mini-sites in the web and distribute username/passwords to the recipients. Apart from the complications of creating and maintaining the credentials, we don't want to leave the reports on the web - even if password protected. They are confidential in the sense that they are meant for the recipients are they can in turn share them with others they trust.

The next idea is to package each mini-site together with a simple web server binary. Upon unpacking the the package the web server binary will spawn a web server and open the mini-site in it. It should work on MS Windows and for the sake of completeness also on Linux.

Do you have ideas, hints or even examples of this scenario? The information I found on the Web depend on some sort of a programming language in the target machine, say Python, which can spawn a small web server on demand. That condition is not given in our recipients' machines.

Фото Particularly helpful Moodlers Фото Translators
The problem is that the vast majority is not those who start with 5.0, but those who inherit question banks from 4.x. Linked to the discussion/suggestion Add a warning to the Moodle 5.0 upgrade documentation. Please follow up the general topic there.
Фото Particularly helpful Moodlers Фото Translators
Yet another case: Moodle 5.0.1 Question Bank.
 
There are solutions for those who start in Moodle 5. But the problem is the inherited question banks. People have any number of questions, thousands, in various constellations. The unlucky ones have millions (literally) because Moodle was generous in duplication question categories in export/import!
 
P.S. I am not going to defend original idea, we haven't started the transition to 5, so not yet directly confronted. We are still cleaning the millions of duplicated that accumulated in 4.1 LTS and freshly upgraded to 4.5 LTS. The idea is for the sake of those who hurriedly upgrade to 5.0 and run in to trouble.
Фото Particularly helpful Moodlers Фото Translators
Apparently unrelated to MDL-80550. Ref, "the stacktrace you’ve produced on the forum thread is unrelated to the issue originally fixed here (it refers to either a cohort or it’s custom fields being linked to non-existent context record)" https://moodle.atlassian.net/browse/MDL-80550?focusedCommentId=994395

So looking for the cause elsewhere?