The idea is simple, splitting the different user properties into categories, as it was done for the Global Configuration pages.
An interesting effect if we are doing this: the security category can be restricted further, for example by reasking the password. This kind of requirement is not necessary when the user wants to change his description or his default view.
By splitting the /configure page, we will need to deprecate the previously used doConfigSubmit from the user, to have one per category.
Originally reported by 
wfollonier, imported from: Categorize the user properties
- assignee: wfollonier
- status: Resolved
- priority: Minor
- component(s): core
- resolution: Fixed
- resolved: 2024-07-15T21:51:06+00:00
- votes: 0
- watchers: 1
- imported: 2025-11-24
Raw content of original issue
The idea is simple, splitting the different user properties into categories, as it was done for the Global Configuration pages.
An interesting effect if we are doing this: the security category can be restricted further, for example by reasking the password. This kind of requirement is not necessary when the user wants to change his description or his default view.
By splitting the /configure page, we will need to deprecate the previously used doConfigSubmit from the user, to have one per category.
The idea is simple, splitting the different user properties into categories, as it was done for the Global Configuration pages.
Originally reported by
wfollonier, imported from: Categorize the user properties
Raw content of original issue