Moodle

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.9, 1.9.1, 1.9.2, 1.9.3, 1.9.4, 1.9.5, 1.9.6
• Fix Version/s: None
• Component/s: Administration
• Labels:

  None
• Environment:

  n/a

Configuring different parts of Moodle to use a directory in the dataroot currently uses a manually-typed path to the dataroot. For example, Flat File Enrollment. If you want to upload to moodledata/enrollments/enroll.txt, you mus put in the path to your moodledatafolder. Say, for example, "/var/moodledata/enrollments/enroll.txt"

But this misses something that seems obvious to me, which is that the path to the Moodledata folder is then hard-coded, even though there is a dynamic, single configuration vaule available to use – $CFG->dataroot.

So what happens when your Moodledata has to move somewhere else? Say, to an NFS-mounted SAN or other local disk or whatever. You have to find every config point and change it. There may be several, or one, but even if there is only one, if it gets missed, it will break the config for that Moodle feature.

I hope this feature/improvement request is clear. My understanding is that moodledata abstraction in Moodle 2.0 and forward may make this request moot.

• Assignee:

  moodle.com

  Reporter:

  Jeffrey Silverman

  Participants:

  Jeffrey Silverman, moodle.com

• Created:

  06/Nov/09 12:45 AM

  Updated:

  06/Nov/09 12:45 AM