Rules for Deleting Reused Content
When you try to delete content, Paligo will check how the deletion will affect your remaining topics. If the remaining topics will be broken by the deletion, Paligo will either:
-
Prevent you from deleting the content
-
Ask you if you want to go ahead with the deletion, even though the content will break links in other topics.
To do this, Paligo has some internal rules that involve checking your content for "dependencies". A dependency is when a topic or some other component needs to reference another component.
The checks that Paligo runs include:
-
Do any topics link to the component you are trying to delete?
-
Do any publications contain the component you are trying to delete?
-
Do any topics contain the component you are trying to delete?
-
Are there any components with dependencies inside the folder (this only applies to folders)?
If the answer is yes, there is a dependency. Depending on the scenario, Paligo will either ask you if you want to proceed with the deletion or it will tell you that the component cannot be deleted.
If you choose to proceed with a deletion, the component will be deleted, but this will result in broken links and missing content from other topics. It is a good idea to remove these dependencies before you delete, so that other topics do not have missing content.
If Paligo will not allow you to delete the component, you can Find and Remove Dependencies, and then try again. When there are no dependencies, Paligo will let you delete the component.