Affects Version/s: 2.5
Fix Version/s: 2.5
- Enable file system repository but do not allow course/user instances
- Create a system-level file system repository (does not need to be a link like Eloy described)
- Make sure users can access this repository from all: system context, user context (private files) and course context
Pull from Repository:
Pull Master Branch:wip-
Pull Master Diff URL:
Hi, here it's a problem I just have detected with file system repository global instances under master. It works perfectly under 24_STABLE so, at some point something has changed.
1) Have a directory anywhere in your hard disk with read perms to the webserver user. Name it "fs_repo_global". Put some stuff into it (images, backup files, whatever...).
2) In your site's moodledata/repository, create a soft link to the directory created in 1). Name it "fs_repo".
3) Go to your site admin -> plugins -> manage reports and enable the file system repository.
4) Add a site-wide instance to it pointing to the "fs_repo" directory (soft link).
5) Mini-problem1, unrelated. The drop-down menu really sucks. It should have a "Pick one ..." element.
6) Mini-problem2, not sure if unrelated or no. This notice is shown:
7) Super-problem1, go to any page in your site (frontpage or course page) and try to get access to the fs_repo by using the "restore course" or "edit course settings" -> summary -> html editor -> images button. The "fs_repo" is not there anymore.
8) Instead, add a new discussion -> post -> html editor -> images button (or add any file as attachment to the post). The fs_repo" is there, you can pick images perfectly.
So this is sort of... site-wide instances not working at course level anymore, but available at activity level (given 7 & 8 above). Not sure if the definition is accurate.
All the steps above as admin. The site-wide repo instance should be available everywhere, isn't it?
Note I don't know if this problem is caused because of the repo being a soft link to another directory (don't think so, really) or because of some regression/change at some point. But IMO that site-wide instance should be available always.