---
title: "Breaking: #107438 - Default parseFunc configuration for Fluid Styled Content"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-107438-1736592000"
source: "Changelog/14.0/Breaking-107438-DefaultParseFuncConfigurationForFluidStyledContentRemoved.rst"
typo3-version: "14.0"
typo3-major: 14
type: "breaking"
issue: 107438
forge: "https://forge.typo3.org/issues/107438"
tags: ["TypoScript", "ext:fluid_styled_content", "ext:frontend", "NotScanned"]
rendered: "2026-10-08T19:59:57+00:00"
---

# Breaking: #107438 - Default parseFunc configuration for Fluid Styled Content {#breaking-107438-1736592000}

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

## Description {#description}

Since TYPO3 v13, the basic `lib.parseFunc` and
`lib.parseFunc_RTE` configurations are always available through
[`EXT:frontend/ext_localconf.php`](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/FileStructure/ExtLocalconf.html#file-extension-ext-localconf-php).

The default parseFunc configuration previously provided by
EXT:fluid_styled_content has been removed to avoid duplicated and outdated
settings. This unifies the parseFunc behavior between EXT:frontend and
EXT:fluid_styled_content.

The `allowTags` syntax is no longer set by default, as HTML
sanitization has been handled properly by the HTML Sanitizer for some time.
All HTML tags are now allowed by default in frontend output, while the
HTML Sanitizer controls which tags and attributes are ultimately permitted.

Note that the `allowTags` directive itself has **not** been
removed. It can still be set to restrict frontend output where desired.

The conceptual approach is:

-   The backend (RTE and its HTML parser/processing) already cleans unwanted
    content and controls what is stored in the database.
-   The frontend output (parseFunc) should only add additional restrictions
    through `allowTags` when content comes from external or
    untrusted sources (for example, custom Extbase output).

## Impact {#impact}

Custom TypoScript configurations using `allowTags` syntax may no
longer work as expected. Specifically:

-   `allowTags := addToList(wbr)` no longer appends `wbr`.
    Instead, it limits allowed tags to only `wbr`.
-   Default CSS classes on HTML elements (for example
    `<table class="contenttable">`) are no longer automatically added by
    the parseFunc configuration.
-   The parseFunc configuration in EXT:fluid_styled_content no longer
    provides custom link-handling options such as `extTarget` and `keep`.

## Affected installations {#affected-installations}

TYPO3 installations that use:

-   Custom TypoScript configurations relying on prior default
    `allowTags` behavior.
-   Extensions or sites depending on the specific parseFunc configuration
    previously provided by EXT:fluid_styled_content.
-   Configurations expecting automatic CSS class additions to HTML elements.
-   Sites relying on the old external link-handling behavior from the
    Fluid Styled Content parseFunc.

## Migration {#migration}

If you need to allow specific HTML tags, explicitly configure
`allowTags` instead of extending a former default.

**Before (no longer works):**

```typoscript
lib.parseFunc_RTE.allowTags := addToList(wbr)
```

**After:**

```typoscript
lib.parseFunc_RTE.allowTags = b,span,i,em,wbr,...
```

For custom CSS classes on HTML elements, use custom CSS or add them through
Fluid templates or TypoScript processing instead.

If you require the previous link-handling behavior, configure it explicitly:

```typoscript
lib.parseFunc_RTE {
    makelinks {
        http {
            extTarget = _blank
            keep = path
        }
    }
}
```