You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Study Intro (studyintro) is available as a Layout Editor element for both the Messages list and Detail views. However, the full sermon body text (studytext) is only rendered via a hardcoded block in site/tmpl/cwmsermon/default_main.php — it is not exposed as a configurable element in the Layout Editor.
This means template administrators have no control over:
Whether the full body text appears on the detail page
Where in the layout it is positioned (row/column)
What CSS class or link type is applied to it
Whether it appears at all (e.g. for audio-only sermon sites that have no written content)
What would change
Adding studytext to the Layout Editor would require:
New fields in template.xml — dstudytext prefixed fields (row, col, colspan, element, custom, linktype) in the details fieldset, following the same pattern as dstudyintro
Layout Editor JS — Register studytext as a draggable element in the details context in layout-editor.es6.js
Rendering in Cwmlisting.php — Add rendering logic for the studytext element alongside the existing studyintro rendering
Remove hardcoded output — The current echo $this->item->studytext in default_main.php would need to be replaced with the Layout Editor-driven rendering
Concerns
Breaking change: Existing templates that rely on the hardcoded studytext output would need migration. After this change, studytext would only appear if explicitly added to the detail layout.
Content length: studytext can be very long (full sermon transcripts). Unlike other Layout Editor elements that are short labels/links, this is potentially pages of HTML content. The Layout Editor UI may need special handling.
Performance: Rendering large HTML blocks through the element pipeline vs. direct output could have performance implications.
Migration path: Existing templates would need a migration script to auto-add dstudytext to row 6 (or similar) so that upgrading doesn’t silently remove sermon body text from detail pages.
Questions for discussion
Should studytext be a Layout Editor element, or should it remain a fixed block that always renders below the layout elements?
If added to the Layout Editor, should it be detail view only, or also available in the messages list view (truncated)?
Is there a preferred migration strategy — auto-add to existing templates, or require manual configuration?
Are there other content fields that should also be exposed (e.g. secondary references, topics list)?
Feedback welcome before we commit to an implementation approach.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Background
Currently the Study Intro (
studyintro) is available as a Layout Editor element for both the Messages list and Detail views. However, the full sermon body text (studytext) is only rendered via a hardcoded block insite/tmpl/cwmsermon/default_main.php— it is not exposed as a configurable element in the Layout Editor.This means template administrators have no control over:
What would change
Adding
studytextto the Layout Editor would require:template.xml—dstudytextprefixed fields (row, col, colspan, element, custom, linktype) in the details fieldset, following the same pattern asdstudyintrostudytextas a draggable element in the details context inlayout-editor.es6.jsCwmlisting.php— Add rendering logic for thestudytextelement alongside the existingstudyintrorenderingecho $this->item->studytextindefault_main.phpwould need to be replaced with the Layout Editor-driven renderingConcerns
studytextoutput would need migration. After this change,studytextwould only appear if explicitly added to the detail layout.studytextcan be very long (full sermon transcripts). Unlike other Layout Editor elements that are short labels/links, this is potentially pages of HTML content. The Layout Editor UI may need special handling.dstudytextto row 6 (or similar) so that upgrading doesn’t silently remove sermon body text from detail pages.Questions for discussion
studytextbe a Layout Editor element, or should it remain a fixed block that always renders below the layout elements?Feedback welcome before we commit to an implementation approach.
Beta Was this translation helpful? Give feedback.
All reactions