Breaking: Adapted frontend editing Fluid files
Description
Version 2.4 changes Fluid templates and partials that
EXT: ships for its frontend editing plugin. They
are shipped files, not API, and an installation that overrides one of
them keeps its own copy and therefore does not receive the change.
This page lists the changes of 2.4 to those files. Most of them have an entry of their own, which describes the change and how to apply it to a copy:
- The contact record lists and
Templates/show hidden records and a show and hide toggle, see Breaking: Adapted frontend editing templates for contact record visibility.Contract/ Show. html Partials/reads the image metadata from the file and no longer requests WebP unconditionally, see Important: Adapted profile image partial and Important: Profile image keeps its own format where WebP is not allowed.Profile/ Show/ Image. html Partials/,Profile/ Properties/ Profile. html Partials/and the contract templates start the rich text editor, see Important: The profile forms now start the rich text editor.Profile/ Properties/ Contract. html Templates/loads the editor configuration from its new location, see Breaking: The editor configuration moved.Profile/ Edit. html - The partials below
Partials/and the templates of the six forms show the messages of a rejected form, see Important: Rejected forms show their messages.Profile/ Forms/ - Every template and partial translates with the extension name
Academic, see Important: Label overrides are read from the documented path.Persons Edit
The changes without an entry of their own follow.
Profile name without empty parts
The headers of the templates and Partials/
rendered the name of a profile as
{profile.,
so a profile without a title or a middle name got a leading or a double
space. They now leave out an empty title and an empty middle name together
with their space:
{f:if(condition: profile.title, then: '{profile.title} ')}{profile.firstName}{f:if(condition: profile.middleName, then: ' {profile.middleName}')} {profile.lastName}
The browser collapses the spaces of the old markup, so the visible name does not change.
Profile image copyright
Resources/Private/Partials/Profile/Show/Image.html
The partial rendered a copyright above the image:
<f:if condition="{image.properties.show_copyright} && {image.properties.copyright}">
<span class="copyright">© {image.properties.copyright}</span>
</f:if>
That block is removed. It has never rendered anything in any released
version, for two independent reasons: the view variable image is never
assigned (see Important: Adapted profile image partial), and show_ is not
a field of TYPO3. It exists in no system extension, in no extension this
package depends on or suggests, and nowhere in this extension except
that condition. The copyright field itself is real, but comes with the
system extension EXT:, which is not a dependency here.
Repairing the property paths would therefore not have produced a working copyright. It would have produced a second, differently broken condition. Rendering the copyright of a profile image is a feature, not a defect fix: it needs a decision about where the value comes from, a declared dependency on whatever provides it, and test coverage proving it renders.
Impact
Installations that override one of the adapted files keep the behaviour
of their own copy. For the two changes described on this page that is
harmless: an overridden Profile/ keeps its
copyright block, which renders nothing there either, and an overridden
header keeps its extra spaces.
The changes listed above with an entry of their own do change what a copy misses. Their entries name the consequences.
Affected Installations
All installations using EXT: that override one of
its templates or partials.
Migration
Re-apply the project specific overrides on top of the updated files, using the entries linked above for the changes they describe.