You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 13/umbraco-cms/reference/configuration/contentsettings.md
+17-8Lines changed: 17 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,8 @@ The following snippet will give an overview of the keys and values in the conten
49
49
"PreviewBadge": "<![CDATA[<b>My HTML here</b>]]>",
50
50
"ResolveUrlsFromTextString": false,
51
51
"ShowDeprecatedPropertyEditors": false,
52
-
"ShowDomainWarnings": true
52
+
"ShowDomainWarnings": true,
53
+
"ShowUnroutableContentWarnings": true
53
54
}
54
55
}
55
56
}
@@ -176,15 +177,23 @@ This setting is used for controlling whether or not the Data Types marked as obs
176
177
177
178
By default this is set to `false`. To make the obsolete data types visible in the dropdown change the value to `true`.
178
179
179
-
### Show Domain Warnings
180
+
### Show domain warnings
180
181
181
182
If you do not configure Domains for each language in a multilingual site then every time you publish your content you get this warning:
182
183
183
184
`Content published: Domains are not configured for multilingual site, please contact an administrator, see log for more information.`
184
185
185
186
If you have a use case for not setting the domains, you can set this setting **ShowDomainWarnings** to `false` to stop the warning from displaying.
186
187
187
-
## ContentVersionCleanupPolicy
188
+
### Show unroutable content warnings
189
+
190
+
If your routing setup leads to more than one document having the same URL, on publish a warning will be displayed:
191
+
192
+
`Content published: The document does not have a URL, possibly due to a naming collision with another document. More details can be found under Info.`
193
+
194
+
To suppress these warnings, set this option to `false`.
195
+
196
+
## Content version cleanup policy
188
197
189
198
The global settings for the scheduled job which cleans historic content versions. These settings can be overridden per Document Type.
190
199
@@ -202,19 +211,19 @@ See [Content Version Cleanup](../../fundamentals/data/content-version-cleanup.md
202
211
203
212
To retain only the current draft and published version, set both the "keep" settings values to 0. The next time the scheduled job runs (hourly) all non-current versions (except those marked "prevent cleanup") will be removed.
204
213
205
-
### EnableCleanup
214
+
### Enable cleanup
206
215
207
216
When set to `true`, a scheduled job will delete historic content versions that are not retained according to the policy every hour.
208
217
209
218
When set to `false`, the scheduled job will not delete any content versions, regardless of any overridden settings for a Document Type.
210
219
211
220
The dotnet new template provides an `appsettings.json` file with the default value set to `true` for all sites.
212
221
213
-
### KeepAllVersionsNewerThanDays
222
+
### Keep all versions newer than days
214
223
215
224
All versions that fall in this period will be kept.
216
225
217
-
### KeepLatestVersionPerDayForDays
226
+
### Keep latest version per day for days
218
227
219
228
For content versions that fall in this period, the most recent version for each day is kept. All previous versions for that day are removed unless marked as preventCleanup.
220
229
@@ -239,11 +248,11 @@ This section is used for managing how Umbraco handles images, allowed attributes
239
248
240
249
Let's break it down.
241
250
242
-
### ImageFileTypes
251
+
### Image file types
243
252
244
253
This is a separated list of accepted image formats
245
254
246
-
### AutoFillImageProperties
255
+
### Auto fill image properties
247
256
248
257
You can define what properties should be automatically updated when an image is being uploaded. This means that if you decide to rename the default **umbracoWidth** and **umbracoHeight** properties the values in **`"WidthFieldAlias"`** and **`"HeightFieldAlias"`** need to be updated. This needs to happen in order to automatically populate the values when the image is being uploaded.
0 commit comments