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

calendar_adminseesall does not really show events in all courses

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • 2.7.8, 2.8.8, 2.9.2, 3.0.2, 3.1.3
    • Calendar
    • MOODLE_27_STABLE, MOODLE_28_STABLE, MOODLE_29_STABLE, MOODLE_30_STABLE, MOODLE_31_STABLE
    • Hide
      • admin user activates calendar_adminseesall in website administration
      • adds block calendar i.e. to my moodle site
      • goes to "Detailed month view for:" (via month link in block)
      • compares "all courses" events with course events of single courses (therefore you'd need a moodle installation with various courses I guess)
      Show
      admin user activates calendar_adminseesall in website administration adds block calendar i.e. to my moodle site goes to "Detailed month view for:" (via month link in block) compares "all courses" events with course events of single courses (therefore you'd need a moodle installation with various courses I guess)

      Admin does not see all course events in the calendar as expected when calendar_adminseesall is active

      Apparently this has been there for a while but not really looked into (maybe it cannot be reproduced easily - but discussion is there ... https://moodle.org/mod/forum/discuss.php?d=196177)

      Result: all courses does not mean that admin sees all course events

      Edited: after long discussion we found out that this happens because of the 20 courses limit in function calendar_get_default_courses() - admin does not see events in the courses that are not in first 20.

            wjroes W.J. Roes
            barbara.braun Barbara Braun
            Andrew Lyons Andrew Lyons
            Votes:
            8 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved:

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