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
@@ -47,7 +47,8 @@ The following snippet will give an overview of the keys and values in the conten
47
47
"PreviewBadge": "<![CDATA[<b>My HTML here</b>]]>",
48
48
"ResolveUrlsFromTextString": false,
49
49
"ShowDeprecatedPropertyEditors": false,
50
-
"ShowDomainWarnings": true
50
+
"ShowDomainWarnings": true,
51
+
"ShowUnroutableContentWarnings": true
51
52
}
52
53
}
53
54
}
@@ -174,15 +175,23 @@ This setting is used for controlling whether or not the Data Types marked as obs
174
175
175
176
By default this is set to `false`. To make the obsolete data types visible in the dropdown change the value to `true`.
176
177
177
-
### Show Domain Warnings
178
+
### Show domain warnings
178
179
179
180
If you do not configure Domains for each language in a multilingual site then every time you publish your content you get this warning:
180
181
181
182
`Content published: Domains are not configured for multilingual site, please contact an administrator, see log for more information.`
182
183
183
184
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.
184
185
185
-
## ContentVersionCleanupPolicy
186
+
### Show unroutable content warnings
187
+
188
+
If your routing setup leads to more than one document having the same URL, on publish a warning will be displayed:
189
+
190
+
`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.`
191
+
192
+
To suppress these warnings, set this option to `false`.
193
+
194
+
## Content version cleanup policy
186
195
187
196
The global settings for the scheduled job which cleans historic content versions. These settings can be overridden per Document Type.
188
197
@@ -200,19 +209,19 @@ See [Content Version Cleanup](../../fundamentals/data/content-version-cleanup.md
200
209
201
210
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.
202
211
203
-
### EnableCleanup
212
+
### Enable cleanup
204
213
205
214
When set to `true`, a scheduled job will delete historic content versions that are not retained according to the policy every hour.
206
215
207
216
When set to `false`, the scheduled job will not delete any content versions, regardless of any overridden settings for a Document Type.
208
217
209
218
The dotnet new template provides an `appsettings.json` file with the default value set to `true` for all sites.
210
219
211
-
### KeepAllVersionsNewerThanDays
220
+
### Keep all versions newer than days
212
221
213
222
All versions that fall in this period will be kept.
214
223
215
-
### KeepLatestVersionPerDayForDays
224
+
### Keep latest version per day for days
216
225
217
226
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.
218
227
@@ -237,11 +246,11 @@ This section is used for managing how Umbraco handles images, allowed attributes
237
246
238
247
Let's break it down.
239
248
240
-
### ImageFileTypes
249
+
### Image file types
241
250
242
251
This is a separated list of accepted image formats
243
252
244
-
### AutoFillImageProperties
253
+
### Auto fill image properties
245
254
246
255
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.
Copy file name to clipboardExpand all lines: 13/umbraco-cms/tutorials/editors-manual/getting-started-with-umbraco/creating-saving-and-publishing-content.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,8 +65,7 @@ To publish the node with descendants, follow these steps:
65
65
3. Select **Publish with descendants**.
66
66
67
67

68
-
4. Toggle the option to **Include unpublished content items** if you wish to. This option includes all unpublished content items for the selected page and the available linked pages.
69
-
68
+
4. Toggle the option to **Include unpublished content items** if you wish to. This option includes all unpublished content items for the selected page and the descendant pages.
70
69

0 commit comments