Uploaded image for project: 'Plugins'
  1. Plugins
  2. CONTRIB-4195

Processing module function webinar_cron ...!!! Error reading from database !!!

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • 2.2.9, 2.3.7, 2.4
    • 2.3.4
    • Module: Webinar
    • None
    • MOODLE_23_STABLE
    • MOODLE_22_STABLE, MOODLE_23_STABLE, MOODLE_24_STABLE

      The Webinar cron fails to run and produces the following error;

      Processing module function webinar_cron ...!!! Error reading from database !!!
      !! Unknown column 'f.reminderperiod' in 'field list'

      SELECT
      su.*,
      f.course,
      f.id as webinarid,
      f.name as webinarname,
      f.reminderperiod,
      se.details
      FROM
      mdl_webinar_signups su
      INNER JOIN
      mdl_webinar_signups_status sus
      ON su.id = sus.signupid
      AND sus.superceded = 0
      AND sus.statuscode = 70
      JOIN
      mdl_webinar_sessions se
      ON su.sessionid = se.id
      JOIN
      mdl_webinar f
      ON se.webinar = f.id
      WHERE
      su.mailedreminder = 0

      [array (
      )]
      Error code: dmlreadexception !!
      !! Stack trace: * line 407 of /lib/dml/moodle_database.php: dml_read_exception thrown

      • line 966 of /lib/dml/mysqli_native_moodle_database.php: call to moodle_database->query_end()
      • line 1574 of /mod/webinar/lib.php: call to mysqli_native_moodle_database->get_records_sql()
      • line 725 of /mod/webinar/lib.php: call to webinar_get_unmailed_reminders()
      • line 259 of /lib/cronlib.php: call to webinar_cron()
      • line 88 of /admin/cron.php: call to cron_run()
        !!

            maberdour Mark Aberdour
            kyle.armstrong Kyle Armstrong
            Mark Aberdour Mark Aberdour
            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.