Overriding templates

EXT:academic_persons_edit is using Fluid as template engine.

This documentation won't bring you all information about Fluid but only the most important things you need for using it. You can get more information in the section Fluid templates of the Sitepackage tutorial. A complete reference of Fluid ViewHelpers provided by TYPO3 can be found in the ViewHelper Reference

Change the templates using TypoScript constants

As any Extbase based extension, you can find the templates in the directory Resources/Private/.

If you want to change a template, copy the desired files to the directory where you store the templates.

We suggest that you use a sitepackage extension. Learn how to Create a sitepackage extension.

# TypoScript constants
plugin.tx_academicpersonsedit {
    view {
        templateRootPath = EXT:mysitepackage/Resources/Private/Extensions/myextension/Templates/
        partialRootPath = EXT:mysitepackage/Resources/Private/Extensions/myextension/Partials/
    }
}

Profile editing template

Profile editing renders from Resources/Private/Templates/Profile/Index.html and thirty-one partials below Resources/Private/Partials/Profile/. Four of them sit directly in that directory - the header, the status toast, the button templates and the prototypes - and the rest in four subdirectories: Field/ for the controls and the two action bars, Documents/ for the structured sections and their two editors, Image/ for the image card and the image editor, and Profile/ for the field sections. Any of them can be overridden on its own.

Two of them carry more than markup. Profile/Field/Control.html is the one place a form control is spelled - every field, of every section and of both editors, is that partial - and Profile/Prototypes.html holds the <template data-pe-proto> blocks the custom elements clone for everything they draw in the browser. When overriding while keeping the shipped JavaScript, preserve the form data attributes, the field class and the slot names of those blocks. The complete contract is documented in Profile editing.

Replacing an icon

The action icons of the profile editing frontend are addressed by identifier, not by file. They are registered in Configuration/Icons.php of EXT:academic_persons_edit as academic-persons-edit-add, -back, -clear, -delete, -edit, -help, -move-down, -move-up, -save, -sort-handle, -undo, -upload-image and -view.

To use different artwork, register the identifier again in the Configuration/Icons.php of the sitepackage with the own file - a later registration wins, and no template has to be overridden:

EXT:mysitepackage/Configuration/Icons.php

<?php

use FGTCLB\AcademicBase\Imaging\IconProvider\CurrentColorSvgIconProvider;

return [
    'academic-persons-edit-save' => [
        'provider' => CurrentColorSvgIconProvider::class,
        'source' => 'EXT:mysitepackage/Resources/Public/Icons/save.svg',
    ],
];

That provider inlines the file rather than rendering an <img>, so the glyph takes the colour of the button it sits in. A file registered with it carries a viewBox, draws its shapes in currentColor and has no id attribute - the markup is part of the document, possibly more than once.

The shipped files are Bootstrap Icons; their MIT licence ships beside them in Resources/Public/Icons/LICENSE-bootstrap-icons.txt.