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

Tiny Editor not working on debugging mode if debugging message shown in header

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • None
    • 4.4
    • Text editor TinyMCE
    • None
    • MOODLE_404_STABLE

      Description

      The Tiny Editor is not always loaded correctly if the debugging mode has been activated and a debugging message is displayed in the header.

      An error is displayed in the console 

      // Failed to initialize the editor as the document is not in standards mode. TinyMCE requires standards mode. 

       

       

      As mentioned [here|https://moodle.org/mod/forum/discuss.php?d=452111&parent=1826078] the reason is the missing <!DOCTYPE html> tag at the top of the page.

      Testing-Instructions

      1. Turn Debugging on (e. g. via $CFG->debug = )E_ALL | E_STRICT); $CFG->debugdisplay = 1; in moodle config.php)
      2. Make sure Editor_Tiny is your chosen editor.
      3. Make sure you get a debugging message in the header
        E.g. you can use the output message for the new Hook API. To do this, you can install a plugin that has not yet fully implemented the new Hook API. One example on your installation could be: https://github.com/catalyst/moodle-tool_heartbeat
      4. As admin create an course.
      • the editor tiny, e.g. in course description is not shown
      • open browser console: Error <Failed to initialize the editor as the document is not in standards mode. TinyMCE requires standards mode.> is shown
      1. Turn Debugging of
      2. Redo step 4 and create an new course
      • the editor tiny is shown in the course description field
      • open the browser console -> no errors

            Unassigned Unassigned
            thomas.ludwig Thomas Ludwig
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

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