I have a couple of problems with this module from the back-end. I haven't used it in over a month though, so it's possible at least some of these have been addressed in the interim.

  1. When a user creates a quiz, the quiz is usually created before the questions. This creates down-time between the quiz's creation and the quiz's completion during which the quiz is published but doesn't work. Some kind of AJAX interface would be great, so users could add questions as needed. It would also simplify the interface because users tend to be confused when submitting a quiz with no questions.
  2. Sometimes, I don't want people who are creating a quiz to be able to choose questions that have already been added. It would be nice if choosing already-added questions was permissions-based.
  3. On multiple-choice questions, any answers that aren't filled out when creating the question still show up when a user is taking the quiz - they just have blank choices. In other words, I need some questions to have less than 5 choices.
  4. Quizzes should be allowed to have less than 10 questions. In particular, if a user creates a quiz with 3 questions, the quiz should work; then the user can come back later and add more questions if necessary.

That's all I can think of ATM. Sorry for not posting this as multiple issues.

Comments

westwesterson’s picture

westwesterson commented
Status: Active » Closed (won't fix)

Some of this has been addressed in the new beta from quiz 1.1 some of this still needs work.

1. after you create a quiz when you view the quiz for the first time, it will tell you that you need to assign questions, with a link to the page where you assign questions.

2. this probably could use work, I would need to see this in action, but i generally agree that since questions are nodes, they should have the ability to be permissioned as a node within the quiz interface. (not sure how possible this is now, but I would check out the existing node permission systems and see if you can already do this.

3. this should not be the case. this is not how it works (or should work in the 2.0 beta.

4. this is how it currently works in the 2.0beta version 1.1 is notoriously buggy and is bearly suported, it is being completely unsupported as of august 1st. Also the head version of this module is not stable, and is outdated. so please do not use that version.

If these are problems you are having with the current beta feel free to refile these as separate bugs so they can be dealt with accordingly.