Content settings contains a handful of settings related to the content in the CMS. It includes settings such as allowed upload files, image settings, and much more. All the values in the content settings has default values, so all configuration is optional.
The following snippet will give an overview of the keys and values in the content section including the default values:
From 10.4, AllowedUploadFiles & DisallowedUploadFiles is deprecated, they will still work, but will be removed in a future version! You can use AllowedUploadedFileExtensions & DisallowedUploadedFileExtensions instead!
In the root level section, that is those without a seperate sub section like Imaging, you can configure:
Invariant properties are properties on a multilingual site that are not varied by culture. This means that they share the same value across all languages added to the website.
When the setting is set to false the invariant properties that are shared between all languages can only be edited from the default language. This means you need access to the default language, in order to edit the property.
When set to true (default) the invariant properties will need to be unlocked before they can be edited. The lock exists in order to make it clear that this change will affect more languages.
If greater control is required than available from the above, this setting can be used to store a list of file extensions. If provided, only files with these extensions can be uploaded via the backoffice.
By default, only relative URLs are allowed when getting URLs for resized images or thumbnails using the ImagesController. If you need absolute URLs you will have to add the allowed hosts to this list. The value could be ["umbraco.com", "www.umbraco.com", "our.umbraco.com"].
This setting allows you to specify whether a user can delete content or media items that depend on other items. This also includes any descendants that have dependencies. Setting this to true will remove or disable the Delete button.
This setting allows you to specify whether or not users can unpublish content items that depend on other items or have descendants that have dependencies. Setting this to true will disable the Unpublish button.
This setting consists of a list of file extensions that editors shouldn't be allowed to upload via the backoffice.
In case of a 404 error (page not found) Umbraco can return a default page instead. This is set here. Notice you can also set a different error page, based on the current culture so a 404 page can be returned in the correct language.
The above example shows what you need to do if you only have a single site that needs to show a custom 404 page. You specify which node that should be shown when a request for a non-existing page is being made. You can specify the node in three ways:
Enter the nodes id ("ContentId": 1)
Enter the node's GUID ("ContentKey": "4f96ffdd-b969-46a8-949e-7935c41fabc0")
Enter the XPath to find the node ("ContentXPath": "/root/Home//TextPage[@urlName = 'error404'")
Ids are usually local to the specific solution (so won't point to the same node in two different environments if you're using Umbraco Cloud).
GUIDs are universal and will point to the same node on different environments, provided the content was created in one environment and deployed to the other(s).
When using XPath, there is no "context" (like, you can't find the node based on "currentPage") so needs to be a global absolute path.
If you have multiple sites, with different cultures, setup in your tree then you will need to setup the errors section like below:
If you have more than two sites and forget to add a 404 page and a culture, the default page will act as fallback. Same happens if you for some reason forget to define a hostname on a site.
This setting can be used to hide the Umbraco logo in backoffice.
You can specify your own background image for the login screen here. The image will automatically get an overlay to match backoffice colors. This path is relative to the wwwroot/umbraco path. The default location is: wwwroot/umbraco/assets/img/installer.jpg.
You can specify your own image for the small logo in the top left corner of the login screen. This path is relative to the wwwroot/umbraco path. The default location is: wwwroot/umbraco/assets/img/application/umbraco_logo_white.svg.
This setting allows you to specify how errors in macros should be handled.
Options:
Inline - Default Umbraco behavior, show an inline error within the macro but allow the page to continue rendering.
Silent - Silently suppress the error and do not display the offending macro.
Throw - Throw an exception.
Content - Silently suppress the error, and display custom content reported in the error event args.
This allows you to customize the preview badge being shown when you're previewing a node.
This setting is used when you're running Umbraco in virtual directories. Setting this to true can increase render time for pages with a large number of links. However, this is required if Umbraco is running in a virtual directory.
This setting is used for controlling whether or not the Data Types marked as obsolete should be visible when creating new Data Types.
By default this is set to false. To make the obsolete data types visible in the dropdown change the value to true.
The global settings for the scheduled job which cleans historic content versions. These settings can be overridden per Document Type.
Current draft and published versions will never be removed, nor will individual content versions which have been marked as "preventCleanup".
See Content Version Cleanup for more details on overriding configuration and preventing cleanup of specific versions.
If you don't wish to retain content versions except for the current ones, you can set both of the "keep" settings values to 0. After doing this, the next time the scheduled job runs (hourly) all non-current versions (except those marked "prevent cleanup") will be removed.
When true a scheduled job will delete historic content versions that are not kept according to the policy every hour.
When false, the scheduled job will never delete any content versions regardless of overridden settings for a Document Type.
This defaults to false when not set in the configuration which will be the case for those upgrading from v9.0.0. However, the dotnet new template will supply an appsettings.json with the value set to true for all sites starting from Umbraco 9.1.0.
All versions that fall in this period will be kept.
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.
This variable is independent of KeepAllVersionsNewerThanDays, if both were set to the same value KeepLatestVersionPerDayForDays would never apply as KeepAllVersionsNewerThanDays is considered first.
This section is used for managing how Umbraco handles images, allowed attributes and, which properties of an image that should be automatically updated on upload.
Let's break it down.
This is a separated list of accepted image formats
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.
If you need to create a custom Media Type to handle images you need to add another object using the custom Media Type alias. Like below. Keep in mind that the width and height attributes have also been changed in this example.
Umbraco can send out email notifications. To set the SMTP server used to send the emails, edit the standard Simple Mail Transfer Protocol (SMTP) section in the global section. See the Global settings article for more information.