Basically what happens on demo.moodle.org is the entire database is rolled back to old files (which can be in any state we like, including any kind of user data). Every change from the past hour is thrown away. This is all done at Unix level, you don't need to do anything special in Moodle.
Martin Dougiamas
貼文的作者是 Martin Dougiamas
We should make it very soon. Currently there are 152 reported bugs targeted for 1.9.1. It's a matter of how many of those get pushed forward to 1.9.2.
How do Moodle developers at edu institutions account for their work in Moodle? That's up to them, and it varies. Some of them are just making things work locally (normal IT work), then they contribute the results back to Moodle. Some have taken up "positions" to maintain this or that module officially. You can see a lot of the affiliations here:
http://moodle.org/cvs
The release notes for recent versions have included team names for major features:
http://docs.moodle.org/en/Release_notes
Some of the donors listed here (from the past year):
http://moodle.org/donations
Many thousands of insitutions contribute by using Moodle Partners for support services. By doing so they contribute 10% of their services cost to Moodle development.
Finally there are registered Moodle users here:
http://moodle.org/sites
None of these is comprehensive, for various reasons.
http://moodle.org/cvs
The release notes for recent versions have included team names for major features:
http://docs.moodle.org/en/Release_notes
Some of the donors listed here (from the past year):
http://moodle.org/donations
Many thousands of insitutions contribute by using Moodle Partners for support services. By doing so they contribute 10% of their services cost to Moodle development.
Finally there are registered Moodle users here:
http://moodle.org/sites
None of these is comprehensive, for various reasons.
The legacy role is the key. Uploading users as "student" will pick the first legacy role it finds. We can't rely on names or anything else as people change them.
Usually you would only have one role "blessed" using the legacy setting as the standard student role. You had two so it picks the first one it finds. You had bad luck this time, sorry.
The fix would be to remove the legacy setting for your new role, and just leave it there for the original role. You can also explicitly specify roles to use by their shortname (see help on that page).
Usually you would only have one role "blessed" using the legacy setting as the standard student role. You had two so it picks the first one it finds. You had bad luck this time, sorry.
The fix would be to remove the legacy setting for your new role, and just leave it there for the original role. You can also explicitly specify roles to use by their shortname (see help on that page).