From bd45336073cfdd75f9d0bd58c577f221dbf83db9 Mon Sep 17 00:00:00 2001 From: Rosie Le Faive Date: Wed, 21 Aug 2024 09:15:39 -0300 Subject: [PATCH] formatting --- docs/user-documentation/extending.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-documentation/extending.md b/docs/user-documentation/extending.md index 218299096..ae8d6fe52 100644 --- a/docs/user-documentation/extending.md +++ b/docs/user-documentation/extending.md @@ -119,8 +119,8 @@ A tool that allows you to clone an existing content type. Can be used to copy an #### Prevent orphaned entity relationships -[Entity Reference Integrity](https://www.drupal.org/project/entity_reference_integrity) -[Entity Reference Integrity Extras](https://github.com/discoverygarden/entity_reference_integrity_extra) +* [Entity Reference Integrity](https://www.drupal.org/project/entity_reference_integrity) +* [Entity Reference Integrity Extras](https://github.com/discoverygarden/entity_reference_integrity_extra) Normally when deleting content (nodes, taxonomy terms, etc), any content that references the deleted entity isn't altered so you end up with orphan/zombie references, which are visible in the JSON representation but invisible otherwise. With Entity Reference Integrity's submodule (-Enforce), you won't be able to delete content that's referenced from elsewhere, preserving your database integrity.