Skip to content

Commit 50835e8

Browse files
authored
Update content-version-cleanup.md
Changed position
1 parent 6bede56 commit 50835e8

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

14/umbraco-cms/fundamentals/data/content-version-cleanup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@ A new version is created whenever you save and publish a content item in Umbraco
44

55
## How it works
66

7+
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).
8+
79
The default cleanup policy will:
810

911
* 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
4648

4749
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.
4850

49-
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).
50-
5151
## Overriding global settings
5252

5353
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.

0 commit comments

Comments
 (0)