Great module, but my client has to make ~30 multi-choice quizzes per month and since the upgrade to 4.x the process has become unnecessarily long winded. The two issues are:

1. WYSIWYG always enabled for multi-choice alternatives (we want plain text, no format option, or default - always goes to our site default format)... might be fixed by #957924: support better_formats (about to test that patch and comment on there) but really HTML is overkill for most so an option to choose the input format would be very beneficial.

2. Question alternatives have a cumbersome and extraneous (for majority of use-cases) 'Alternative [X]' fieldset meaning user can no longer easily tab between answers. Before we could just cut, tab, paste or type between alternatives - now there's all this extra UI in the way. I understand why the fieldsets exist, I just reckon perhaps they're in the wrong place - maybe it'd be better to put the 'Advanced options' together under a separate fieldset after the alternatives so the flow data entry is not broken or complicated. Or perhaps allow the extra options to be disabled somehow?

I realise this is all fixable with some hook_form_alter goodness, but I think this otherwise excellent module should aim for streamlined entry and 'simple case' excellence first off...

Just wondered your thought before I thought further about patches etc.?

CommentFileSizeAuthor
#4 better_multichoice_filter_and_ui-1053726-04.patch3.67 KBJim Kirkpatrick
#2 input_formats_better_answer_entry.patch.patch3.81 KBJim Kirkpatrick
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

falcon’s picture

falcon CreditAttribution: falcon commented
Category: bug » task

I agree, but I do not agree that this is a bug. How do you plan to solve this?

1. Did the patch fix the problem?
2. Would tab indexes help?

Jim Kirkpatrick’s picture

Jim Kirkpatrick CreditAttribution: Jim Kirkpatrick commented
Status: Active » Needs review
FileSize
input_formats_better_answer_entry.patch.patch3.81 KB

Hi Falcon,

1 didn't really help - the issue is that as far as I can see the multichoice module assumes the answer input format is set, but I see nowhere in the code it actually is.

So, attached is a patch (against 4.0, not DEV) that adds a choice of 'Default answer input format' to the multichoice admin screen, ensures that's used as a default - or the saved answer format is if present. This DOES NOT add the input formats option to the answers - that's a separate issue. This just sets up sensible defaults and integrates with the admin screen.

It also keeps the alternatives answers fieldsets expanded when index < default number of alternatives, not the arbitrary "2" that's currently in place.

I'll check with my client but I think that, when combined with a new 'plain text' input format, this fixes the issues I raised for us. Let me know if you want any alterations.

EDIT: If you like this and want this patch against DEV (and you probably do) let me know...

Jim Kirkpatrick’s picture

Jim Kirkpatrick CreditAttribution: Jim Kirkpatrick commented

Bump to - remind me to re-roll the patch above against DEV... - and to hope that this usability improvement makes it into the next version.

Any chance if I submit a refreshed patch? Hope to next week...

Jim Kirkpatrick’s picture

Jim Kirkpatrick CreditAttribution: Jim Kirkpatrick commented
Title: Entering multi-choice alternatives now overcomplicated, slightly cumbersome in 4.x » UI and Filter improvements to help users when entering lots of multi-choice questions
Version: 6.x-4.0 » 6.x-4.x-dev
FileSize
better_multichoice_filter_and_ui-1053726-04.patch3.67 KB

New patch for the following UI and filter handling improvements against 6.x-4.x-DEV:

  1. When entering a multi-choice question, the "Default number of alternatives" (from http://www.example.com/admin/quiz/settings/questions_settings) are pre-expanded, rather than the arbitrary '2' hardcoded presently.
  2. Adds a 'Default answer input format' to the above "Question configuration" page which is then used when entering each multi-choice option. We need this because we don't want rich text/html for options, just plain text. Others might want it to avoid huge WYSIWYG editors for simple options that might say 'Yes', for example.
  3. Basic Better Formats integration for quiz forms.

Note: this is related to #534716: Question bodies hidden when user doesn't have access to input format should ideally committed ASAP to avoid multi-choice options saying 'n/a' because of incorrect check_markup() code.

djdevin’s picture

djdevin
Location Philadelphia
CreditAttribution: djdevin commented
Issue summary: View changes
Status: Needs review » Closed (outdated)

This issue is being closed because it was filed against a version that is no longer supported. If the issue still persists in the latest version of Quiz, please open a new issue.