#107828cache_tags is not validated in TCA
Description
If you set value of your cache_tags for page to value with space, you will break your page. I’m not sure if it’s intended, but throwing exception during misconfiguration in field is not really user friendly solution.
I would rather add validation or normalize that field, or at least give user some information that he is about to break frontend for that page, if he changes value of that field.
It’s problem at least on version v11 and v13, not tested on current main yet.
clipboard-202510241133-45vgh.png
Reviews 3
Files 1
History 36
-
Marcin Sągol commented <span data-processor="relativetime" data-value="2025-10-24T09:50:26+00:00" > 10/24/25, 09:50 </span>
So to make it more clear:- the cache_tags field expects as a valid value multiple tags separated by comma
- the cache tag can’t conaint space etc.
- this field is not validated on the backend side, to prevent user from using invalid tags
- when invalid tag is entered, it will break the page as an exeption will be thrown
-
Garvin Hicking changed category <span data-processor="relativetime" data-value="2025-10-24T09:52:56+00:00" > 10/24/25, 09:52 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 95470 status
NewUnder Review <span data-processor="relativetime" data-value="2026-08-28T08:55:21+00:00" > 08/28/26, 08:55 </span> -
Gerrit Code Review pushed patch set 1 for 14.3 to change 95516 <span data-processor="relativetime" data-value="2026-09-01T12:01:34+00:00" > 09/01/26, 12:01 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 95517 <span data-processor="relativetime" data-value="2026-09-01T12:01:45+00:00" > 09/01/26, 12:01 </span>
-
Georg Ringer commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-09-01T12:25:12+00:00" > 09/01/26, 12:25 </span>Applied in changeset commit:635c6957e85afc3b93cd8312a306bc4fbb980589.