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

Unoconv doesn't work after the scheduled task conversion_cleanup_task has run

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide
      1. Set up a Moodle site with working Unoconv with pathtounoconv correctly set up.
      2. View the Unoconv test PDF:
        1. Browse to Site administrationPluginsDocument convertersManage document converters, and click Settings for the Unoconv entry.
        2. Click Test unoconv path.
        3. Click Download the converted pdf test file. The test PDF ("This is a test") should appear.
      3. Delete the file conversion row: DELETE FROM mdl_file_conversion WHERE sourcefileid IN (SELECT id FROM mdl_files WHERE filename = 'unoconv_test.docx' AND filearea = 'fileconverter_unoconv'); This simulates the actions of \core_files\task\conversion_cleanup_task which would delete the row after one week.
      4. View the Unoconv test PDF by repeating the steps under step 2.

      Expected results

      After step 4, the test PDF should appear. No error messages should appear.

      Show
      Set up a Moodle site with working Unoconv with pathtounoconv correctly set up. View the Unoconv test PDF: Browse to Site administration → Plugins → Document converters → Manage document converters , and click Settings for the Unoconv entry. Click Test unoconv path . Click Download the converted pdf test file. The test PDF ("This is a test") should appear. Delete the file conversion row: DELETE FROM mdl_file_conversion WHERE sourcefileid IN (SELECT id FROM mdl_files WHERE filename = 'unoconv_test.docx' AND filearea = 'fileconverter_unoconv'); This simulates the actions of \core_files\task\conversion_cleanup_task which would delete the row after one week. View the Unoconv test PDF by repeating the steps under step 2. Expected results After step 4, the test PDF should appear. No error messages should appear.
    • Affected Branches:
      MOODLE_33_STABLE, MOODLE_34_STABLE, MOODLE_36_STABLE, MOODLE_37_STABLE, MOODLE_38_STABLE
    • Fixed Branches:
      MOODLE_36_STABLE, MOODLE_37_STABLE
    • Pull from Repository:
    • Pull 3.6 Branch:
      MDL-59911-conv_cleanup_check-36
    • Pull 3.7 Branch:
      MDL-59911-conv_cleanup_check-37
    • Pull Master Branch:
      MDL-59911-conv_cleanup_check

      Description

      Hello,

      I'm having problems with Unoconv and Moodle 3.3. Test unoconv path -page says "The unoconv path appears to be properly configured." but when I press "Download the converted pdf test file." I get an error;

      // Coding error detected, it must be fixed by a programmer: id is required to delete
      More information about this error
      ×Debug info: 
      Error code: codingerror
      ×Stack trace:
      line 600 of /lib/classes/persistent.php: coding_exception thrown
      line 197 of /files/converter/unoconv/classes/converter.php: call to core\persistent->delete()
      line 51 of /files/converter/unoconv/testunoconv.php: call to fileconverter_unoconv\converter->serve_test_document()
      

      Also no PDF is generated for the student submissions in the grading window in assingment.

      This happens in Moodles that have been updated from 3.1 to 3.3, they are on the same server as some other Moodle 3.1 installations and in these Unoconv works fine.

      So any ideas how to fix this? Please see also;

      https://tracker.moodle.org/browse/MDLSITE-4616

       Discussion here;

       https://moodle.org/mod/forum/discuss.php?d=357247

        Attachments

        1. MDL-59911.jpg
          MDL-59911.jpg
          50 kB
        2. imageT6x8.png
          imageT6x8.png
          43 kB
        3. error.PNG
          error.PNG
          47 kB

          Issue Links

            Activity

              People

              • Votes:
                34 Vote for this issue
                Watchers:
                40 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  9/Sep/19

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 hour, 5 minutes
                  1h 5m