Tim Hunt

That looks like something went badly wrong when upgrading 2.0 -> 2.1.

As part of that upgrade, the following should have happened:

1. old question_attempts table renamed to question_usages
2. new question_attempts table created
3. extra columns added to question_attemps

It looks to me like steps 1. and 2. got missed out. I have no idea how that could have happened. You will need to investigate, and try to work out what did happen.

You are right. The relevant code is the check_safe_browser method in mod/quiz/accessrule/safebrowser/rule.php. As you can see, that is woefully insecure. You should be able to change that to something better.

If you look at the process_finish method in mod/quiz/attemptlib.php, you will see that you are wrong. quiz_save_best_grade is called before fire_state_transition_event. So, you should be able to get the score in the event handler.

"If I want to push my whole repository to our git-server so the files below "pmatch" are lost because there is a ".git" directory inside, isn't it?"

That statement is incorrect.

When you are in the top-level folder (moodle), then git there will see all the changes in subfolders, including question/type/pmatch. (It will just ignore the question/type/pmatch/.git folder).

Just so you know, I work at the Open University where we have 200,000+ users. It is exactly because we are thinking big that search results have to be limited to a reasonable number. 100 seems reasonsable to me.

If you need to adminster Moodle at larger scale, look at the the various authentication and enrolment plugins that let you integrate with the data in your institution's other database, without requiring manual enrolment in Moodle at all. Alternatively, look at the various bulk upload options.