-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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:
payload-status-issue.mp4
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