From e12bb5286fc7233a7c157ba06f0e2beeac5b85ec Mon Sep 17 00:00:00 2001 From: Jette <110890857+Jette94@users.noreply.github.com> Date: Thu, 24 Oct 2024 10:39:48 +0200 Subject: [PATCH 1/6] Update content-version-cleanup.md Added relevant information from https://docs.umbraco.com/umbraco-cms/reference/configuration/contentsettings#enablecleanup --- 14/umbraco-cms/fundamentals/data/content-version-cleanup.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/14/umbraco-cms/fundamentals/data/content-version-cleanup.md b/14/umbraco-cms/fundamentals/data/content-version-cleanup.md index 9cd7197359b..f094f41405d 100644 --- a/14/umbraco-cms/fundamentals/data/content-version-cleanup.md +++ b/14/umbraco-cms/fundamentals/data/content-version-cleanup.md @@ -46,6 +46,8 @@ Additionally, it is possible to keep the feature enabled but mark specific versi It is worth noting that whilst we delete rows, we do not shrink database files or rebuild indexes. For upgraded sites with a lot of history you may wish to perform these tasks. If they are not part of your regular database maintenance plan already. +If set to `true`, a scheduled job will delete historic content versions every hour, while setting it to `false` will never delete any content versions regardless of settings. For more information on this, see [EnableCleanup](../../reference/configuration/contentsettings.md#enablecleanup). + ## Overriding global settings It is possible to override the global settings per Document Type in the backoffice to prevent unwanted cleanup. This can be managed in the "permissions" Content App for each Document Type. From 24c6500c181949880a3a5d166490521b81cecb6e Mon Sep 17 00:00:00 2001 From: Jette <110890857+Jette94@users.noreply.github.com> Date: Thu, 24 Oct 2024 14:39:34 +0200 Subject: [PATCH 2/6] Update 14/umbraco-cms/fundamentals/data/content-version-cleanup.md Co-authored-by: sofietoft --- 14/umbraco-cms/fundamentals/data/content-version-cleanup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/14/umbraco-cms/fundamentals/data/content-version-cleanup.md b/14/umbraco-cms/fundamentals/data/content-version-cleanup.md index f094f41405d..3e55d57f689 100644 --- a/14/umbraco-cms/fundamentals/data/content-version-cleanup.md +++ b/14/umbraco-cms/fundamentals/data/content-version-cleanup.md @@ -46,7 +46,7 @@ Additionally, it is possible to keep the feature enabled but mark specific versi It is worth noting that whilst we delete rows, we do not shrink database files or rebuild indexes. For upgraded sites with a lot of history you may wish to perform these tasks. If they are not part of your regular database maintenance plan already. -If set to `true`, a scheduled job will delete historic content versions every hour, while setting it to `false` will never delete any content versions regardless of settings. For more information on this, see [EnableCleanup](../../reference/configuration/contentsettings.md#enablecleanup). +A scheduled job will delete content versions every hour when the Content Version Cleanup Policy is enabled. When not enabled, no content versions will be deleted regardless of settings. For more information on this, see [EnableCleanup](../../reference/configuration/contentsettings.md#enablecleanup). ## Overriding global settings From 6bede567d0f6778d66a5b67cb7d219720d0e3047 Mon Sep 17 00:00:00 2001 From: Jette <110890857+Jette94@users.noreply.github.com> Date: Fri, 25 Oct 2024 08:57:27 +0200 Subject: [PATCH 3/6] Update 14/umbraco-cms/fundamentals/data/content-version-cleanup.md Co-authored-by: sofietoft --- 14/umbraco-cms/fundamentals/data/content-version-cleanup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/14/umbraco-cms/fundamentals/data/content-version-cleanup.md b/14/umbraco-cms/fundamentals/data/content-version-cleanup.md index 3e55d57f689..c6d7410396d 100644 --- a/14/umbraco-cms/fundamentals/data/content-version-cleanup.md +++ b/14/umbraco-cms/fundamentals/data/content-version-cleanup.md @@ -46,7 +46,7 @@ Additionally, it is possible to keep the feature enabled but mark specific versi It is worth noting that whilst we delete rows, we do not shrink database files or rebuild indexes. For upgraded sites with a lot of history you may wish to perform these tasks. If they are not part of your regular database maintenance plan already. -A scheduled job will delete content versions every hour when the Content Version Cleanup Policy is enabled. When not enabled, no content versions will be deleted regardless of settings. For more information on this, see [EnableCleanup](../../reference/configuration/contentsettings.md#enablecleanup). +A scheduled job will delete content versions regularly when the Content Version Cleanup Policy is enabled. For more information on how often content is deleted, read the [ContentSettings article](../../reference/configuration/contentsettings.md#enablecleanup). ## Overriding global settings From 50835e8dbfd4df1791664b1246e789173db4b657 Mon Sep 17 00:00:00 2001 From: Jette <110890857+Jette94@users.noreply.github.com> Date: Fri, 25 Oct 2024 09:00:46 +0200 Subject: [PATCH 4/6] Update content-version-cleanup.md Changed position --- 14/umbraco-cms/fundamentals/data/content-version-cleanup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/14/umbraco-cms/fundamentals/data/content-version-cleanup.md b/14/umbraco-cms/fundamentals/data/content-version-cleanup.md index c6d7410396d..cccb50575a8 100644 --- a/14/umbraco-cms/fundamentals/data/content-version-cleanup.md +++ b/14/umbraco-cms/fundamentals/data/content-version-cleanup.md @@ -4,6 +4,8 @@ A new version is created whenever you save and publish a content item in Umbraco ## How it works +A scheduled job will delete content versions regularly when the Content Version Cleanup Policy is enabled. For more information on how often content is deleted, read the [ContentSettings article](../../reference/configuration/contentsettings.md#enablecleanup). + The default cleanup policy will: * Not delete any versions created over the previous 4 days. The recent version history is preserved. See the `KeepAllVersionsNewerThanDays` setting. @@ -46,8 +48,6 @@ Additionally, it is possible to keep the feature enabled but mark specific versi It is worth noting that whilst we delete rows, we do not shrink database files or rebuild indexes. For upgraded sites with a lot of history you may wish to perform these tasks. If they are not part of your regular database maintenance plan already. -A scheduled job will delete content versions regularly when the Content Version Cleanup Policy is enabled. For more information on how often content is deleted, read the [ContentSettings article](../../reference/configuration/contentsettings.md#enablecleanup). - ## Overriding global settings It is possible to override the global settings per Document Type in the backoffice to prevent unwanted cleanup. This can be managed in the "permissions" Content App for each Document Type. From 692576213891e6ce89c72fe31c4247e5463fe5a3 Mon Sep 17 00:00:00 2001 From: sofietoft Date: Fri, 25 Oct 2024 09:05:33 +0200 Subject: [PATCH 5/6] Small fix to trigger GitBook checks --- 14/umbraco-cms/fundamentals/data/content-version-cleanup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/14/umbraco-cms/fundamentals/data/content-version-cleanup.md b/14/umbraco-cms/fundamentals/data/content-version-cleanup.md index cccb50575a8..ee88ff81d6c 100644 --- a/14/umbraco-cms/fundamentals/data/content-version-cleanup.md +++ b/14/umbraco-cms/fundamentals/data/content-version-cleanup.md @@ -1,6 +1,6 @@ # Content Version Cleanup -A new version is created whenever you save and publish a content item in Umbraco. This is how you can roll back to a previous version. Every saved version stores a record in the database, not only for the version but also for each content item property for that version. In a multi-lingual site, further rows are added for every culture variation. Over time this amount of data can build and swallow up the capacity of your SQL Server and slow the performance of the Umbraco backoffice. +A new version is created whenever you save and publish a content item in Umbraco. This is how you can roll back to a previous version. Every saved version stores a record in the database, not only for the version but also for each content item property for that version. In a multi-lingual site, further rows are added for every culture variation. Over time, this amount of data can build and swallow up your SQL Server's capacity and slow the Umbraco backoffice's performance. ## How it works From 6f1f433bb3e3a5daf2a511e1103340292c018c28 Mon Sep 17 00:00:00 2001 From: sofietoft Date: Fri, 25 Oct 2024 09:11:09 +0200 Subject: [PATCH 6/6] Trigger GitBook checks --- .../fundamentals/data/content-version-cleanup.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/14/umbraco-cms/fundamentals/data/content-version-cleanup.md b/14/umbraco-cms/fundamentals/data/content-version-cleanup.md index ee88ff81d6c..668f6f22fd1 100644 --- a/14/umbraco-cms/fundamentals/data/content-version-cleanup.md +++ b/14/umbraco-cms/fundamentals/data/content-version-cleanup.md @@ -21,7 +21,7 @@ Based on the default cleanup policy, you can roll back content to the latest ver * Created within the last 90 days, or * Marked as "Prevent Cleanup" in the Backoffice version history. -The **History** section, which acts as an audit log, is not cleared out, and will continue to show logs for versions older than 90 days. +The **History** section, which acts as an audit log, is not cleared out and will continue to show logs for versions older than 90 days. {% endhint %} The feature can be configured in the `appSettings.json`: @@ -42,11 +42,11 @@ The feature can be configured in the `appSettings.json`: } ``` -For sites with stricter requirements, it is possible to opt-out of both options globally, see [ContentSettings](../../reference/configuration/contentsettings.md#contentversioncleanuppolicy) and by Document Type. +For sites with stricter requirements, it is possible to opt out of both options globally, see [ContentSettings](../../reference/configuration/contentsettings.md#contentversioncleanuppolicy) and by Document Type. Additionally, it is possible to keep the feature enabled but mark specific versions to keep forever. -It is worth noting that whilst we delete rows, we do not shrink database files or rebuild indexes. For upgraded sites with a lot of history you may wish to perform these tasks. If they are not part of your regular database maintenance plan already. +It is worth noting that whilst we delete rows, we do not shrink database files or rebuild indexes. For upgraded sites with a lot of history, you may wish to perform these tasks. If they are not part of your regular database maintenance plan already. ## Overriding global settings @@ -58,7 +58,7 @@ It is possible to override the global settings per Document Type in the backoffi It is possible to mark important content versions as "prevent cleanup" to ensure they are never removed. This happens via the new and improved rollback modal which can be found on the "info" content app for each document. -1. Open rollback modal. +1. Open the rollback modal.
2. Click **Prevent cleanup** button for each important version.