Visvanath Ratnaweera

Ken

Many thanks for your detailed information! It took me by surprise. When I said "I don't mind a cleaning action with all the testing involved", I didn't mean a full surgery.
;-(

Based on this discussion I made the decision to do the 2.7-to-3.1 migration first, without touching the legacy files. Then I will transfer the 3.1 site to a test server and practice the surgery. Will keep in touch.

The "political will" can be stirred, if there is belief! The question is, will "start again from scratch" solve the problem (forever)? If that means course backup and restore, it might not. (See method 1 proposed by William https://moodle.org/mod/forum/discuss.php?d=349988#p1412215.)

If "start again from scratch" means rebuilding the courses, method 3, that will work, technically. But to drag their owners, I am going to need more than just the will.


Theoretically, I could do the job myself. Even if I offer the "few days" it needs, teachers won't accept it: It is plain paternalism in their eyes. (The German word is beautiful: "bevormunden", lit. "to beat the mouth".)

So, the Gordian Knot type? Brilliant idea millennia ago. Not today!


Seriously, people recycle their courses. If you knew the kind of chin-ups they do just to avoid "another" course!

Also die Aussage ist, wenn du den Vorschlag vom Moodle fuer moodledata von Hand anlegst, kannst du mit der Installation weiterfahren. Hingegen, wenn du vor dem Installationsstart ein anderes Verzeichnis von Hand angelegt hast, bleibt Moodle an dem Punkt haengen, mit der Meldung "moodledata kann nicht erstellt werden" (sinngemaess).

Interessant. Meine Erfahrung ist, dass die Meldung vom Moodle an dieser Stelle richtig ist. Was ist das fuer einen Server? Hat er irgendwelche Einschraenkungen?

Hallo Tobias

Es kann nicht sein, dass ein so gravierendes Problem sechs Jahre ungeloest bleibt!
;-(

Beschreibe _dein_ Problem! Wie genau, steht zu oberst im Forum, https://moodle.org/mod/forum/view.php?id=949, beschrieben.