Itamar Tzadok

The module could be fairly simple, showing a timer and disabling the input fields on elapsed time. But as I mentioned above this could be easily worked around and so you need also to store question attempt start time and check elapsed on attempt save.

Well, 5 weeks-5 days a week course, each week a section and each day an activity. Sections and activities cannot be accessed before their due date. But also resources in each section cannot be accessed before their respective week. So you would have to set conditios for individual activities but would like to use the section conditions to determine collective access to section resources.

The reason I'm asking is because if the solution referred to in http://tracker.moodle.org/browse/MDL-24419 is merely a bulk adjustment of the activities conditions to their parent section's conditions then I may have a simpler approach which may not require core changes.

Afaict the crux of this whole issue is that activity conditions are contextual and a course section is not a context and so any core change for conditional sections which does not make the section a context is just a hack, not a genuine solution.

Are section conditions prepended to activities conditions or completely changing them? That is, if section conditions are met can there be further activity conditions for activities in the section?

Of coursecat.

Tim, I'm using question_category_options to get a list of question categories from which I generate options for mform select. I can get context instances for system/courses/modules so as to retrieve the respective categories as they appear in the qbank. But the qbank also allows categories in course category contexts. How do I retrieve these categories?