#107269All redirects get marked as having errors despite integrity_status is showed as no_conflict
Description
In my database nearly all redirects have an empty string as integrity_status value. I guess this comes due to not recreating the sys_redirect table after the TCA default for sys_redirect.integrity_status was set to RedirectConflict::NO_CONFLICT.
This leads to the behavior, that in the Overview template the danger class is set.
EXT:cms-redirects/Resources/Private/Templates/Management/Overview.html
line 135 class=”{f:if(condition: ‘{redirect.integrity_status} !== {defaultIntegrityStatus}’, then: ‘danger’)}”
In my opinion, either there should be an additional check for empty string in the template or we should set the integrity_status actively to RedirectConflict::NO_CONFLICT. This could be possible with the CheckIntegrityCommand.
Reviews 3
Related issues 1
History 817
-
Garvin Hicking changed category <span data-processor="relativetime" data-value="2025-08-12T21:06:05+00:00" > 08/12/25, 21:06 </span>
-
Stefan Bürk changed assigned to Stefan Bürk <span data-processor="relativetime" data-value="2025-08-12T21:14:35+00:00" > 08/12/25, 21:14 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 92431 status
NewUnder Review <span data-processor="relativetime" data-value="2026-01-20T17:42:51+00:00" > 01/20/26, 17:42 </span> -
Gerrit Code Review pushed patch set 2 for main to change 92431 <span data-processor="relativetime" data-value="2026-01-20T19:26:55+00:00" > 01/20/26, 19:26 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 92431 <span data-processor="relativetime" data-value="2026-02-03T14:30:54+00:00" > 02/03/26, 14:30 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 92431 <span data-processor="relativetime" data-value="2026-04-22T07:15:46+00:00" > 04/22/26, 07:15 </span>
-
Markus Klein changed Related to #108785 <span data-processor="relativetime" data-value="2026-06-11T19:34:10+00:00" > 06/11/26, 19:34 </span>
-
Torben Hansen commented <span data-processor="relativetime" data-value="2026-07-06T11:21:05+00:00" > 07/06/26, 11:21 </span>
Agree, this needs a backport to v13.
-
Gerrit Code Review pushed patch set 5 for main to change 92431 <span data-processor="relativetime" data-value="2026-07-29T13:29:15+00:00" > 07/29/26, 13:29 </span>
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 94999 <span data-processor="relativetime" data-value="2026-07-29T16:13:05+00:00" > 07/29/26, 16:13 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 95000 <span data-processor="relativetime" data-value="2026-07-29T16:13:28+00:00" > 07/29/26, 16:13 </span>
-
Gerrit Code Review pushed patch set 2 for 13.4 to change 95000 <span data-processor="relativetime" data-value="2026-07-29T16:13:55+00:00" > 07/29/26, 16:13 </span>
-
Christian Buelter commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-07-29T16:15:09+00:00" > 07/29/26, 16:15 </span>Applied in changeset commit:43c2fd95997b0170a8f3ddde6a145ff57dc0cd83.
-
Gerrit Code Review pushed patch set 3 for 13.4 to change 95000 status
ResolvedUnder Review <span data-processor="relativetime" data-value="2026-07-30T07:47:50+00:00" > 07/30/26, 07:47 </span> -
Christian Buelter commented and changed status
Under ReviewResolved <span data-processor="relativetime" data-value="2026-07-30T08:10:12+00:00" > 07/30/26, 08:10 </span>Applied in changeset commit:4f094661a2810bf6d78e871d53576b7727aacf65.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-08-11T08:46:40+00:00" > 08/11/26, 08:46 </span>
I think v13 needs a backport of #108785.
Then the default value is correctly set during upgrades.