Slug will be generated pre-maturely on first draft save resulting in single letter slugs

Question

Slug will be generated pre-maturely on first draft save resulting in single letter slugs

Closed this issue a month ago · 3 comments

Describe the Bug

Hi. Just started evaluating Payload as a Strapi replacement. I have started with the website template and realised an issue with slug generation: Slug will be generated pre-maturely on first draft save resulting in single letter slugs.
Example: When I type "Hello world" into the title field I end up with "h" as the slug.
I think it might be related to autosaving drafts, which happens while typing.

Is this expected behaviour? I would expect the slug to be generated either (1) on first user triggered save or (2) on keyup when editing the title until first save.

Link to the code that reproduces this issue

Reproduction Steps

blank install of latest template Website"

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

area: core, area: templates

Environment Info

Binaries:
  Node: 22.12.0
  npm: 10.9.0
  Yarn: 1.22.17
  pnpm: 10.5.0
Relevant Packages:
  payload: 3.56.0
  next: 15.4.4
  @payloadcms/db-mongodb: 3.56.0
  @payloadcms/email-nodemailer: 3.56.0
  @payloadcms/graphql: 3.56.0
  @payloadcms/live-preview: 3.56.0
  @payloadcms/live-preview-react: 3.56.0
  @payloadcms/next/utilities: 3.56.0
  @payloadcms/payload-cloud: 3.56.0
  @payloadcms/plugin-form-builder: 3.56.0
  @payloadcms/plugin-nested-docs: 3.56.0
  @payloadcms/plugin-redirects: 3.56.0
  @payloadcms/plugin-search: 3.56.0
  @payloadcms/plugin-seo: 3.56.0
  @payloadcms/richtext-lexical: 3.56.0
  @payloadcms/translations: 3.56.0
  @payloadcms/ui/shared: 3.56.0
  react: 19.1.0
  react-dom: 19.1.0
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:15 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10

Answer 1 · 2025-09-26T08:44:09.000Z

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

Answer 2 · 2025-10-07T14:24:27.000Z

🚀 This is included in version v3.59.0

Answer 3 · 2025-10-15T05:05:22.000Z

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