Important: Category type icons come from the frontend icon registry
Description
The partner page, the partner card of the partner list, the partnerships list
and the partnerships teaser show the icon of each category type of a partner.
The partials Partials/,
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 collaboration type
draws the shared partnership icon of academic_base, and the other
icons of this extension are renamed, see
Breaking: Icons are renamed 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. partners. region 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.