Overview

With recent updates to the Contently platform, some users may experience issues when attempting to clone stories created in our legacy editors (Versions 1 and 2). This guide clarifies the current state of cloning between editors, why certain limitations exist, and what options are available to you.

Example Error You May Encounter:

"Cloning from V2 to V1 editor is not supported. Please select a publication with Text Editor V2 or V3 enabled."

---

What’s Changed?

As part of our ongoing platform improvements, we’ve made changes to enhance:

• System performance

• Security

• Editor compatibility with modern content workflows

Initially, cloning from V2 to V1 was silently supported but was recently and unintentionally disabled due to backend changes. This was not an intentional product decision, but rather a side effect of system upgrades. The engineering team has since reviewed and re-enabled V2 to V1 cloning to preserve backward compatibility.

However, cloning to or from the newer V3 editor remains limited due to fundamental differences in design and architecture.

---

✅ Current Cloning Capabilities

---

What You Can Do Instead (If Cloning is Not Supported)

If you need to clone and the feature isn’t available due to editor incompatibility, we offer an alternative:

Migration Support

Our engineering team can manually migrate your stories into the desired editor. These migrated versions will:

• Retain your original content

• Be clearly labeled with “Clone” in the title for easy identification

---

How to Request Migration

To request a migration:

1. Collect the URLs of the stories you'd like cloned.

2. Confirm the error you are receiving when cloning.

3. Submit a support ticket or reply to your current ticket with:

   • The list of story links

   • Error observed

   • A note requesting migration to complete the cloning. 

Our team will process your request and let you know once the cloned stories are available in your account.