when the question is created - it is needed to add link "back on quiz" into that question page, or load current quiz page
igorik - July 12, 2007 - 23:09
| Project: | Quiz |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | patch (code needs work) |
Description
Hi!
when the question is created - it is really needed to add link "back on quiz" on that question page, or load current quiz page.
The current state is really has really bad behaviour - after creating question user is on page www.hisdomain.com/question/name-of-new-questions and he/she doesn't know what now
press back, or what...?
Adding and manage questions must be easy and simple for users.
Thanks
Igor
somvprahe.sk
#1
I was thinking of something similar actually. Here is what I think: There needs to be a variable created or appended on the creation of a new question type. This variable will tell the system all of the question types (and should be named exactly as it is in the node_type table). The quiz module should have the following buttons: Add Existing Questions, Add New Questions, and a checkbox to allow the currently logged in user to view only questions that he/she has created. Any questions type node should include the following: a button for more questions and a question types field for what kind of question should be added.
#2
There should also be an option on all question creation pages to go to the last modified quiz by the currently logged in user (that way they can continue the quiz creation process). The button should be entitled: Add Questions to Last Added Quiz. There should also be a checkbox to allow the user to only show his/her questions.
With this workflow, the user still has the ability to have orphaned questions, question types are still generic, and navigation is easier.
#3
I found out there is already a function to tell all question types.
#4
Redirection for multichoice and for quiz modules are included in this patch. This will allow you to navigate from page to page smoothly as you see fit.
#5
I forgot to update the status. Now it's updated.
#6
Subscribing, greetings, Martijn
EDIT: If I was responsable to set this to critical it was not on purpose, sorry then!
Greetings, martijn
#7
Please do not set the priority to critical unless it contains a serious error. A feature request is never critical.
The patch in #4 does not apply to the current head anymore (no surprise... the code has changed a lot since July, 2007). If somebody wants to rewrite the patch, I will test it.
#8
Summit: No, you weren't responsible for setting it to critical. Apparently it has been like that for many months. I just didn't notice before.