---
title: "Breaking: The profile editing plugin ships no stylesheet"
manual: "Academic Profiles Edit"
version: "main"
permalink: "https://docs.typo3.org/permalink/fgtclb/academic-persons-edit:breaking-profile-editing-ships-no-stylesheet@main"
source: "Changelog/3.0/Breaking-ProfileEditingShipsNoStylesheet.rst"
rendered: "2026-10-17T08:48:06+00:00"
---

# Breaking: The profile editing plugin ships no stylesheet {#breaking-profile-editing-ships-no-stylesheet}

## Description {#description}

The profile editing plugin no longer brings a stylesheet. The file
`EXT:academic_persons_edit/Resources/Public/Css/frontend/profile-editing.css`
and its source are removed, and neither `Templates/Profile/List.html` nor
`Templates/Profile/Index.html` registers it any more. The markup carries
the Bootstrap 5 classes and the speaking `ace-*` classes, and the site
package styles it.

The stylesheet came with the profile editor of 3.0, and no release of version 2
shipped it. Changelog entries of 3.0 and the manual of the editor that speak of
the stylesheet of the editor describe the one this entry removes.

The rules are kept as an example in the mono repository the extension is
developed in: the stylesheet of its development instances,
[\_academic-persons-edit.scss of EXT:academics_dev_site](https://github.com/fgtclb/academic-extensions/blob/main/packages-dev/dev-site/Resources/Private/Scss/frontend/_academic-persons-edit.scss),
which is never shipped with an extension.

## Impact {#impact}

The editor renders with Bootstrap and the theme of the site alone. Most of what
the removed file held is appearance, but several parts of the editor do not
work without its rules:

-   **The image cropper is not usable.** TYPO3 delivers the CropperJS module the
    image editor imports to the frontend, and its stylesheet only inside the
    backend. Without rules for the widget CropperJS builds, the cropper renders
    as an invisible stack of elements and nothing can be dragged.
-   **Regions the editor hides stay visible.** The editor hides the image
    editor, the contact editors, empty field messages and action groups with
    the `hidden` attribute. Bootstrap's display utilities on the same
    elements outrank Bootstrap's own rule for the attribute, so the delete
    actions of the image editor, for example, stay on screen.
-   The custom elements of the editor are laid out as inline boxes, because an
    unknown element is `display: inline`. A flex or grid parent of the
    theme then takes the wrong element as its item.
-   The collapse of the document editor and of the image editor, and the drag
    states of a sortable list, have no visible effect: the editor only writes
    the classes.

## Affected Installations {#affected-installations}

Every installation that renders the profile editing plugin and has no
stylesheet of its own for it. Installations whose template override registers
`Css/frontend/profile-editing.css` by path.

## Migration {#migration}

1.  Style the editor in the site package. Copy the rules of the example above
    into the stylesheet of the site and adapt them to the theme. Keep at least
    the cropper rules, the rule for `[hidden]` and the `display` of
    the custom elements, which the parts listed under *Impact* need to work.
1.  An overridden `Templates/Profile/List.html` or
    `Templates/Profile/Index.html` that registers
    `Css/frontend/profile-editing.css` drops that line, the file does
    not exist any more.