---
title: "Feature: The plugins can render the content element header"
manual: "Academic Partners"
version: "main"
permalink: "https://docs.typo3.org/permalink/fgtclb/academic-partners:feature-1790440962@main"
source: "Changelog/3.0/Feature-PluginsCanRenderContentElementHeader.rst"
rendered: "2026-10-26T19:20:19+00:00"
---

# Feature: The plugins can render the content element header {#feature-1790440962}

## Description {#description}

The header and the subheader an editor enters on a **Partner List**,
**Partner Map**, **Partners Linked** or
**Partner Logo Teaser** 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:

**TypoScript constants**

```typoscript
plugin.tx_academicpartners.renderContentElementHeader = 1
```

On a site that uses the site set, that is the site setting **Render the
content element header in the plugins** of `fgtclb/academic-partners`. 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.defaultHeaderType`, mapped from the constant
`styles.content.defaultHeaderType`, 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/All.html` of the site package wins over it, and the extension does
not require **EXT:fluid_styled_content**. See
[The header of the content elements](https://docs.typo3.org/permalink/fgtclb/academic-partners:configuration-content-element-header@main).

On TYPO3 v14 the header partial renders the header through the `record` view
variable, so the plugin views now carry `record` next to `data`: the content
element as a record object.

## Impact {#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 copied a template only to add the header can switch it on and
drop the copy.