Issue Bug Closed

#107269All redirects get marked as having errors despite integrity_status is showed as no_conflict

Christian Osswald 08/12/25, 14:18 updated 08/11/26, 08:46

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

History 817

  1. Markus Klein commented <span data-processor="relativetime" data-value="2026-06-11T19:34:48+00:00" > 06/11/26, 19:34 </span>

    I think v13 needs a backport of #108785.
    Then the default value is correctly set during upgrades.

  2. Christian Buelter commented and changed status Under Review Resolved done 0 % 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.

  3. Gerrit Code Review pushed patch set 3 for 13.4 to change 95000 status Resolved Under Review <span data-processor="relativetime" data-value="2026-07-30T07:47:50+00:00" > 07/30/26, 07:47 </span>

  4. Christian Buelter commented and changed status Under Review Resolved <span data-processor="relativetime" data-value="2026-07-30T08:10:12+00:00" > 07/30/26, 08:10 </span>

    Applied in changeset commit:4f094661a2810bf6d78e871d53576b7727aacf65.