payloadcms / payloadcms/payload

Localization: Can not publish single locale

Open
#14,672 1 comment 0 reactions 1 assignee View on GitHub

@JarrodMFlesch is already working on this.

Since Nov 19, 2025.

Dominant language
TypeScript
Stars
44.8k
Forks
4.2k
Avg merge
2d 21h
Merged PRs (30d)
53

Description

Describe the Bug

I'm looking to upgrade one of our websites to the latest version of Payload from 3.48.0 to benefit from all the improvements.

Unfortunately in early testing it became clear there are issues with publishing single locales.

Firstly, the UI doesn't respect that the locale is published, getting stuck in "Changed", this becomes all the more confusing now that "Draft (has published version)" exists as you will never see a "Published" page, it will always appear as a "Draft".

Secondly, it doesn't just publish the locale you are asking it to, clicking "Publish in Global" also publishes every other locale. This isn't expected behaviour.

These two in combination make localization feel very broken.

Link to the code that reproduces this issue

https://github.com/PP-Tom/payload-status-issue

Reproduction Steps

Reproduction steps demonstrated in the video below:

https://github.com/user-attachments/assets/cf10f3e7-b43f-45e3-a1e6-0f71cf7f3698

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

area: core

Environment Info
Binaries:
  Node: 22.14.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  payload: 3.64.0
  next: 15.4.7
  @payloadcms/db-mongodb: 3.64.0
  @payloadcms/graphql: 3.64.0
  @payloadcms/next/utilities: 3.64.0
  @payloadcms/richtext-lexical: 3.64.0
  @payloadcms/translations: 3.64.0
  @payloadcms/ui/shared: 3.64.0
  react: 19.1.0
  react-dom: 19.1.0
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
  Available memory (MB): 16203
  Available CPU cores: 16

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.