Review main Merged

90054[BUGFIX] Avoid broken 'notify editors' in workspaces

Christian Kuhn CR +2 V +2 Normal +5 −129 updated 07/12/25, 20:03

Commit message

The workspaces notification system is quite complex to allow
fine grained selection and pre-selection of persons to notify
when records transition to other stages.

Both 'internal' stages (draft, publish, publish execute) and
custom stages have a checkbox to notifity 'Editors' on record
stage changes. The intention (which we found by reading the
code, there is no documentation abouth this one) is to find
and notify editors that were involved in the editing process,
but are not direct or group related members through one of the
plenty other fields. The solution is broken:

* The logic is based on lookups in sys_history per affected
  record, but looks only for the initial creator, not for anyone
  else who may have edited.
* The result of that lookup immediately gets lost in method
  getRecipientsOfStage() since that method does not iterate on
  the result set, but a different one. It looks as if that faulty
  behavior is the case since 'ever'. Users found this way are thus
  never rendered in the notification selection window and don't
  receive any notification.
* Even if it would work, that detail is questionable: A record
  may have been created years ago, and "current" users who should
  take care of stage changes are most likely part of some other
  group or workspace related notification field already ("owner",
  "member", "default recipient" or "responsible person"), and thus
  notified.
* The naming "Editors" of that toggle is so misleading that
  probably only very few people understand what it is supposed to
  do. There is also no reported issue about this toggle questioning
  its behavior.

The patch removes the entire thing: For 'internal' stages the
editor checkbox is gone. In custom stages we keep the checkbox
as 'unused' since removing it at position 3 would move the bitset
of position 4, which would be breaking. This is a limitation of
TCA type=check, and we will most likely create a v14 change that
will allow integrators to deal with this and similar scenarios.
Keeping a dummy value however allows us to backport this change
to v13 as well, which is why we decided for this path.

Review

  • Code review CR +2 Done
    • Christian Kuhn +2
    • Garvin Hicking +1
    • Anja Leichsenring +1
  • Verified V +2 Done
    • Christian Kuhn +2
    • Garvin Hicking +1
    • Anja Leichsenring +1
    • core-ci +1 CI

Issues 1

Files 9

Review log 913

  1. Christian Kuhn uploaded patch set 1 07/11/25, 12:52

  2. core-ci voted on patch set 1 V +1 07/11/25, 12:59 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/81612

  3. Christian Kuhn updated the commit message in patch set 2 V +1 07/11/25, 14:04

  4. core-ci voted on patch set 2 V +1 07/11/25, 14:11 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/81614

  5. Christian Kuhn updated the commit message in patch set 3 V +1 07/11/25, 16:35

  6. core-ci voted on patch set 3 V +1 07/11/25, 16:43 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/81617

  7. Anja Leichsenring voted on patch set 3 CR +1 V +1 07/12/25, 14:29

  8. Christian Kuhn rebased onto patch set 4 CR +1 V +1 07/12/25, 14:31

  9. core-ci voted on patch set 4 V +1 07/12/25, 14:39 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/81632

  10. Anja Leichsenring voted on patch set 4 CR +1 V +1 07/12/25, 14:41

  11. Garvin Hicking voted on patch set 4 CR +1 V +1 07/12/25, 18:28

  12. Christian Kuhn voted on patch set 4 CR +2 V +2 07/12/25, 20:03

  13. Christian Kuhn merged patch set 5 07/12/25, 20:03