"body" field for "Service Sub-landing page" content type disabled

[bisd]

Creating a new instance of the above content type results in the headline showing but not the body. So the user has to go to the “Manage display” page for that content type and manually enable the disabled by default "body" field.

[markconroy]

Editing the title to remove reference to the localgov_base theme, as this is purely a site builder/config issue, not a theme issue.

[MichaelDCR]

This is in the wrong Repo

[bisd]

Thank you MichaelDCR would you like me to move it to a different repo?

[keelanfh]

I think this is confusing on a few content types:

• service landing page
• service sub-landing page
• guide overview

If my understanding is correct, the 'body' field appears on all these content types, but it doesn't show up in the actual site. The reason that the body field is there is so that a truncated version of the body (or the summary, if present) is used as teaser text on the parent page of these pages. So it's called 'body' and supports rich text styling, but never actually appears as such.

We could label this field as 'teaser text' and reduce to one field (rather than having a summary and body field) - example of how we do this in our existing CMS below. But this would cause problems for councils that have changed from the default configuration to actually show the body text on their site.

[markconroy]

I find the body field quite handy on this content types, so make it display on the page, rather than using it as "just" a teaser field.

[keelanfh]

Yeah, it's a bit of a tricky one - I can see that it needs to be there for councils that have the field visible, but I think in the default setup it can be confusing...

[finnlewis]

One for the forthcoming product group /proudct team to discuss?