TYPO3 Core

Update : the implementation in the patch is a little different than described here: We create an additional status if checkintegrity was not run or is outdated. The status which shows ok or redirects is still displayed.

Ideally the "reports" checks if checkintegrity was run lately (e.g. within last 24 hours) and

• if checkintegrity was run and no conflicts: OK
• no redirects exist: OK
• if checkintegrity was not run (lately) and no conflicts (known): WARNING or INFO, e.g. "there are no known redirect conflicts, please run checkintegrity"
• if there are conflicts: WARNING (as before)

Reproduce¶

1. Create conflicts (e.g. rename slug of page twice)
2. confirm conflict by loading the page and check TYPO3 log (in case of redirect to self there will be something like " Redirect /styleguide-demo-1/test/redrects points to itself! Aborting" in log
3. look in report: will show OK. No indication that this is incorrect or something needs to be done.
4. confirm checkintegrity finds something (will show 1 conflict):

 php typo3/sysext/core/bin/typo3 redirects:checkintegrity

I expect a WARNING instead of OK status in report if there are conflicts and checkintegrity was never used or not used recently.

Screenshots (current core version)¶

Status: "Ok" (blissfully unaware of pending doom)

Status: after running checkintegrity

also, the text is weird, but that's another issue.

Screenshot (implementation, see patch)¶

This is current version in patch, not in core!: