Feature: The contact list can render the content element header
Description
The header and the subheader an editor enters on a Contacts for this page content element are rendered by the content element layout of the site, like those of any other content element. The layouts of EXT:fluid_styled_content and of the bootstrap package do that. A site package whose layout leaves the header out, because its element templates render it, showed no header for these content elements, and projects copied the templates to add it.
A site whose layout renders no header now switches the header on:
plugin.tx_academiccontacts4pages.renderContentElementHeader = 1
The extension declares no site settings, so a site that uses the site set sets
the constant in config/. It is off by
default.
Switched on, the templates render the header partial of
EXT:fluid_styled_content above their output, for every header layout
except Hidden. The plugin settings carry
settings., mapped from the constant
styles., so the header layout
Default renders a heading. The partial path of
EXT:fluid_styled_content is added below every other one, so a
Header/ of the site package wins over it, and the extension does
not require EXT:fluid_styled_content. See
The header of the content elements.
Impact
Nothing renders differently until a site switches the header on. A site whose layout renders the header leaves it off: switched on, the header appears twice. A project that replaced the list template only to render the header, as Important: The plugin assigns a record view variable describes, can switch it on and drop the copy.