Review main Merged

92630[FEATURE] Introduce UserSettings object for BE_USER profile settings

Benni Mack CR +2 V +2 Expert +1171 −6 updated 04/21/26, 15:05

Commit message

This change introduces two major improvements in EXT:setup:

1. New UserSettings object
   A readonly UserSettings object provides structured access to backend
   user profile settings defined via $GLOBALS['TYPO3_USER_SETTINGS'].
   Access via $GLOBALS['BE_USER']->getUserSettings() with has(), get(),
   toArray() methods and typed getters like isEmailMeAtLoginEnabled().

2. New JSON storage with backward compatibility
   Profile settings are now stored in a new be_users.user_settings JSON
   field. For backward compatibility, the existing serialized uc blob
   continues to be written alongside (dual-write). An upgrade wizard
   migrates existing settings from uc to the new JSON field.

Further refactorings in EXT:setup will come on top.

Review

  • Code review CR +2 Done
    • Georg Ringer +2
    • Anja Leichsenring +1
  • Verified V +2 Done
    • Georg Ringer +2
    • Anja Leichsenring +1
    • core-ci +1 CI

Issues 1

Files 16

Review log 79

  1. Benni Mack uploaded patch set 1 02/02/26, 21:24

  2. core-ci voted on patch set 1 V -1 02/02/26, 21:35 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/94851

  3. Benni Mack uploaded patch set 2 V -1 02/03/26, 10:53

  4. Benni Mack marked it ready for review 02/03/26, 10:53

  5. core-ci voted on patch set 2 V +1 02/03/26, 11:01 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/94890

  6. Anja Leichsenring voted on patch set 2 CR +1 V +1 02/03/26, 17:21

  7. Georg Ringer voted on patch set 2 CR +2 V +2 02/03/26, 19:12

  8. Georg Ringer merged patch set 3 02/03/26, 19:12

  9. Benjamin Franzke commented on patch set 3 02/05/26, 07:30

    UserSettingsSchema.php:23 Unresolved

    Can we use the Settings API (as used for dashboard/site-settings) to define the schema, or do you see limitations?