EXAMPLE: If you want to export the News module, together with its content items, Sitefinity CMS will export the items from the default provider for News. If your News module is also setup to use items from another provider, they will not be exported. For more information, see Configure the modules of a site.
EXAMPLE: You have a multisite Sitefinity CMS instance that has Site A and Site B and you want to install an add-on that creates a dynamic module ABC and imports some dynamic content types. When you install the add-on, the following content providers are automatically created: Site A ABC, which is associated with Site A and Site B ABC, which is associated with Site B. When you activate the add-on on Site A, the content items are imported in provider Site A ABC. To use the items in Site B, you should configure its ABC dynamic module to use data from provider Site A ABC. For more information, see Share content providers of modules.
If in the add-on, you have custom code that uses DynamicModuleManager, you should use providers in the following way:
This ensures that DynamicModuleManager always works with the correct provider for the current website.
All related data and media fields are updated to work with the Default site source.
EXAMPLE: In Site A, you create a custom related image field to the News module. The field is setup to work with the images provider of Site B. You then export the News module in an add-on. When you install the add-on in Site C, the custom field is updated to work with the default provider for images in Site C.
Default page templates are not exported.
Dependencies, such as dependencies between modules and related data, related media, and classification fields, between pages and page templates, are not exported automatically, if not selected for export.
You must select all dependent modules.
For more information, see Dependency of exported items.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important