Presets - duplicated users & crashes when opening preset list

Open
#15,672 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
nextjs, react, typescript
Domain
frontend

Research direction

Start by running the linked steepnicki/payload-preset-bugs reproduction repository with the listed Payload, Next.js, React, and MongoDB environment, then reproduce each of the three preset scenarios in the UI. Done means users are not duplicated after saves, presets using the "IS IN" condition open without crashing, and links remain clickable after duplicating a preset.

Written by the indexing model from the issue text.

Description

area: ui Bug stale status: needs-triage
Describe the Bug

Bug no. 1 - Duplicated users - when editing a preset and adding or removing a user from the access list, currently logged in user will be appended to the users list after every save
Bug no. 2 - Preset with "IS IN" conditional - when creating a preset which uses "IS IN" conditional, after saving and trying to open the list of presets, crashes occurs
Bug no. 3 - Duplicating a preset causes no links to be clickable after duplicating

In my reproduction repo I have added a script which automatically creates the mock data in the database on app launch. This includes the presets that are experiencing issues.

Link to the code that reproduces this issue

https://github.com/steepnicki/payload-preset-bugs

Reproduction Steps

1 - Duplicated users - edit preset, add or remove a user from the access list. Currently logged in user will be appended to the users list after every save
2 - Create a preset with "IS IN" conditional, save, and open the list with presets
3 - Duplicate a preset, be navigated back to the list, observe that no links are clickable in the list

Which area(s) are affected?

area: ui

Environment Info
Binaries:
  Node: 22.14.0
  npm: 10.9.2
  Yarn: 1.22.22
  pnpm: 10.30.0
Relevant Packages:
  payload: 3.56.0
  next: 15.5.8
  @payloadcms/db-mongodb: 3.56.0
  @payloadcms/email-nodemailer: 3.56.0
  @payloadcms/graphql: 3.56.0
  @payloadcms/next/utilities: 3.56.0
  @payloadcms/plugin-cloud-storage: 3.56.0
  @payloadcms/richtext-lexical: 3.56.0
  @payloadcms/storage-s3: 3.56.0
  @payloadcms/translations: 3.56.0
  @payloadcms/ui/shared: 3.56.0
  react: 19.1.3
  react-dom: 19.1.3
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.3.0: Wed Jan 28 20:49:24 PST 2026; root:xnu-12377.81.4~5/RELEASE_ARM64_T8132
  Available memory (MB): 32768
  Available CPU cores: 10
Dominant language
TypeScript
Stars
44.8k
Forks
4.2k
Avg merge
2d 21h
Merged PRs (30d)
53

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from payloadcms/payload

All issues in payloadcms/payload

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.