Environment
- Academi theme v5.2 (release 2026042900)
- Moodle 5.2.12
- Also reproduced on Moodle 4.5.12 with an earlier Academi build
Steps to reproduce
- Site administration → Front page → Front page settings
- Enable "Add custom content" and add content (tested with a linked image and an H5P accordion)
- Save, view Site Home as admin with editing ON → content displays
- Turn editing OFF → content disappears
- Log in as a student (non-editing) → content is not visible at all
Expected behavior
Custom content should display for all users regardless of editing mode.
Actual behavior
Custom content only renders while editing mode is on. It's empty/missing for non-editing admins and students alike.
Diagnostics already ruled out
- Not a permissions/capability issue (fails for admin-with-editing-off too, not just students)
- Switching theme to Boost with no other changes → content displays correctly for students
- Switching back to Academi → issue returns
Regression, not a persistent bug
We have an older Moodle server running Moodle 4.5.0 with Academi v4.5 – 2025010400, where custom content on the home page works fine with no issues. This suggests something changed between that build and the versions above (v4.5-2025010400 → the builds tested on 4.5.12 and 5.2.12) that broke this rendering path.
Likely a template conditional tied to editing mode that only renders the custom content region inside the "editing on" branch — possibly introduced in a change between those releases.
Environment
Steps to reproduce
Expected behavior
Custom content should display for all users regardless of editing mode.
Actual behavior
Custom content only renders while editing mode is on. It's empty/missing for non-editing admins and students alike.
Diagnostics already ruled out
Regression, not a persistent bug
We have an older Moodle server running Moodle 4.5.0 with Academi v4.5 – 2025010400, where custom content on the home page works fine with no issues. This suggests something changed between that build and the versions above (v4.5-2025010400 → the builds tested on 4.5.12 and 5.2.12) that broke this rendering path.
Likely a template conditional tied to editing mode that only renders the custom content region inside the "editing on" branch — possibly introduced in a change between those releases.