Detaching a Live Copy and deleting vs deleting Language Copy and then deleting Live Copy

[ambmal01]

We've come to find out that if we do not detach before deleting a Live Copy page, it will add a property to the Language copy of the page that tells the system not to inherit that page in the Live Copy again. It's caused some problems, so we're trying to be careful to detach a Live Copy before deleting it, so we have the option to roll that page out again in the future. 

However, in the event that we want to delete a page from both a Language Copy and it's Live Copies, can we simply delete the page in the Language Copy first and then in the Live Copy? Essentially, is a Live Copy essentially "detached" if you delete it's Blueprint first?

[AsifChowdhury · Accepted solution]

Hi @ambmal01 

You can delete a page from both the Language Copy and its Live Copies by first deleting the page in the Language Copy and then in the Live Copy. Deleting the page in the Blueprint (Language Copy) will effectively detach the Live Copy from its Blueprint, making it an independent page that can be deleted separately without affecting the Language Copy's ability to serve as a Blueprint for future Live Copies.

Here's the step-by-step process:

1. Delete the Language Copy (Blueprint): Before deleting the Live Copy page, delete the page in the Language Copy (Blueprint). This action will sever the association between the Language Copy and the Live Copy, ensuring that the Live Copy will no longer inherit updates from the Language Copy.

2. Delete the Live Copy: Once you've deleted the Language Copy, you can proceed to delete the Live Copy page separately. Since it has been detached from its Blueprint, the Live Copy can be deleted independently without any issues.