Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Upgrading themes to Moodle 3.6

From MoodleDocs
Revision as of 11:16, 13 December 2018 by Bas Brands (talk | contribs) (Created page with "{{Moodle 3.2}} {{Template:Themes}} Moodle 3.6 adds a few new features that effects child themes, the new messaging user interface requires a renderer callback to load the mes...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Moodle 3.2


Moodle 3.6 adds a few new features that effects child themes, the new messaging user interface requires a renderer callback to load the message drawer. This can affect boost and bootstrap base child themes.

Boost based child themes

If your child theme overrides one of these Boost layout files:

templates/columns1.mustache templates/columns2.mustache

You will need to add this callback to your custom layout file:

{{{ output.standard_after_main_region_html }}}

You custom layout file might define its own main content region, adding the renderer callback after this region should make it work:

...

{{{ output.standard_after_main_region_html }}} If your theme defines its own layout files, make sure the callback is added there too. The callback should not be added to layout files for login, maintenance or the secure.mustache layout.

Bootstrapbase based child themes

If your child theme overrides one of these layout files:

layout/columns1.php layout/columns2.php layout/columns3.php

You will need to add this callback to your custom layout file:

<?php echo $OUTPUT->standard_after_main_region_html() ?>

You custom layout file might define its own main content region, adding the renderer callback after this region should make it work:

...

<?php echo $OUTPUT->standard_after_main_region_html() ?>

If your theme defines its own layout files, make sure the callback is added there too. The callback should not be added to layout files for embedded, maintenance, popup or the secure.php layout.