Question preview error Undefined property: _hx_array::$a

[kiratskitizing]

Using environment
Moodle Code: 4.1.3 (Build: 20230424)
Filter Wiris: 2023042400

Setup = Enabled site wide Filter MathType by WIRIS.

1. Create a course.
2. Go to the Question Bank.
3. Add a Question.
4. Select WIRIS QUIZZES -Cloze Science
   name: my Wiris Q
   question text (copy and paste to editor): test123 {1:SA:=#m1100000000} {1:MCS:=#SG11#SG12~#SG13~#SG14}
   «math xmlns=¨http://www.w3.org/1998/Math/MathML¨»«mo»§#8943;«/mo»«/math»
5. Click "Decode and verify the question text" and save it.
6. Preview the question.
   RESULT:

Exception - Undefined property: _hx_array::$a (errno: 2) in [dirroot]/filter/wiris/integration/lib/php/Lib.class.php at line #31

Debug info:
Error code: generalexceptionmessage 
Stack trace:

    line 49 of /question/type/wq/quizzes/lib/com/wiris/quizzes/wrap/QuestionWrap.class.php: HException thrown
    line 264 of /question/type/shortanswerwiris/question.php: call to com_wiris_quizzes_wrap_QuestionWrap->getSlots()
    line 254 of /question/type/shortanswerwiris/question.php: call to qtype_shortanswerwiris_question->is_text_answer()
    line 322 of /question/type/shortanswerwiris/question.php: call to qtype_shortanswerwiris_question->format_answer()
    line 184 of /question/type/multianswer/question.php: call to qtype_shortanswerwiris_question->get_correct_response()
    line 161 of /question/type/wq/question.php: call to qtype_multianswer_question->get_correct_response()
    line 322 of /question/type/multianswerwiris/question.php: call to qtype_wq_question->get_correct_response()
    line 1291 of /question/engine/questionattempt.php: call to qtype_multianswerwiris_question->get_correct_response()
    line 828 of /question/engine/questionusage.php: call to question_attempt->get_correct_response()
    line 235 of /question/bank/previewquestion/preview.php: call to question_usage_by_activity->get_correct_response()

[icaparros-at-wiris]

Hello @kiratskitizing.

First of all, thank you for reporting the issue! This bug will be fixed in the next release in the second half of November.

Thank you :)