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

Renderer subtypes should find templates in the "templates" directory only.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • None
    • 2.9
    • HTML and CSS
    • MOODLE_29_STABLE
    • MDL-50040-master
    • Hide
      1. Apply patch file attached to this issue
      2. Go to the event monitor subscription page and verify TEST is added to the page
      3. Go to the template library and verify a template for the tool_monitor can be displayed (it just says TEST)
      1. Create a file at theme/clean/templates/tool_monitor/test.mustache (Put anything in the file you want)
      2. Repeat 2 & 3 and verify that TEST has changed
      Show
      Apply patch file attached to this issue Go to the event monitor subscription page and verify TEST is added to the page Go to the template library and verify a template for the tool_monitor can be displayed (it just says TEST) Create a file at theme/clean/templates/tool_monitor/test.mustache (Put anything in the file you want) Repeat 2 & 3 and verify that TEST has changed

      There is a coding error when generating the file name of the template to search for - so it's not possible to use renderer subtypes properly with templates.

      Further more - it becomes restrictive to limit subtypes from using templates in other subtypes from the same plugin - and harder for themers to determine the folder in which to overwrite a template. We should ignore the subtype everywhere when searching for a template.

        1. 0001-TEST-MDL-50040.patch
          1 kB
          Damyon Wiese

            damyon Damyon Wiese
            damyon Damyon Wiese
            Dave Cooper Dave Cooper
            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.