#108832Find a better way to access the settings of a user
Description
When dealing with Backend users, the ominous “uc” keeps a lot of data, and we don’t really have a clean API to access this information to runtime.
We should introduce a UserSettings object.
Reviews 7
- main 93780[BUGFIX] Mitigate missing `user_settings` field during CLI bootstrap
- main 94282[!!!][TASK] Remove legacy $GLOBALS['TYPO3_USER_SETTINGS']
- 14.3 93875[BUGFIX] Merge deprecated EMU::addFieldsToUserSettings user settings
- main 93839[BUGFIX] Merge deprecated EMU::addFieldsToUserSettings user settings
- main 92630[FEATURE] Introduce UserSettings object for BE_USER profile settings
- main 93726[BUGFIX] Fix double JSON encoding of backend user settings
- main 92653[FEATURE] Migrate user settings configuration to TCA
Related issues 5
- Task #108843Get rid of TYPO3_USER_SETTINGS global
- Bug #109638Backend user settings are JSON-encoded twice before being stored in the database
- Bug #109707ExtensionManagementUtility::addFieldsToUserSettings() no longer works in TYPO3 v14
- Bug #109719Prevent undefined "titleLen" key warnings in backend user settings usage
- Task #109966Remove legacy $GLOBALS['TYPO3_USER_SETTINGS'] support