Questionnaire for moodle 2 available

Questionnaire for moodle 2 available

by Joseph Rézeau -
Number of replies: 20
Picture of Core developers Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers Picture of Translators

Good newscool for those who are currently testing Moodle 2 and want to use Questionnaire. You can download that Questionnaire version from here: Download for Moodle 2.0

The Questionnaire Documentation has been entirely re-written.

Please install on your moodle 2 test site and report any remarks, bugs, etc. in this thread. There are a few minor bugs remaining, for you to spot.wink

One of those is that is is not currently not possible to insert images (or other media) in the questions text: CONTRIB-2624.

The online help system has changed a lot in Moodle 2.0 (see Development:Help strings) which means that there is quite some work to be done by translators, especially in the Wiki Docs. Questionnaire translators are invited to contact me for further details.

Joseph

Average of ratings: Useful (2)
In reply to Joseph Rézeau

Re: Questionnaire for moodle 2 available

by Toshimi Hatanaka -

Thank you for your great work!

I tried to create a Japanese version of questionnaire.php and put it in lang/ja/ folder, but Moodle doesn't recognize it.  This way worked on Moodle 1.9. Different process would be needed on 2.0?

Please let me know.

In reply to Joseph Rézeau

Re: Questionnaire for moodle 2 available

by Paul Webster -

Thanks Joseph-

I installed and ran update on the modules from the admin page.  It said it was successful.

Should I be able to see my old questionnaire activities in my courses that I made in 1.9? I can't see them.  It does appear to let me create a new questionnaire activity and it even asks if I want to "copy existing" and it shows me my old questionnaires, as options.  I thought maybe there was a setting in the plugins or modules under the admin section, but I couldn't find anything for Questionnaire.

I would like to get to my old Questionnaires, as they have important results in them.

Thanks

Paul

In reply to Paul Webster

Re: Questionnaire for moodle 2 available

by Paul Webster -

I apparently solved my own problem but I don't know what I did, if anything.

Since it looked like I could make a new questionnaire but not see my old ones I:

  1. Made a new questionnnaire that was copied from an old one.  It said I had an error writing to the database and suggested I turn on debugging.  I couldn't find where to turn on debugging, as it seems to be in a different place in 2.0.
  2. So, I started digging around in the Manage Activities section.  I found that Questionnaire was listed but there are no settings for it.  I closed the eye to make it invisible.  I made it visible again.

Then when I went back to the course, there were my old Questionnaires.

So, I'm not sure if making it invisible/visible fixed the problem or if it just took time (maybe for a cronjob or something).

Anyway, the old ones seem to work now.  I am still getting errors on writing to the database, when I make new questionnaires.  We'll see if that is still a problem after I reboot the server.  I ran updates and did a virus scan on it today as well.

Paul

In reply to Paul Webster

Re: Questionnaire for moodle 2 available

by Paul Webster -

I still am getting database errors when I try to make new questionnaires.  I don't know how to turn on debugging to problem solve this.

In reply to Paul Webster

Re: Questionnaire for moodle 2 available

by Jenny Gray -

To turn on debugging in Moodle 2, you have to be logged in with admin permissions then...

  • In the settings block, expand the site administration section
  • expand the development section
  • click on the debugging link
  • the screen looks much like Moodle 1.9 did, so set debug messages to Developer and put a tick in the display debug messsages checkbox.

Now when you try to create a new questionnaire, you should see more errors.  Copy and paste them here and I'm sure Joseph will find them helpful.

In reply to Paul Webster

Re: Questionnaire for moodle 2 available

by Joseph Rézeau -
Picture of Core developers Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers Picture of Translators

This new bug seems to have developed recently. Please wait for fix.

Reported in the bug tracker as CONTRIB-2653.

Joseph

EDIT.- Bug fixed by Mike. Thanks.

In reply to Joseph Rézeau

Re: Questionnaire for moodle 2 available

by Paul Webster -

Thanks Joseph (and Mike)-

Is the Module Download updated then to fix this now, or should I wait?  I imply, from your Edit, that Mike fixed it but it shows that the last update on the module download page was on January 5.  I think you and Mike posted to the bug notice that it was resolved on January 12.  I'm a little hesitant to download again, as I don't understand the bug fix process that well.  My debugging messages match exactly what Mike posted on the bug log.

Thanks

Paul

In reply to Paul Webster

Re: Questionnaire for moodle 2 available

by Joseph Rézeau -
Picture of Core developers Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers Picture of Translators

