payloadcms/payload

"Create new" redirects to existing document instead of creating new

Closed this issue · 3 comments

hindrek-uptime commented

Describe the Bug

"Create new" redirects to existing document instead of creating new. This only happens some times and I believe it happens due to prefetch, similar to this #9012.

This is create new button: https://github.com/payloadcms/payload/blob/main/packages/ui/src/elements/ListHeader/TitleActions/ListCreateNewDocButton.tsx
This is the actual button: https://github.com/payloadcms/payload/blob/main/packages/ui/src/elements/Button/index.tsx

The button basically has prefetch={undefined}.
I believe it should be false.

Link to the code that reproduces this issue

Reproduction Steps

Which area(s) are affected? (Select all that apply)

area: core

Environment Info

Binaries:
  Node: 22.19.0
  npm: 10.9.3
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  payload: 3.55.1
  next: 15.4.4
  @payloadcms/db-postgres: 3.55.1
  @payloadcms/email-nodemailer: 3.55.1
  @payloadcms/graphql: 3.55.1
  @payloadcms/live-preview: 3.55.1
  @payloadcms/live-preview-react: 3.55.1
  @payloadcms/next/utilities: 3.55.1
  @payloadcms/payload-cloud: 3.55.1
  @payloadcms/plugin-cloud-storage: 3.55.1
  @payloadcms/plugin-form-builder: 3.55.1
  @payloadcms/plugin-import-export: 3.55.1
  @payloadcms/plugin-nested-docs: 3.55.1
  @payloadcms/plugin-redirects: 3.55.1
  @payloadcms/plugin-search: 3.55.1
  @payloadcms/plugin-seo: 3.55.1
  @payloadcms/storage-s3: 3.55.1
  @payloadcms/translations: 3.55.1
  @payloadcms/ui/shared: 3.55.1
  react: 19.1.0
  react-dom: 19.1.0
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Thu Jun  5 18:30:46 UTC 2025
  Available memory (MB): 31947
  Available CPU cores: 32
github-actions commented

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@latest -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

github-actions commented

This issue has been automatically locked.
Please open a new issue if this issue persists with any additional detail.

github-actions commented

🚀 This is included in version v3.57.0