Upgrading themes to Moodle 3.6: Difference between revisions
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..." |
David Mudrak (talk | contribs) m Text replacement - "<code php>" to "<syntaxhighlight lang="php">" |
||
| Line 8: | Line 8: | ||
If your child theme overrides one of these Boost layout files: | If your child theme overrides one of these Boost layout files: | ||
< | <syntaxhighlight lang="php"> | ||
templates/columns1.mustache | templates/columns1.mustache | ||
templates/columns2.mustache | templates/columns2.mustache | ||
| Line 15: | Line 15: | ||
You will need to add this callback to your custom layout file: | You will need to add this callback to your custom layout file: | ||
< | <syntaxhighlight lang="php"> | ||
{{{ output.standard_after_main_region_html }}} | {{{ output.standard_after_main_region_html }}} | ||
</code> | </code> | ||
| Line 21: | Line 21: | ||
You custom layout file might define its own main content region, adding the renderer callback after this region should make it work: | You custom layout file might define its own main content region, adding the renderer callback after this region should make it work: | ||
< | <syntaxhighlight lang="php"> | ||
<div id="page" class="container-fluid"> | <div id="page" class="container-fluid"> | ||
... | ... | ||
| Line 33: | Line 33: | ||
If your child theme overrides one of these layout files: | If your child theme overrides one of these layout files: | ||
< | <syntaxhighlight lang="php"> | ||
layout/columns1.php | layout/columns1.php | ||
layout/columns2.php | layout/columns2.php | ||
| Line 41: | Line 41: | ||
You will need to add this callback to your custom layout file: | You will need to add this callback to your custom layout file: | ||
< | <syntaxhighlight lang="php"> | ||
<?php echo $OUTPUT->standard_after_main_region_html() ?> | <?php echo $OUTPUT->standard_after_main_region_html() ?> | ||
</code> | </code> | ||
| Line 47: | Line 47: | ||
You custom layout file might define its own main content region, adding the renderer callback after this region should make it work: | You custom layout file might define its own main content region, adding the renderer callback after this region should make it work: | ||
< | <syntaxhighlight lang="php"> | ||
<div id="page-content" class="row-fluid"> | <div id="page-content" class="row-fluid"> | ||
... | ... | ||
Revision as of 13:34, 14 July 2021
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:
<syntaxhighlight lang="php"> templates/columns1.mustache templates/columns2.mustache
You will need to add this callback to your custom layout file:
<syntaxhighlight lang="php"> {{{ 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:
<syntaxhighlight lang="php">
...
{{{ 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:
<syntaxhighlight lang="php"> layout/columns1.php layout/columns2.php layout/columns3.php
You will need to add this callback to your custom layout file:
<syntaxhighlight lang="php"> <?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:
<syntaxhighlight lang="php">
...
<?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.
