---
title: "Deprecation: #95318 - TypoScript parseFunc.sword"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:deprecation-95318"
source: "Changelog/11.5/Deprecation-95318-TypoScriptParseFuncsword.rst"
typo3-version: "11.5"
typo3-major: 11
type: "deprecation"
issue: 95318
forge: "https://forge.typo3.org/issues/95318"
tags: ["Frontend", "TypoScript", "NotScanned", "ext:frontend"]
rendered: "2026-09-20T18:31:11+00:00"
---

# Deprecation: #95318 - TypoScript parseFunc.sword {#deprecation-95318}

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

## Description {#description}

The TypoScript option `parseFunc.sword` allows to wrap
search words (such as defined via GET parameter `sword_list%5B%5D=MySearchText`)
in a special wrap when `no_cache=1` is set. This functionality has been marked as
deprecated as this feature only works in non_cached environments, which
is not a recommended solution by TYPO3.

Since this behavior is enabled by default, it is highly recommended to avoid
this in general, which can be achieved by disabling the `no_cache=1` GET parameter
in `DefaultConfiguration.php`.

Also, such an option within `parseFunc` does not cover all cases to highlight
a search word, such as in headlines or HTML content which is not rendered
via `parseFunc`.

## Impact {#impact}

Websites called via `https://example.com/?no_cache=1&sword_list%5B%5D=MySearchText`
and a custom sword wrap will trigger a PHP `E_USER_DEPRECATED` error.

As this feature is seldom used and only configured with indexed
search as desired functionality, deprecations are only triggered
when explicitly configured.

In addition, this feature only works if `disableNoCacheParameter`
is disabled or `config.no_cache = 1` is explicitly set via TypoScript
which is also not recommended in production.

## Affected Installations {#affected-installations}

TYPO3 installations actively using the GET argument `sword_list` and have
`no_cache` as allowed GET argument enabled, usually in cases where indexed
search is in use.

## Migration {#migration}

It is recommended to implement this functionality on the client-side via
JavaScript as a custom solution, when this feature is needed.

Setting `lib.parseFunc.sword` to an empty string will actively
disable the functionality and not trigger a PHP `E_USER_DEPRECATED` error as well.

Setting `lib.parseFunc.sword = <span class="ce-sword">|</span>`
will also not trigger a PHP `E_USER_DEPRECATED` error for TYPO3 v11.