Localization Website Example: Title locked to slug overrides

[Jbmanllr]

Describe the Bug

Hello, I don’t know how such an obvious issue could have been left unresolved, but when trying to write a title for a non-default locale, the slug (which is locked to the title) is changed automatically. The admin UI even shows two different slugs for each locale. I did not localize the slug field. The non-default locale results in a 404.

Link to the code that reproduces this issue

link-to-reproduction.link

Reproduction Steps

Reproduction: Clone the current localization example: https://github.com/payloadcms/payload/tree/main/examples/localization , pnpm i, pnpm dev, enjoy.

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

area: core

Environment Info

Binaries:
  Node: 22.18.0
  npm: 11.5.2
  Yarn: N/A
  pnpm: 10.14.0
Relevant Packages:
  payload: 3.50.0
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.5.0: Tue Apr 22 19:52:00 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6031
  Available memory (MB): 36864
  Available CPU cores: 14

[github-actions]

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

• Reproduction Guide
• Contributing to Payload