---
title: "Breaking: Project pages render inside the site layout"
manual: "Academic Projects"
version: "main"
permalink: "https://docs.typo3.org/permalink/fgtclb/academic-projects:breaking-project-page-renders-inside-the-site-layout@main"
source: "Changelog/3.0/Breaking-ProjectPageRendersInsideTheSiteLayout.rst"
rendered: "2026-10-12T23:12:54+00:00"
---

# Breaking: Project pages render inside the site layout {#breaking-project-page-renders-inside-the-site-layout}

## Description {#description}

The page template of the page type **Academic project**,
`Resources/Private/Pages/AcademicProject.html`, declared no Fluid layout.
On a site package that renders its header, navigation and footer through a page
layout, as [`bk2k/bootstrap-package`](https://packagist.org/packages/bk2k/bootstrap-package) does, a project page therefore
rendered without any of them. The template rendered every part inline, so a
project that wanted to change one of them had to replace the whole template.
And its paths were registered at the key `100` of the page object, which on a
`PAGEVIEW` site package replaced the package's own paths of that key
on project pages - its layouts and partials were gone there.

From 3.0 on:

-   The template renders the section `Main` of the layout named by the
    new setting `plugin.tx_academicprojects.page.layout`, `Default`
    by default. A site package without a layout `Default` gets a fallback
    layout of this extension, which renders the section alone.
-   The section renders five partials: `Project/Page/Header.html`,
    `Project/Page/Media.html`, `Project/Page/Categories.html`,
    `Project/Page/Facts.html` and `Project/Page/Content.html`.
-   The header renders the subtitle of the page between the title and the
    short description, in an element with the class `ace-subtitle`. The
    element around title and short description is a
    `<header class="ace-header">`.
-   Without a project title, the heading shows the title of the page on a
    `PAGEVIEW` page object as well. It stayed empty there, because
    the template read the page from `{data}`, which only a
    `FLUIDTEMPLATE` page object assigns.
-   `paths`, `templateRootPaths` and
    `partialRootPaths` of the page object use the key `50` instead of
    `100` on project pages. `layoutRootPaths.100`, which named a
    directory that does not exist, is removed.

The setting is a site setting of the aggregate set `fgtclb/academic-projects`
and a constant for the static templates, see [The layout of a project page](https://docs.typo3.org/permalink/fgtclb/academic-projects:project-page-layout@main). The
program page made the same move in 3.0, so the three academic page types
follow one pattern.

## Impact {#impact}

-   A project page on a site package with a layout `Default` renders
    inside it: with the header, navigation and footer of the site.
-   A site package whose layout `Default` renders no section
    `Main` renders the project page without its content.
-   A site package without a layout `Default` renders the project page
    as before, without the frame of the site. A layout named by the setting
    that the site package does not have fails the page.
-   A project page with a subtitle shows it below the title.
-   A project page without a project title shows the page title as its heading
    on a `PAGEVIEW` page object as well.
-   A `PAGEVIEW` site package that assigns a variable
    `data` of its own no longer breaks project pages. The page
    record now comes from `{page}` first, in the template and in the
    data processor.
-   A path a project registered at a key between `50` and `100` now wins over
    the extension, where it lost before. A site package path at `100` is no
    longer replaced on project pages.
-   A project that set, read or cleared `page.10.paths.100`,
    `templateRootPaths.100`, `partialRootPaths.100` or
    `layoutRootPaths.100` inside the condition on the project page
    type reaches nothing of this extension there any more.

## Affected Installations {#affected-installations}

Every installation that renders project pages on a site package with page
layouts, and every installation that styles the markup of the project page or
changes its paths at the key `100`.

An override of the whole `AcademicProject.html` keeps rendering, without a
layout, as long as it does not render `styles.content.getContent`,
see [Breaking: Project pages render their content without a global path](https://docs.typo3.org/permalink/fgtclb/academic-projects:breaking-projects-content-load-set-removed@main).

## Migration {#migration}

-   A site package whose layout for project pages has another name sets
    `plugin.tx_academicprojects.page.layout` to it. One whose
    layout renders another section than `Main` overrides
    `Pages/AcademicProject.html`.
-   A project that overrides `AcademicProject.html` to change one part
    moves that change to the matching partial below
    `Project/Page/` and removes the template override.
-   A project that added a subtitle of its own renders the page field
    **Subtitle** instead, or overrides `Project/Page/Header.html`.
-   Move a path set at the key `100` inside the project page condition to
    `50`, or to a key above it to win over the extension.