Copying document between locales removes all content entries

Hi,

Over time I've noticed three different behaviors when copying documents between locales:

  1. Previous Behavior: Copying a document only removed related documents, which was expected and ideal.
  2. Interim Behavior: Copying retained all related documents. This wasn’t expected but manageable, as we would manually unlink and link documents to the current locale.
  3. Current Behavior: Copying a document with related content results in the new document being completely emptied—text fields, booleans, and even assets (which are shared between locales) are removed. This makes the core functionality of copying nearly useless since we need to manually re-enter the content and relink all assets, which is time-consuming and error-prone.

To work around this issue, we've been using the archive functionality:

  • We unlink all related documents, save the draft, and then copy.
  • Next, we revert the original document to its last published state, preserving the original links.

This process adds significant overhead and increases the risk of errors, impacting reliability and productivity.

Could you please clarify the reasoning behind this change? Is there a recommended workflow for handling this scenario, and should we expect the current behavior to remain or not?

Thank you for your support.

2 Likes

Wanted to ask about this issue as well.
Our content team has informed us that they are also having an issue with copying content to other locales. This creates massive and frankly unnecessary overhead for our team and bogs down the speed at which we can move.

Is this expected behavior or is this a bug being worked out?
Thank you for any assistance

Hey Everyone,

This should be fixed now.

Thanks.

2 Likes

Thank you Phil.
Incredibly quick response and resolution.
Thank you again!

1 Like