[#46829] - Persist Column Selection Preferences Per User
- New
- Medium
- Build: 5.4-dev
- # 46829
Joomla Version: 5.x / 6.x
Component: Backend List Views (All Components)
Date: February 4, 2026
CURRENT SITUATION (PROBLEM)
When administrators customize which columns to show/hide in backend list views (using the column selector), these preferences are NOT saved in the database.
This causes the following problems:
- Preferences are lost when using a different browser
- Preferences are lost when using a different device
- Preferences are lost in incognito/private browsing mode
- Preferences are lost when clearing browser cache/local storage
- Each administrator must reconfigure their column preferences on every browser/device they use
This affects ALL backend list views including:
- Users list
- Articles list
- Categories list
- Custom fields list
- All component backend list views
REQUESTED FEATURE
Save column visibility preferences in the database per user account, so they persist across:
- Different browsers
- Different devices
- Sessions
- Cache clearing
- Incognito/private browsing
Similar to how Joomla already saves other user preferences in the database:
- Backend language preference
- Editor choice
- Help site language
WHY THIS WOULD BE USEFUL
Practical examples:
-
Multi-device work
An administrator works from office desktop and home laptop. Currently must configure column preferences twice. With this feature, preferences would automatically sync. -
Shared workstations
Multiple administrators use the same computer but different Joomla accounts. Currently they overwrite each other's column preferences. With this feature, each user would see their own preferences. -
Browser maintenance
Administrators who regularly clear browser cache lose all column preferences. With this feature, preferences would survive cache clearing. -
New browser/device
When switching to a new computer or browser, all column preferences must be reconfigured. With this feature, preferences would immediately be available.
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
richard67
- | Labels |
Added:
Feature
|
||
Thanks for the context, Brian. A few thoughts:
Screen size argument
Valid point, but users can always manually adjust columns when needed for a specific situation. The question is which scenario occurs more frequently - I suspect most administrators primarily work from the same device/setup, making persistent preferences more valuable than the occasional need to adjust for a different screen. And when they do switch devices, manual adjustment remains possible.
Performance argument
The impact could be minimal if preferences are loaded once at login and cached in the session - similar to how user parameters are already handled. No additional queries per list view, just one small read during authentication?
I work from two specific devices with two very different screen resolutions and my time is divided almost evenly between those two devices. That is why I spent the time to write this code. For me the change you are suggesting would make this feature useless. But those are my personal opinions and are what drove me to write the feature. None of that is to say that the code can't be improved - everything can be improved and nothing is ever perfect
It was a deliberate decision (by me) to save this in the browser storage and not per user etc. some of the reasons were