wiris / moodle-qtype_multianswerwiris Goto Github PK

When previewing the question on Moodle 3.1, I am seeing debugging warning:

Warning: Declaration of
qtype_multianswerwiris_helper_renderer::subquestion(question_attempt $qa, question_display_options $options, $index, $subq)
should be compatible with
qtype_multianswer_renderer::subquestion(question_attempt $qa, question_display_options $options, $index, question_graded_automatically $subq)
in .../question/type/multianswerwiris/renderer.php on line 27

The plugin description reads

On the student's side, they will be able to introduce their answers by using a WYSIWYG formula editor and, if the teacher so specifies, they will have access to a WIRIS cas session to make some calculations.

I tried to use a SHORTANSWER subquestion with a variable value as the right answer. But to the student, there is no wiris input element displayed. Only the common HTML input field is displayed.

An error is appearing after doing the following steps in Moodle 4.0:

• Create a course
• Go to Course -> Question Bank
• Select "Import"
• Select Moodle XML format
• Import the following file attached Test file This file is located in multianswerwiris/tests/fixtures/testquestion.moodle.xml and is used for the Behat tests of the plugin.
• After this, you should see "Parsing questions from import file.". Click on Continue.
• Now Edit the created question.
• In the edit view, just click on Save Changes without making any change.
• The following error appears:

This may be because in multianswerwiris/questiontype.php line 151, $authorizedquestion->category is unset. There is a variable that may contain the category which is $authorizedquestion->questioncategoryid but this one can also be unset. A possible solution can be something like this:

if (isset($authorizedquestion->category)) {
            $question->category = $authorizedquestion->category;
        } elseif (isset($authorizedquestion->questioncategoryid)) {
            $question->category = $authorizedquestion->questioncategoryid;
     }

... but I'm not sure in which escenarios this may not work.

Thanks.