payloadcms / payloadcms/payload
Admin panel column user settings lost on page refresh
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.8k
- Forks
- 4.2k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 53
Description
Describe the Bug
Viewing a collection in the admin panel you can select the columns you want to see in the collections table view. The bug occurs when you change the visibility settings, refresh the browser and then change the current page of the table pagination.
So you need of course more items then one page holds so you get the pagination ui. And you need to refresh the browser before switch the page. Otherwise this error does not occur.
I think it might have something to do with the query param added to the url when you change column settings.
Link to the code that reproduces this issue
https://github.com/matulkum/payload-issue-col-settings-loss
Reproduction Steps
- Got to the users collection admin view (eg localhost:3000/admin/collections/users).
- make sure pagination is set to 5 items per page so you get at least 2 pages.
- Change visible columns (eg. remove
name,createdAtcolumns and addidcolumn instead. - refresh browser page.
- select the second page in the pagination
- observe how the previous column visibility settings are restored and your last setting is lost.
Which area(s) are affected?
area: ui
Environment Info
Binaries:
Node: 26.5.0
npm: 11.17.0
Yarn: N/A
pnpm: 11.13.1
Relevant Packages:
payload: 3.88.0
next: 16.3.0
@payloadcms/db-sqlite: 3.88.0
@payloadcms/drizzle: 3.88.0
@payloadcms/graphql: 3.88.0
@payloadcms/next/utilities: 3.88.0
@payloadcms/richtext-lexical: 3.88.0
@payloadcms/translations: 3.88.0
@payloadcms/ui/shared: 3.88.0
react: 19.2.6
react-dom: 19.2.6 Operating System: Platform: darwin
Arch: arm64 Version: Darwin Kernel Version 25.6.0: Sat Jul 11 15:26:21 PDT 2026; root:xnu-12377.161.13~4/RELEASE_ARM64_T6000
Available memory (MB): 32768 Available CPU cores: 10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked reproduction and follow the admin collection table's column-visibility and pagination behavior around the URL query parameters. Confirm the settings are retained after a refresh and subsequent page change, then run the relevant admin UI checks or reproduction steps to verify the fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- next.js, react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100