Issue Bug Closed

#109876Error "is not a valid tag for a cache entry" after 13.4.30 maintenance update

Mathis Krüper 05/26/26, 15:32 updated 08/11/26, 08:50

Description

Hello,
Today I installed the 13.4.30 maintenance release on our TYPO3 instance, which has several subdomains.
After the update, I received the following error on the subdomains (the main domain works perfectly):

Fatal error: Uncaught InvalidArgumentException: “site_awm.stadt-muenster.de” is not a valid tag for a cache entry. in /app/vendor/typo3/cms-core/Classes/Cache/Frontend/VariableFrontend.php on line 46

I suspect this has something to do with the following commit from the maintenance release:
8af66a56dd1 [TASK] Include current site in cache tag collection

Are there any suggestions or tips on how to resolve or work around this issue?
There were no such issues with version 13.4.29.

Best regards

Reviews 3

History 69

  1. Oliver Hader commented and changed status New Accepted Is Regression 1 <span data-processor="relativetime" data-value="2026-05-26T16:17:20+00:00" > 05/26/26, 16:17 </span>

    Confirmed, due to PATTERN_TAG = '/^[a-zA-Z0-9_%\\-&]{1,250}$/'; (which does not allow to use the site’s domain name)
    Introduced with https://review.typo3.org/c/Packages/TYPO3.CMS/+/94024

  2. Garvin Hicking commented <span data-processor="relativetime" data-value="2026-05-26T16:39:09+00:00" > 05/26/26, 16:39 </span>

    A workaround could be to rename your site identifier from “awm.stadt-muenster.de” to “awm-stadt-muenster” (not having dots). If you access your site identifier in some API you’d have to use the new id there too (e.g. for CLI context when creating a Site instance).

    The fix for this will not be hard, but a new release needs discussion.

  3. Gerrit Code Review pushed patch set 1 for main to change 94161 status Accepted Under Review <span data-processor="relativetime" data-value="2026-05-26T17:22:42+00:00" > 05/26/26, 17:22 </span>

  4. Christian Kuhn commented <span data-processor="relativetime" data-value="2026-06-09T23:05:32+00:00" > 06/09/26, 23:05 </span>

    this has been fixed by reverting the regressing patch with #109876