---
title: "Breaking: #96149 - EXT:form EmailFinisher always uses FluidEmail"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-96149"
source: "Changelog/12.0/Breaking-96149-EXTformEmailFinisherAlwaysUsesFluidEmail.rst"
typo3-version: "12.0"
typo3-major: 12
type: "breaking"
issue: 96149
forge: "https://forge.typo3.org/issues/96149"
tags: ["YAML", "NotScanned", "ext:form"]
rendered: "2026-09-25T23:17:45+00:00"
---

# Breaking: #96149 - EXT:form EmailFinisher always uses FluidEmail {#breaking-96149}

See [forge#96149](https://forge.typo3.org/issues/96149)

## Description {#description}

In recent versions, the `EmailFinisher` of EXT:form allowed sending
emails with either `StandaloneView` or via `FluidEmail`, which
has been introduced in TYPO3 v10. The `StandaloneView` option has
therefore now been removed together with the `Html.html` and
`Plaintext.html` templates.

## Impact {#impact}

Since the EXT:form `EmailFinisher` is now always using `FluidEmail`
for sending emails, the `templatePathAndFilename` is not evaluated
anymore. For forms, which still define custom templates with this option,
a fallback kicks in, sending the emails with the default EXT:form
`FluidEmail` templates.

Also the `useFluidEmail` configuration option, previously used to
allow a smooth migration path is now obsolete and can safely be removed
from any form finisher configuration.

## Affected Installations {#affected-installations}

Installations, which have not yet switched to `FluidEmail`, while using
custom email templates, configured with `templatePathAndFilename`.

## Migration {#migration}

In case you use custom email templates, replace `templatePathAndFilename`
with the `templateName` and `templateRootPaths` options. Also
make sure, you have separate template files for the used formats, e.g.
`ContactForm.html` and `ContactForm.txt`.