Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-30749

notices when exporting answers using question/type/questiontypebase.php code

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.1.4, 2.2.1
    • Fix Version/s: 2.1.4, 2.2.1
    • Component/s: Questions
    • Labels:
      None
    • Testing Instructions:
      Hide

      Turn debugging on, and output error messages as part of the page.

      Export a question to XML format using a type which does not override the base export_to_xml method (such as the varnumericset question type found here : https://github.com/jamiepratt/moodle-qtype_varnumericset), ensuring that the feedback blocks are in HTML format.

      Check that there are no php notices in the exported question's file.

      Import the question from the XML file and then edit it. The feedback edit areas should now be HTML editors.

      Show
      Turn debugging on, and output error messages as part of the page. Export a question to XML format using a type which does not override the base export_to_xml method (such as the varnumericset question type found here : https://github.com/jamiepratt/moodle-qtype_varnumericset ), ensuring that the feedback blocks are in HTML format. Check that there are no php notices in the exported question's file. Import the question from the XML file and then edit it. The feedback edit areas should now be HTML editors.
    • Affected Branches:
      MOODLE_21_STABLE, MOODLE_22_STABLE
    • Fixed Branches:
      MOODLE_21_STABLE, MOODLE_22_STABLE
    • Pull Master Branch:

      Description

      There is still a problem with exporting answers using the code in the base class.

      The code mistakenly refers to $question->feedbackformat rather than $answer->feedbackformat at line 1012.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  9/Jan/12