Configure limitations in content types
Do you want to make sure your content creators know when their text is too long or a file they uploaded is too large? You can achieve this by setting limitations for elements when defining a content type.
Table of contents
How to configure limitations
- In Content model, open a content type for editing.
- For the element you want to limit, click Show configuration.
- Adjust the limits to fit your needs.
- Click Save changes.
Use limitations as validation rules
Once you've got the limitations set, they will work as validation rules and provide content creators with visual cues.
These limitations will stay as visual reminders in all workflow steps before the Published step. Content creators will see which elements still require work before they publish the content item.
When a content item doesn't meet the limitations, it can't be published. This means if someone tries to publish the item, they'll see a notification like the one below.
Validation rules for optional elements
You can define limitations also for elements that aren't set as required. For instance, you can make an asset element optional while setting its rules to accept exactly two assets. The result of this setup is that your content creators may either leave the element empty, or they can insert exactly two elements.
Finding incomplete elements
There is a handy notification in the content item's Content details.
The item will also appear in your content list as Unfinished, symbolized by an orange dot 🟠.
Which elements can have limitations
Asset elements can have limits in the number of assets (maximum, minimum, or exact number) and maximum size (in kB, MB, or GB). You can set limits for images within the element in terms of their height and width (maximum, minimum, or exact number in px).
By limiting the file types to Adjustable images, you can restrict formats to only jpg, png, gif, and webp. These image types support image transformation via the Delivery API.
How to find out image dimensions
The image width and height are displayed in the asset thumbnail only when asset limitations are set for an element. If needed, you can always find the image dimensions in the asset detail.
Linked items and subpages elements
Linked items and subpages elements can have limits in the number of items that can be added (maximum, minimum, or exact number) and the specific content types that can be added.
Rich text elements
Rich text elements can have the following limits set:
- The text can have a maximum length set as the number of words or characters. You can also allow only specific types of text formatting. This way you can prevent content creators, for example, from using H1 headings or links. Text can be allowed or forbidden.
- Images within the element can be limited in their maximum size (in kB, MB, or GB) and height and width (maximum, minimum, or exact number in px). By limiting the image types to Adjustable images, you can restrict image formats to only jpg, png, gif, and webp. These image types support image transformation via the Delivery API. Images can be allowed or forbidden.
- Components and linked items within the element can be limited to certain content types. Components and linked items can be allowed or forbidden.
- Links to content items within the element can be limited to certain content types. This limitation applies to links in text and tables.
- For tables, you can limit allowed text formatting along with the use of headings, lists, and images in table cells. Tables can be allowed or forbidden.
Taxonomy elements can have limits on the number of terms that can be selected (maximum, minimum, or exact number).
If you know that certain terms will be used a lot, preselect them in the element's default value. The terms will be prefilled when content creators add a new content item.
Text elements can have a maximum length set as the number of words or characters.
If you know a part of the text element's value will repeat a lot, set a default value for the element. The default value will be prefilled when content creators add a new content item.
You can set regular expressions to make sure the element's value matches a specific pattern. Check out the examples of the patterns you can use:
- Email address:
- US phone number:
- Web URL:
To ensure your regex validates the whole value of the element, not just part of it, start it with
^ and end it with
$. For example, use
^[0-9]+$ to allow only numbers. If you'd use only
[0-9]+, any value with at least one number would pass the validation.
Once you add the regex pattern, write the validation description to help your content creators fill in correct values in content items.
Developers can also set custom validation rules with regular expressions for text elements using the Management API.
URL slug elements
By default, URL slug elements auto-generate their value based on a specified text element. For example, "Hello World" becomes "hello-world".
You can specify custom regular expressions for URL slug elements to make sure your URL slugs match a specific pattern, just like regular expressions in text elements.