Important: Category type icons come from the frontend icon registry
Description
The project page and the project card of the project list show the icon of
each category type of a project. The partials
Partials/ and
Partials/ rendered it with core:, from the icon
registry of the TYPO3 backend. They now render it with the ab:
ViewHelper of academic_base, from its frontend icon registry, with
the arguments they had.
The identifiers stay category_, and so does the
rendered markup, the inlined drawing in its wrapper
<span class="t3js-.
category_types registers every category type icon in both
registries, so the backend and the frontend show the same drawing unless one of
the cases below applies. The drawings are new in 3.0, the cooperation and the
project department draw shared icons of academic_base, and the page
type and the content elements show icons of this extension instead of a core
icon, see Breaking: Project icons are replaced and follow the colour scheme.
One case changes on purpose: a category type declared without an icon file
made the partials fail with exception 1440754980 of the bitmap icon provider of
TYPO3, which the backend icon registry picks for an empty source. It now shows
TYPO3's not-found placeholder.
What the frontend shows can now differ from the backend:
- A type that declares a
frontendinIcon Configuration/shows that file in the frontend and itsCategory Types. yaml iconin the backend. - A site package replaces the icon of a type for the frontend only by
registering its identifier, for example
category_, in its owntypes. projects. competence_ field Configuration/.Frontend Icons. php
An override of one of the partials that still renders the icons with
core: keeps working and keeps showing the backend icon of each type. It
misses a frontend and a frontend replacement until it switches: replace
<core: with <ab:, keep every argument, and declare
xmlns: in the
<html>
tag of the partial.