Review main Merged

94234[BUGFIX] Extbase must ignore enable fields in Backend

Markus Klein CR +2 V +2 Easy +25 −0 updated 07/17/26, 16:28

Commit message

Core v13 removed a critical feature for Extbase persistence layer
usage in backend: "ignoreAllEnableFieldsInBe"

This central configuration was required to ensure that all Extbase
database queries consistently knew whether enable fields should be
respected or ignored.

Since this feature is gone, it is not possible anymore to fetch data
consistently.

If the enable fields are ignored in a repository any related data of
those entities are still loaded with enable fields applied.

As the TYPO3 backend generally does not respect enable fields - which
is the expected behavior - this patch disables enable field restrictions
globally in backend context, effectively restoring the behavior of the
former ignoreAllEnableFieldsInBe setting.

Review

  • Code review CR +2 Done
    • Benni Mack +2
    • Simon Schaufelberger +1
  • Verified V +2 Done
    • Benni Mack +2
    • Simon Schaufelberger +1
    • core-ci +1 CI

Issues 2

Files 2

Review log 1520

  1. Markus Klein uploaded patch set 1 06/01/26, 09:16

  2. core-ci voted on patch set 1 V -1 06/01/26, 09:28 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/102754

  3. Markus Klein uploaded patch set 2 V -1 06/01/26, 14:47

  4. core-ci voted on patch set 2 V +1 06/01/26, 14:55 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/102769

  5. Markus Klein updated the commit message in patch set 3 V +1 06/03/26, 14:46

  6. core-ci voted on patch set 3 V +1 06/03/26, 14:53 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/102912

  7. Josef Glatz updated the commit message in patch set 4 V +1 06/08/26, 03:40

  8. Josef Glatz commented on patch set 4 06/08/26, 03:42

    @markus.klein@typo3.org hey I‘ve tried to fix the commit message grammatically because it was hard to read for me. Feel free to adopt/rollback!
  9. core-ci voted on patch set 4 V +1 06/08/26, 03:47 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/103099

  10. Georg Ringer voted on patch set 4 CR +1 V +1 06/08/26, 05:26

  11. Josef Glatz commented on patch set 4 CR +1 V +1 06/08/26, 08:33

    functionality tested. however I can not say anything if the change is conceptional the right way.
  12. Simon Schaufelberger voted on patch set 4 CR +1 V +1 06/16/26, 14:52

  13. Benni Mack commented on patch set 4 06/16/26, 17:44

    I see this needs to be fixed, but it's really the worst case because we need to deal with the request object. I assume we should get it in like this with a big remark, that we should have multiple "TYPO3QuerySettings" objects, and we use a custom QuerySettings object for the backend and one for the frontend. something along those lines. don't want to block it, but just have this for historical reasons in there, in case I will have a look at that commit in 5 years or so :)
  14. Markus Klein commented on patch set 4 06/18/26, 12:47

    Reply

    I'll add a comment, of course. Thanks for checking the patch.
  15. Markus Klein uploaded patch set 5 CR +1 V +1 06/18/26, 13:03

  16. core-ci voted on patch set 5 V +1 06/18/26, 13:10 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/103639

  17. Simon Schaufelberger voted on patch set 5 CR +1 V +1 06/18/26, 14:15

  18. Benni Mack voted on patch set 5 CR +1 V +1 07/17/26, 16:01

  19. Benni Mack voted on patch set 5 CR +2 V +2 07/17/26, 16:28

  20. Benni Mack merged patch set 6 07/17/26, 16:28