Posts made by Visvanath Ratnaweera

Picture of Particularly helpful Moodlers Picture of Translators

According to https://stats.moodle.org/ the no. 1 version is use is Moodle 4.4 with 24%.

What is no. 2, what do you think? If you said 4.3, you're wrong. It is the 4.1 LTS with 18.3%.

And the surprise, 4.3 is not even no. 3, it has to share the third place with 3.11, both way behind with 8.4% resp. 8.5%.

So the "Your site is not up-to-date" scare in the version check is not bringing the expected results, eh?

I hope, 4.5 LTS will consolidate that, but unlikely do to do that in its 4.5(.0) release.

Average of ratings: Useful (1)
Picture of Particularly helpful Moodlers Picture of Translators

What do you mean by "raw files"? The mp3 you've uploaded to Moodle? Sure they are there, not converted to any other format. They have just been renamed to a hash of their content and in moodledata/filedir/ab/cd/abcdef1234..... You can find their original names and many other information in the Moodle database and can do what you want with them.

If the provider supports a different audio format you can't just replace the files, since the new files will have different content hashes and new names too (counting the file extension).

As I always say, the Moodle repository is convenient for the end user, a nightmare for the system administrator.

BTW, the above is to my knowledge and what immediately came to my mind. There could be more practical solutions which I'm not aware of (and willing to learn).

Average of ratings: Useful (1)
Picture of Particularly helpful Moodlers Picture of Translators
Well, you can serve them from a different web server. You could run your own web server and upload the mp3 to a place where it serves the files. Then go to every place on your Moodle where it serves a mp3, change them to a URL, something like yoursite/upload/audio.mp3.

Alternatively, you can upload them to some kind of media service like, YouTube, Vimeo, Odysee, Peertube, ..

Be aware that then the participants are able to see the URLs and share them with non-participants.
 
As you see, the root cause of the problem is your provider. You have to find a provider who allows the type of files you need. Next time he'll say no PNGs, what will you do?
Average of ratings: Useful (2)
Picture of Particularly helpful Moodlers Picture of Translators
Rick

For those you were reading at the beginning and the lost - the thread is ridiculously long for something as straight-forward as a Moodle migration - could you confirm what I remember is correct?

a) This is about two managed Moodle sites the OP is trying to reproduce locally. I repeat, *reproduce*, so no upgrading, neither the core nor the additional plug-ins.

b) The OP has all the three components of a Site backup intact.

c) The moodledata directories are huge so that quick up-down-load, installing in VMs in laptops, etc. are not feasible.

d) The core has been customized by the supplier.

e) The sites have a very large number of additional plug-ins installed, some of them are not even in the official plug-in database.

f) The environment the sites run (ran) are not known (other than re-engineering from the backups available).

If all that is correct, I see a professional challenge the OP faces, which he can't simply delegate to a loose collection of "open source fans" spread around the world - independently of how much they "love" their software. Software is one thing, running them is a different thing. A neighbour, who is a big fan of lawn mower X, will gladly lend you his mower but he is unlikely to cut your grass.