Localization enhancements #10705
Replies: 2 comments
-
Being able to unpublish specific locales really needs to be prioritised. It seems like a fundamental feature for localization. Currently the only way I can see to unpublish a locale is completely deleting the document and re-implementing it without publishing the specific locale, causing all version history to be lost (which in our case is not practical). If anyone has any other workarounds I'd appreciate if they could share. Glad to see it's showing up here for discussion. |
Beta Was this translation helpful? Give feedback.
-
@rilrom, I support your view, and here's how I see this improvement for Payload's localization to match Strapi's excellent implementation. We need two key features for collections with translations:
For example: if content ID 5 has English published but French in draft:
This solves the common issue where content exists in some languages but not others, ensuring users only see properly published content in their requested language. These changes would significantly improve Payload's localization workflow and make it more user-friendly for content managers working with multiple languages. |
Beta Was this translation helpful? Give feedback.
-
We aim to improve current localization features with the following items:
status
bar to include all locale status information. Related thread here by italodr.Any other localization enhancements requests are welcome, they will be prioritized and incorporated into the roadmap accordingly.
Beta Was this translation helpful? Give feedback.
All reactions