Posts made by Tim Hunt

Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
Look directly in the database, I'm sure the code is not missing. I think the bug is probably to do with what happens when the editing form is redisplayed to let you edit an existing question. But that is only a guess. If you can compare what is on screen at various times with what is stored in the database, you can probably work out exactly which bit of the process has a bug in it, and that would be really helpful.

If the bug still occurres with an up-to-date version (1.7.3+. 1.8.3+ or 1.9 beta2+) then please file an issue in the tracker.
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
The reason it is difficult is that different question types use different extra tables to store parts of their definition, and the students results are stored in the mdl_question_states table in the answer field in a way that is question-type dependant.

So if you only use a few question types in your quiz, and stare hard at http://docs.moodle.org/en/Development:Quiz_database_structure, you can probably come up with a query that is good enough. If you want a general solution that works perfectly, you will have to use PHP code and include the individual question type classes.
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
In that case I don't understand why it doesn't work.

If Staff and Authenticated user are both overridden in the block to allow and prevent, so they cancel at that level, why does it not then inherit from the sitewide definition of the two roles, which then gives allow?
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
Because I had not seen that bug before. I can't remember what searches I did in the tracker before creating a new issue, but clearly they weren't good enough.

I needed to get the HTML block backup and restore bug fixed, so I discussed it with Eloy who is the backup and restore expert, then did the simplest fix I could do.

This was clearly an important set of patches, so it is a pity that it did not get onto people's radars. I know you assigned it to Martin, but there are nearly 2000 bugs assigned to Martin in the tracker (http://tracker.moodle.org/browse/MDL) so the chances of that getting it noticed are small.

You only marked it as being in Component Blocks. You can select multiple components, so if you had added Backup too, Eloy might have seen it and done something.

You could also have set the fix version/s field to include 1.9, to indicate that you think it should go into that release. That would have got it onto this list: http://tracker.moodle.org/secure/IssueNavigator.jspa?mode=hide&requestId=10251 which would have got people to look at it.

Finally, you could have pingged Martin, or one of the other HQ developers outside the tracker, to ask them look at it.