Paul,

Do you do your contrib modules updates via CVS or not? If not, simply download the questionnaire version for 2.0 from the modules & plugins database, unzip and overwrite all of the contents of your moodle2.0/mod/questionnaire folder.

I have just checked, the latest files are dated Jan. 13th, so you should be OK with the bug fixes

Joseph

In reply to Joseph Rézeau

Re: Questionnaire for moodle 2 available

by Paul Webster -

Thanks Joseph.  Unfortunately, my server isn't setup to use CVS.  It sounds like updates would be easier if it were.  I will remove the questionnaire folder from my /mod directory and replace it with the new one that I download.

It is my impression that moving over to CVS at this point would be difficult, as it was setup manually.  Maybe when I do a full server update I'll reinstall the newest ubuntu OS and then setup on CVS.

Thanks

Paul

In reply to Paul Webster

Re: Questionnaire for moodle 2 available

by Mary Cooch -
Picture of Documentation writers Picture of Moodle HQ Picture of Particularly helpful Moodlers Picture of Testers Picture of Translators

I've just uploaded the new questionnaire to my moodle 2.0 course and am about to play with it. This isn't an upgrade from 1.9 so I can't comment on any transition issues - so far the only things I have noticed have been theme related (for example the tabs "advanced settings/questions/preview" are not clickable in the Magazine theme I was using so I had to switch to a different one. I think that's the problem of the theme designers though, not the questionnaire writerssmile (Only non-clickable when "no content" had been defined - when I switched to another theme and added some questions and switched back, the tabs in Magazine worked then.)

In reply to Mary Cooch

testing Questionnaire for moodle 2

by Mary Cooch -
Picture of Documentation writers Picture of Moodle HQ Picture of Particularly helpful Moodlers Picture of Testers Picture of Translators

Well, so far so good - questionnaire worked, sent out emails, grades went to gradebook -  exported into Excel and was able to re-use in another questionnaire -I haven't found these (deliberately!) hidden bugs yet, although I have noticed that students can't add images in the essay question but that is doubtless related to the tracker entry mentioned by Joseph above.

In reply to Mary Cooch

Re: Questionnaire for moodle 2 available

by Joseph Rézeau -
Picture of Core developers Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers Picture of Translators

Thanks for testing, Mary. The bug you mention with the Magazine theme is really strange. I will investigate.

Joseph

In reply to Joseph Rézeau

Re: Questionnaire for moodle 2 available

by Joseph Rézeau -
Picture of Core developers Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers Picture of Translators

Unclosed div tags caused display problems with Magazine theme (and of course did not validate W3C).blush

CONTRIB-2672 (fixed)

In reply to Joseph Rézeau

Re: Questionnaire for moodle 2 available

by Nate Jarchow -

I'm seeing an issue viewing rated 1-5 question type responses in the release for 2.0.

Currently I'm working on a test installation running 2.0.1 (build from the 12th) and the plugin downloaded from the link above.

I can add a Rated 1-5 question to a questionnaire, said question will view in the questionnaire, can be reponded to while taking the questionnaire, but when attempting to view review the reponses I get a DB error when the site attempts to display the results of the Rated 1-5 question. All other questions before the Rated question show but none after.

The error is:

Error reading from database

More information about this error

