I still wasn't able to replicate this, if the page exists in the locale that you're trying to duplicate it in, it will keep the translation. You have to duplicate it from the right locale, and releases are locale-specific, so you do have to go into the French one (for example) to find the duplicated page in the right locale. If that's already what you're doing, would you mind recording a Jam of this behavior so I see the steps you're taking and we can get to the bottom of this? There might be something wrong with the way we do it here, or a bug specific to the repository you're working with, so I'd like to see it if possible! (You can send me the link in a private message if needed).
Similarly, I'm getting the right assets when translating (photos and linked pages). What are the assets you're not seeing when you're duplicating? For linked pages, the linked page has to already exist in the locale of the page you're duplicating if that makes sense.
I understand what you're saying, it's not the most intuitive workflow. I'm open to creating a feature request to improve it with your suggestions, just trying to clarify what's a bug and what needs to be improved upon
I am also struggling with this duplication flow.
What would be expected was to have a duplicate button that would duplicate a document in its all (already) translated locales.
Iāve followed your flow, and it created a release with the same document, which was weird.
So if I update the ācopiedā document, I release it Iāll end up changing the original document not having cloned it afterwards.
Is there any way to clone/duplicate a document and itāll include all the translated versions?
My use case is that I want to have 2 different versions of the same document in all 4 locales, with the exception to have a different slug.
If this is possible, can you please record a video on how to do it?
Not sure Iām fully following what youāre trying to do, but weāll try to figure it out together
If you copy a page into another locale, the original and its locales will always be linked together. This is to make sure that locales donāt get orphaned and links continue working throughout locales. If you want different versions of the same documents, you have to duplicate the original first, then copy to other locales the original document for your translations, and then copy to other locales the duplicate. This will create two āsetsā of documents that you can modify independently. Does that make sense?
Duplicating a document only ever duplicates the current locale. It wonāt duplicate all of them. So youād have to duplicate the master locale ā translate that duplicated one to the other ones.
Iāll present an example of my use-case: I have a document in 4 languages (EN, ES, PT and RU).
I need to create a new document in the same 4 languages while just changing some minor parts of the text, like a number or a title.
In a easy flow, I would just click a button that would duplicate the document in its 4 languages to a new document while duplicating the same 4 languages.
Your described flow complicates this approach, as Iāll need to create the translations after duplicating the document in EN, where I need to copy+paste translations for ES, RU and PT, just because I want to keep the languages linked to the same document.
There should be an easier way to achieve this.
Is there such a way? If not, please consider my feedback to the team.
Thank you for clarifying, I completely understand what you mean now. Youād like to duplicate a page and all its associated content (locales) in one go, as opposed to it duplicating just the page youāre on (locale specific). Right? If so, this is something weāve flagged in the past here: Jira so itās on the Page Builderās radar to improve. I donāt know when exactly theyāll get around to it, but they know thereās a user need for this Iāll add your post to the ticket so we can warn you when this has been introduced. Thanks again!
Hey @joel, and anyone passing by this post still: this feature has been introduced. Copying to another locale now keeps the slices of the original locale.
