Modules supported for export

You can create an add-on from the following system elements:

  • Static modules
    You can export only active modules.
    You can export the following static modules: Blogs and blog posts, Content blocks, Events, Forms, Lists and List items, and News.
    For static modules, the following elements are exported:
    • Custom fields
    • View definitions (part of the config files that are exported)
    • Widgets and widget templates
      Sitefinity CMS exports all modified and new widget templates of static modules.
    • Content items
      Sitefinity CMS exports all content for a given type without granular selection.
  • Static media modules and their libraries
    You can export either all media modules (images, videos, and documents), or none of them. You can export only active modules.
    For static media modules, the following elements are exported:
    • Custom fields
    • View definitions (part of the config files that are exported)
    • Widgets and widget templates
      Sitefinity CMS exports all modified and new widget templates of media modules.
    • Libraries and their items
      Sitefinity CMS exports all content for a given media type without granular selection.
  • Dynamic modules
    You can export only active modules.
    For dynamic modules, the following elements are exported:
    • The dynamic module and its types
      When you export a dynamic module, you export all of its types.
    • View definitions (part of the config files that are exported
    • Dynamic widgets and widget templates
      Sitefinity CMS exports all widget template of the dynamic modules that have been selected for export.
    • The content items of all types
  • Classifications
  • Pages
    You can export either all pages, or none.
    Only pages in status Published are exported.
  • Custom Page templates
    All page templates different than the default ones are exported.
    Only pages in status Published are exported.
  • Web services
    You can export either all created web services, or none. Both active and inactive web services are exported.
    These are the web services created with Sitefinity CMS Web services module.
    For more information, see Create a web service.
  • User profiles
    You can export either all or none of the created user profiles.
    The export includes any created custom profile types and any custom fields added to the Basic profile type. The export does not include the field values, because they are part of the users’ data, and users are not exported.

Dependency of exported items

When you export an item, you should make sure that you export any dependent types, modules, or widgets.

  • Pages depend on their page templates
    For example, if you want to export pages that are based on a custom template, together with Pages, you should also export Page Templates.
  • Related data or media custom fields depend on their custom types.
    For example, if a static or a dynamic module has a custom images field, together with the module, you should also export Libraries.
  • Classifications custom fields depend on classification.
    For example, if a static or a dynamic module has a custom categories field, together with the module, you should also export Classifications.

Export custom functionality

Custom functionality is not automatically exported. However, you can still manually include it in the add-on. Such custom functionality may include a custom module, custom widget, custom HTTP handlers, custom web service, etc.

PREREQUISITES: You should develop custom functionality in a separate project and then manually reference it from the .nuspec file. By referencing it from the .nuspec file, you include it in the NuGet package and then distribute it with the add-on.

Was this article helpful?

Next article

Limitations of add-ons