Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGES.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ Changes

### Unreleased

* 2025-10-24 - Bugfix: Site support form success message was shown below blocks or advert tiles on frontpage, resolves #488
* 2025-10-23 - Feature: Add a type for smart menu item to use mailto links, resolves #702

### v5.0-r11
Expand Down
2 changes: 1 addition & 1 deletion templates/theme_boost/drawers.mustache
Original file line number Diff line number Diff line change
Expand Up @@ -199,6 +199,7 @@
{{> core/moremenu}}
</div>
{{/secondarymoremenu}}
{{{ output.course_content_header }}}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am afraid that we can't move that function call that easily. The course_content_header() outputs the page notifications, but it also outputs course content which should not be moved on the page.

My gut feeling is that we could move forward by overwriting the course_content_header() function in Boost Union's core renderer class and by splitting it into two parts, the first one which just shows the notifications and the second one which just shows the course content. Both functions could then be called here in Mustache individually.

We have done something like that before with the standard_end_of_body_html_endtoken() and standard_end_of_body_html_additionalhtmlfooter() function.

Do you think you could proceed into this direction?

{{#regions.contentupper.hasblocks}}
<section id="theme-block-region-content-upper" class="theme-block-region" aria-label="{{#str}}blocks{{/str}}">
{{{ regions.contentupper.addblockbutton }}}
Expand All @@ -217,7 +218,6 @@
{{#hasregionmainsettingsmenu}}
<div class="region_main_settings_menu_proxy"></div>
{{/hasregionmainsettingsmenu}}
{{{ output.course_content_header }}}
{{#headercontent}}
{{> core/activity_header }}
{{/headercontent}}
Expand Down
19 changes: 19 additions & 0 deletions tests/behat/theme_boost_union_feelsettings_blocks.feature
Original file line number Diff line number Diff line change
Expand Up @@ -486,3 +486,22 @@ Feature: Configuring the theme_boost_union plugin for the "Blocks" tab on the "F
| setting | shouldcontain |
| yes | should contain |
| no | should not contain |

@javascript
Scenario: Support form success notification is shown before content-upper blocks on site home
Given the following config values are set as admin:
| config | value | plugin |
| defaulthomepage | Home | |
| enableaccessibilitysupport | yes | theme_boost_union |
| blockregionsforfrontpage | content-upper | theme_boost_union |
And the following "blocks" exist:
| blockname | contextlevel | reference | pagetypepattern | defaultregion |
| online_users | Course | Acceptance test site | site-index | content-upper |
When I log in as "admin"
And I am on site homepage
And I should see "Online users" in the "#theme-block-region-content-upper" "css_element"
And I am on accessibilitysupport page
And I set the field "Message" to "Frontpage notification order test"
And I click on "Submit" "button"
And I wait until the page is ready
Then "Your accessibility support request was sent" "text" should appear before ".block_online_users" "css_element"