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

IMSCC import failed because of a "&"

XMLWordPrintable

    • MOODLE_38_STABLE

      There is an error when importing imscc when a backup file contains an & in its name.
      This character is not escaped correctly to & amp; (without space)

       

      Debut info :
      Error code:
      Fatal Error in [backuptempdir]/d3a1f4e2ab6936a07fc4def38ee9667d/moodle.xml: xmlParseEntityRef: no name at line 76810

      $a contents:
      line 118 of /backup/converter/imscc11/lib.php: imscc11_convert_exception thrown
      line 129 of /backup/converter/convertlib.php: call to imscc11_converter->execute()
      line 206 of /backup/util/helper/convert_helper.class.php: call to base_converter->convert()
      line 500 of /backup/controller/restore_controller.class.php: call to convert_helper::to_moodle2_format()
      line 100 of /backup/restore.php: call to restore_controller->convert()

       

      This is the file in error 

      <MOD>
      <ID>54</ID>
      <MODTYPE>resource</MODTYPE>
      <NAME>Sujet et Corrigé Mai 2018</NAME>
      <TYPE>file</TYPE>
      <REFERENCE>19_Y_19_A_ImportedContent_20191007034226/Mai 2018- sujet & corrigé .pdf</REFERENCE>
      <SUMMARY></SUMMARY>
      <ALLTEXT></ALLTEXT>
      <POPUP></POPUP>
      <OPTIONS>objectframe</OPTIONS>
      <TIMEMODIFIED>1599129271</TIMEMODIFIED>
      </MOD>

       

       

      <REFERENCE>19_Y_19_A_ImportedContent_20191007034226/Mai 2018- sujet & corrigé .pdf</REFERENCE>

      should work if it becomes

      <REFERENCE>19_Y_19_A_ImportedContent_20191007034226/Mai 2018- sujet & amp; corrigé .pdf</REFERENCE>

       

      Thanks

            Unassigned Unassigned
            davidbokobza David Bokobza
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.