Allow Editing of Multiple Locales at once

[zubricks]

We need to open up the possibility of editing multiple locales at once, in a way similar to how Contentful does it. The editor should be able to select which locales to show at any given time, and a field per locale should be rendered allowing the editor to view multiple locales at once.

Work involved

• Before design work is completed, we could begin extending the create and update operations to accept more than one locale's data in a single request. Similar to the way that locale=* works now. This would be a backend-only change, and would be relatively isolated in nature.
• Design intent should be established or approved by the Payload team.
• Once we have the API changes that allow locale=* on create and update, we should begin extending the Payload UI so that it meets design intent, showing multiple fields at a given time in the editing UI.

Design Update 11/29/23

• Add the ability to select multiple locales from the Edit view. This will update the current selector with multi-select functionality instead of single selectable locale. Along with this, we'll be storing locales selections to user preferences on a per-route basis, i.e. if you were editing a document in English before selecting multiple locales in the Edit view, when you navigate back to a view that doesn't support multiple locales, English will be selected.

• With Publish Individual Locales #4194, we'll be updating the button component to allow for publishing changes on a locale basis, i.e. Publish English only would publish only changes to English locale fields, and leave other locale's data in its draft state. The same logic would apply if multiple locales are selected.

• When editing a single locale, localized fields will show a pill with the current locale next to the label.

• When editing multiple locales, show localized fields as grouped with indentation, and a border along the left edge.
• Fields within collapsible blocks follow the same pattern. Indentation should be the same size as container padding. This allows for the Lexical rich text editor to keep its absolute positioned tools within a safe margin without overlapping other elements.

• Some fields have different layouts for the labels, here is an example of how some of those would appear when editing multiple locales.

[matthijs166]

This would be awesome in combination with this plugin!! https://github.com/r1tsuu/payload-plugin-translator

Can't wait to see this feature release 👍

[jessrynkar]

Great plugin! Thanks for sharing

[justuskilianwolff]

I'd love that! Do you know roughly when it's gonna make it?

[Kenji-Nguyen]

I can't wait for this feature, as this is would significantly reduce the hurdle for our clients where editing multiple locales is a requirement.
Any updates on this feature?

[supra-dheerajacharya]

I’m eager for this feature! Any idea when it might become available?

[mik01aj]

Hey, I've seen this feature on your homepage (I mean, look at the screenshot), does that mean that it is already available? I'm a bit confused.

[christophemenager]

This feature would be amazing. I am really struggling with translations with only two locales.
The UX is pretty poor :

• you can't edit multiple locales at the same time
• you have to click on the smallest button ever on the top right to change the locale
• you can validate a locale but keep required fields not filled on an other local with no error and no way to know that another locale is missing fields

[anyuj]

Any update on this? Need this feature badly. 😭

[snakemastr]

I would love this. Is this still worked on?

[anyuj]

I’d like to gently bump this discussion. As many others have mentioned, localization is at the heart of most modern CMS workflows. Being able to edit and compare multiple locales side by side in the UI would be a true game changer for content teams, and it will dramatically improve efficiency. If there’s any way to raise the priority of this functionality, it would be greatly appreciated by those of us who rely on Payload for multilingual projects.

[jacktsin1]

Any updates on this??

[jessrynkar]

Thank you all for your patience on this feature and we love to see this level of demand 🙏

We will be discussing the implementation of this feature in our sprint planning next week, I will report back then with an accurate ETA. For now, hold tight, it will prioritized for the near future!