> whereas the answer is so simple
Except that wasn't the answer, because I wanted to disable all forms of enrollment and have no users subscribed; the courses should not display in anyone's 'my courses' list. The answer was to disable the 'guest' feature at the site level (forcing log-ins), enabling 'guest without password' at the course level, and disabling all other enrollment types. The official docs don't make it clear that these two guest features are independent of one another.
> you are the wrong person to manage your school's Moodle
No, I am the wrong person to spend hundreds of hours of my own spare time, free of charge, on top of an already full workload, trying to fix a system that was not implemented properly, on software that is barely fit for purpose, for a bunch of teachers and students who don't even want to use it. I'd like to know who the right person is, under those circumstances.
> If you could maintain a civilized language
I read WTF as 'what the fudge'. If you swear in your head while reading that acronym, then it perhaps says more about you than me!
No-one is forcing you to swear in your head, except yourself! In a second language no less!
> I hope that this incompatibility is not a wider problem, that it touches only Moodle
I put 100% into everything I do, and gave Moodle (v2.5) a damn good chance. It fell short in just about every admin task I needed to perform. So, no. The problem is not me. The only way someone else could have got further with it, is if they ignored the Moodle web interface completely and set up all the courses, subscriptions, groups/groupings and blocks using a combination of php scripts, CSV, LDAP and database queries. But then, a person with that kind of skillset would not be working during their evenings, weekends and holidays for free, would they?