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

progress_bar used in a non-CLI script without setting NO_OUTPUT_BUFFERING while importing competency framework

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.6
    • Fix Version/s: 3.4.7, 3.5.4
    • Component/s: Competencies
    • Labels:
    • Testing Instructions:
      Hide
      1. Login as an admin.
      2. Go to Site administration ► Competencies ► Competency Frameworks
      3. Create a competency framework CF1 if you don't have any.
      4. Update framework with at least 3 levels of competencies, one competency rule, some related competencies and some custom scales.
      5. Go to Site administration ► Competencies ► Export competency framework
      6. Select CF1 as "Competency framework" and press Export
      7. Check downloaded file and ensure the data exported is as expected.
      8. Edit exported file in text editor and update parent id number and id number for each competency
      9. Go to Site administration ► Competencies ► Import competency framework
      10. Select exported file and press import
      11. Make sure you don't get the following debugging message:

        progress_bar used in a non-CLI script without setting NO_OUTPUT_BUFFERING.
        line 4826 of /lib/outputcomponents.php: call to debugging()
        line 82 of /lib/classes/progress/display.php: call to progress_bar->__construct()
        line 96 of /lib/classes/progress/display_if_slow.php: call to core\progress\display->start_html()
        line 277 of /admin/tool/lpimportcsv/classes/framework_importer.php: call to core\progress\display_if_slow->start_html()
        line 75 of /admin/tool/lpimportcsv/index.php: call to tool_lpimportcsv\framework_importer->__construct()
        

      Show
      Login as an admin. Go to Site administration ► Competencies ► Competency Frameworks Create a competency framework CF1 if you don't have any. Update framework with at least 3 levels of competencies, one competency rule, some related competencies and some custom scales. Go to Site administration ► Competencies ► Export competency framework Select CF1 as "Competency framework" and press Export Check downloaded file and ensure the data exported is as expected. Edit exported file in text editor and update parent id number and id number for each competency Go to Site administration ► Competencies ► Import competency framework Select exported file and press import Make sure you don't get the following debugging message: progress_bar used in a non-CLI script without setting NO_OUTPUT_BUFFERING. line 4826 of /lib/outputcomponents.php: call to debugging() line 82 of /lib/classes/progress/display.php: call to progress_bar->__construct() line 96 of /lib/classes/progress/display_if_slow.php: call to core\progress\display->start_html() line 277 of /admin/tool/lpimportcsv/classes/framework_importer.php: call to core\progress\display_if_slow->start_html() line 75 of /admin/tool/lpimportcsv/index.php: call to tool_lpimportcsv\framework_importer->__construct()
    • Affected Branches:
      MOODLE_36_STABLE
    • Fixed Branches:
      MOODLE_34_STABLE, MOODLE_35_STABLE
    • Pull from Repository:
    • Pull 3.4 Branch:
    • Pull 3.5 Branch:
    • Pull Master Branch:
      MDL-63823-master

      Description

      When importing a competency framework I see this error twice:

      progress_bar used in a non-CLI script without setting NO_OUTPUT_BUFFERING

      I see it first when I upload the file and then again when I confirm that I want to import it. It appears in both Boost and Clean. I discovered the problem while testing MDLQA-12783.

      I tried defining 'NO_OUTPUT_BUFFERING' in admin/tool/lpimportcsv/index.php. That suppressed the error, but the progress bar did not perform correctly. The import was very fast but the progress bar remained grey.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  14/Jan/19

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 23 minutes
                  23m