Kentico Xperience 13 documentation and ASP.NET Core

Most documentation about running Xperience applications under ASP.NET Core can be found in a dedicated section: Developing Xperience applications using ASP.NET Core. The rest of the documentation still applies, but some code samples and scenarios might need slight modifications for Core projects.

All major differences between the MVC 5 and Core platforms are summarized in Migrating to ASP.NET Core.

×

Exporting objects

In addition to exporting websites, you can create export packages containing only selected objects (page types, users, etc.).

Exporting pages

The objects available for selection during export do not include individual pages within the content tree of sites. To export pages, you need to export entire sites with their full page tree.

Exporting selected objects

  1. Open the Sites application.
  2. Click Export in the page header. The Export wizard starts.
  3. Fill in the name of the export package and choose the object pre-selection type:

    OptionDescription

    File name

    Sets the name of the export package. The wizard creates a zip file containing the export data in the ~/CMSSiteUtils/Export folder.

    Preselect all objects

    Preselects all objects related to the site.

    Preselect objects changed after specific date

    Preselects all objects changed after the specified date.

    Use previous export settings

    Preselects objects based on the settings of a previous export.

    Tip: To clear the history of previous exports, open the Sites applications, click View export history among the header actions and delete the items on the History tab. Deleting export history items does not remove the corresponding packages from the file system.

    Select an option and click Next.

  4. Select which objects you want to export. The tree separates objects into categories according to the related functionality. Selecting a category opens a set of check boxes in the right part of the screen, allowing you to select which objects will be exported.

    See the Export - Object selection settings section for details.

    Selecting objects for export

  5. After making all required selections, click Next to proceed. A log appears, showing you the export progress. You can abort the export by clicking Cancel at any time. When the export finishes, a message appears at the top of the log, showing the full path to the exported file.

  6. Click Finish.

The system returns you to the Sites application. You can now copy the exported package into the ~/CMSSiteUtils/Import folder of the target installation of Xperience, and use the Import site or objects wizard described in Importing a site or objects.

Export - Object selection settings

The following options are available in the Object selection step of the Export wizard.

Select the root of the tree (All objects) to access the following general export settings:

Global selection

Load default selection

Preselects all objects based on your choices in Step 1 of the import wizard.

Select all objects

Selects all available objects.

Deselect all objects

Unselects all objects.

Export settings

Export tasks

If enabled, delete tasks (incremental deployment) will be included in the package.

Export files

Some database objects are linked with physical files stored on the file system inside the web project. If you check this option, such files will be exported along with the corresponding database objects.

Export global folders

If enabled, all files under the following folders will be added to the export package:

  • ~/CMSGlobalFiles/
  • ~/CMSScripts/Custom/
  • ~/Old_App_Code/Global/

Export custom assembly files

If enabled, custom assembly files (dlls) that store classes related to certain types of custom objects will be exported together with the given objects. Applies to form controls, translation services, payment options, integration connectors, scheduled tasks, advanced workflow actions, marketing automation actions, smart search analyzers, etc.

The system considers assemblies as custom if their name does not start with the CMS. prefix.

The following categories contain extra options to be set:

Custom tables

Export custom table data

If selected, custom table records (the actual data stored in the tables) will be exported along with the selected custom tables.

Pages

Export pages

If selected, pages will be exported.

Export page histories

If selected, histories of all exported pages will be exported.

Export page relationships

If selected, relationships of all exported pages will be exported.

Export page level permissions

If selected, page security settings made in the Pages application will be exported.

Forms

Export forms data

If selected, stored forms data will be exported together with the exported forms.

Export physical files

If selected, physical files saved within form records (if there are some) will also be exported.

Media libraries


Export media files

If selected, media files stored in the database will be exported.

Export physical files

If selected, physical media files stored in the file system will be exported. This option is not selected by default as it may result in extremely large export packages. Instead, it is recommended to transfer these physical files manually.

Modules
Seal the selected modules

If selected, the system seals the exported modules. When the modules are imported to another instance of Xperience, they will not be in development mode (i.e. it is not possible to edit the module's properties, or create new classes, UI elements, permissions and settings).

You cannot export a module again from instances where it is sealed.

If you have the Log export tasks setting enabled in Settings -> Versioning & Synchronization -> Staging, a list of object deletion tasks may be displayed at the bottom of the list. If you leave the boxes selected, the objects will be deleted after you import the package on the target server.


Was this page helpful?