Debug info: ERROR: column "c.content" must appear in the GROUP BY clause or be used in an aggregate function
LINE 1: SELECT C.content, AVG(A.rank+1) AS average, COUNT(A.response...
^
SELECT C.content, AVG(A.rank+1) AS average, COUNT(A.response_id) AS num FROM mdl_questionnaire_quest_choice C, mdl_questionnaire_response_rank A WHERE C.question_id = 6 AND A.question_id = 6 AND A.choice_id = C.id AND A.rank >= 0 AND response_id IN (1) GROUP BY C.id
[array (
)]
Stack trace:
  • line 391 of /lib/dml/moodle_database.php: dml_read_exception thrown
  • line 229 of /lib/dml/pgsql_native_moodle_database.php: call to moodle_database->query_end()
  • line 669 of /lib/dml/pgsql_native_moodle_database.php: call to pgsql_native_moodle_database->query_end()
  • line 562 of /mod/questionnaire/questiontypes/questiontypes.class.php: call to pgsql_native_moodle_database->get_records_sql()
  • line 746 of /mod/questionnaire/questiontypes/questiontypes.class.php: call to questionnaire_question->get_response_rank_results()
  • line 593 of /mod/questionnaire/questiontypes/questiontypes.class.php: call to questionnaire_question->display_response_rank_results()
  • line 2330 of /mod/questionnaire/locallib.php: call to questionnaire_question->display_results()
  • line 620 of /mod/questionnaire/report.php: call to questionnaire->survey_results()
In reply to Nate Jarchow

Re: Questionnaire for moodle 2 available

by Mike Churchward -
Picture of Core developers Picture of Plugin developers Picture of Testers

This fix has been added back to 2.0. The latest in contrib should solve your problem.

In reply to Joseph Rézeau

Re: Questionnaire for moodle 2 available

by Daniele Cordella -
Picture of Core developers Picture of Plugin developers

My question is: what is our target? Do we have to say that questionnaire is here or do we need/like/enjoy questionnaire?

The story of new questionnaire on my computer:

t=0: downloaded and installed
t=2s:

mod_questionnaire

componentname_capabilities array is deprecated, please use capabilities array only in access.php files
  • line 3301 of /lib/accesslib.php: call to debugging()
  • line 3398 of /lib/accesslib.php: call to load_capability_def()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()
Legacy type admin in access.php was renamed to manager, please update the code.
  • line 1707 of /lib/accesslib.php: call to debugging()
  • line 3472 of /lib/accesslib.php: call to assign_legacy_capabilities()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()
Legacy type admin in access.php was renamed to manager, please update the code.
  • line 1707 of /lib/accesslib.php: call to debugging()
  • line 3472 of /lib/accesslib.php: call to assign_legacy_capabilities()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()
Legacy type admin in access.php was renamed to manager, please update the code.
  • line 1707 of /lib/accesslib.php: call to debugging()
  • line 3472 of /lib/accesslib.php: call to assign_legacy_capabilities()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()
Legacy type admin in access.php was renamed to manager, please update the code.
  • line 1707 of /lib/accesslib.php: call to debugging()
  • line 3472 of /lib/accesslib.php: call to assign_legacy_capabilities()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()
Legacy type admin in access.php was renamed to manager, please update the code.
  • line 1707 of /lib/accesslib.php: call to debugging()
  • line 3472 of /lib/accesslib.php: call to assign_legacy_capabilities()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()
Legacy type admin in access.php was renamed to manager, please update the code.
  • line 1707 of /lib/accesslib.php: call to debugging()
  • line 3472 of /lib/accesslib.php: call to assign_legacy_capabilities()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()
Legacy type admin in access.php was renamed to manager, please update the code.
  • line 1707 of /lib/accesslib.php: call to debugging()
  • line 3472 of /lib/accesslib.php: call to assign_legacy_capabilities()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()
Legacy type admin in access.php was renamed to manager, please update the code.
  • line 1707 of /lib/accesslib.php: call to debugging()
  • line 3472 of /lib/accesslib.php: call to assign_legacy_capabilities()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()
Legacy type admin in access.php was renamed to manager, please update the code.
  • line 1707 of /lib/accesslib.php: call to debugging()
  • line 3472 of /lib/accesslib.php: call to assign_legacy_capabilities()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()
Legacy type admin in access.php was renamed to manager, please update the code.
  • line 1707 of /lib/accesslib.php: call to debugging()
  • line 3472 of /lib/accesslib.php: call to assign_legacy_capabilities()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()
Legacy type admin in access.php was renamed to manager, please update the code.
  • line 1707 of /lib/accesslib.php: call to debugging()
  • line 3472 of /lib/accesslib.php: call to assign_legacy_capabilities()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()
Legacy type admin in access.php was renamed to manager, please update the code.
  • line 1707 of /lib/accesslib.php: call to debugging()
  • line 3472 of /lib/accesslib.php: call to assign_legacy_capabilities()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()
Legacy type admin in access.php was renamed to manager, please update the code.
  • line 1707 of /lib/accesslib.php: call to debugging()
  • line 3472 of /lib/accesslib.php: call to assign_legacy_capabilities()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()
Legacy type admin in access.php was renamed to manager, please update the code.
  • line 1707 of /lib/accesslib.php: call to debugging()
  • line 3472 of /lib/accesslib.php: call to assign_legacy_capabilities()
  • line 473 of /lib/upgradelib.php: call to update_capabilities()
  • line 265 of /lib/upgradelib.php: call to upgrade_plugins_modules()
  • line 1352 of /lib/upgradelib.php: call to upgrade_plugins()
  • line 290 of /admin/index.php: call to upgrade_noncore()