---
title: "Important: The job plugins leave the content element header to the layout"
manual: "Academic Jobs"
version: "main"
source: "Changelog/2.4/Important-JobPluginsLeaveTheHeaderToTheLayout.rst"
rendered: "2026-09-27T01:55:48+00:00"
---

# Important: The job plugins leave the content element header to the layout {#important-1790323400}

## Description {#description}

A **Jobs List**, **Jobs Detail** or **Jobs New**
content element renders through the content element layout of the site, like
any other content element. The layouts of **EXT:fluid_styled_content**
and of the bootstrap package render the header and the subheader an editor
enters, and the templates of the three plugins rendered them a second time:

```html
<f:render partial="Header/All" arguments="{_all}" />
```

With an explicit header layout the header and the subheader appeared twice.
With the header layout **Default** the plugin left an empty
`<header></header>` element behind, because the header partial takes the
heading level for that layout from a setting the plugin settings did not carry.

The templates now render the header only when the site switches it on:

**TypoScript constants**

```typoscript
plugin.tx_academicjobs.renderContentElementHeader = 1
```

The same is the site setting **Render the content element header in
the plugins** of the set `fgtclb/academic-jobs`. It is off by default.

The plugin settings now also carry `settings.defaultHeaderType`,
mapped from the constant `styles.content.defaultHeaderType` of
**EXT:fluid_styled_content**, so with the switch on the header layout
**Default** renders a heading. See
[The header of the content elements](../../Configuration/General/Index.html#configuration-general-content-element-header).

## Impact {#impact}

On a site whose content element layout renders the header, the header of the
three content elements appears once, and the markup of the plugins no longer
contains a `<header>` element.

## Affected Installations {#affected-installations}

Installations whose content element layout renders **no** header - a site
package that renders the header in its element templates instead - lose the
header of the job content elements. Switch
`renderContentElementHeader` on for such a site.

Projects that copied `Job/List.html`, `Job/Show.html` or
`Job/New.html` keep rendering the header in their copy. On a site whose
layout renders the header, drop the `<f:render partial="Header/All" … />`
line from the copy; on any other site, keep it or wrap it in the same
condition as the shipped templates:

```html
<f:if condition="{settings.renderContentElementHeader}">
    <f:render partial="Header/All" arguments="{_all}" />
</f:if>
```