Dynamic module settings

You can manage various configurations of dynamic modules, related to permissions, module settings, and the content items in the dynamic modules.

For example, you can define permissions for modules and their content items, configure sharing of modules in multisite environment, or include dynamic modules in the internal search of the website.

In addition, you can manage URL generation of both the modules and their content items.

Permissions for dynamic modules

Permissions for dynamic content items

You can set permission for dynamic content items of a certain type and you can set individual permissions for each field of a dynamic type. For example, some users can change the answer to an FAQ, others can only view it, but can create questions. To be able to set permissions for individual fields, you must have enabled this when Create a dynamic content type.

To change the permissions for all items of certain dynamic type, navigate to the page of this type under Content main menu. On your dynamic content type page, click  (Settings for <content type>) » Set permissions link in the right side of the page.
The Permissions page appears.

Sharing dynamic modules between multiple sites

Search indexes

For more information about including a dynamic module items in search indexes, see Create search indexes.

Dynamic content types support additional URLs for their items. When you change the title or the URL of an item, this is not going to break any existing links that navigate to it. When you open an item on the frontend, the URL that you set last is displayed.

This is also valid for content types that have hierarchical structure. The URL for an item is created by combining all of the parent item’s URLs. For example ~/page/item-1/item-2/item-3/item-4, where item-1 is parent of item-2, etc. For these scenarios keep in mind the following cases:

• If you change the URL of an item that is in the lowest level of the hierarchy, its previous URL continues to work.
  For example, if you have an item with URL ~/item-1/item-2 and change the URL of item-2 to item-2-edit . When you open item-2 on the frontend, its URL is ~/item-1/item-2-edit, but ~/item-1/item-2 is still active.
• If you change the URL of an item that has child items, the URLs of the child items are updated.
  For example, if you have an item with URL ~/item-1/item-2 and change item-1 to item-1-edit. When you open item-2 on the frontend, its URL is ~/item-1-edit/item-2, but ~/item-1/item-2 is still active.
• If you break the hierarchical structure of dynamic content types, prevents the hierarchical URLs.
  For example, if you have an item with URL ~/item-1/item-2 and detach the two content types so that both are on a one level of hierarchy. When you open item-2 on the frontend, its URL is ~/item-2, but ~/item-1/item-2 is still active.
• If you have hierarchical content types and a parent item has two or more URLs, when you a create child item, its URL is generated using the current URL of the parent.
  For example, if you have a parent item with URL ~/item-1 and change it to item-1-edit. When you create item-2 that is child of item-1, its URL is ~/item-1-edit/item-2. The URL ~/item-1/item-2 returns error 404 – page not found.