Deploy Content (Admin)

Want this feature?

Deploy Content is part of CV ecommerce's franchiser and multisite features. For implementation, contact Commerce Vision. All sits in the network must be on the same version (min. 2022.3).

Overview

A site in your organisation network can be both a source site and target site. A source site deploys content and a target site receives content. The Deploy Content feature allows flexibility in how your organisation configures specific sites. If your organisation also uses Content Lock to control content on multiple sites remotely, make sure this feature is enabled or disabled, depending on your business requirements.

For Administrator and Content Administrator roles

On this page:

Use Deploy Lock with Content Lock

A content type that is lockable, e.g., Article Locks, works with the Content Lock feature in a deployment. Lockable content type data must be in 'locked' status to be deployable.

Whether content managers on target sites can edit or delete deployed 'locked' content depends on whether their site has:

Content Lock ON - deployed content is locked. Content is locked from editing and deletion unless 'unlocked' status is deployed from the source site.
Content Lock OFF - deployed content is unlocked. Content can be edited and deleted by target site CMS users (as per their usual role permissions).

Source Site Admins

On a source site, CMS Administrators and Content Administrators can enable or disable deployment of specific content types and select target sites. Other roles can be given one or more specific permissions:

Manage Linked Sites - select/deselect target sites
Manage Deployed Content - select/deselect deployment content types
View Deployed Content - view but not edit or delete locked content deployed from a source

NOTE - Contact Commerce Vision to apply one or more permissions to a non-administrator role.

Target Site Admins

On a target site with Content Locked enabled, CMS Administrators and Content Administrators CANNOT edit or delete any locked content deployed from another site. To allow this content to be edited on the target site, the source site admin must re-deploy the content to unlock it.

Step-by-step Guide

1. Configure Deploy Content

The Deploy Content feature must be enabled by Commerce Vision. When enabled, Administrator and Content Administrator roles can select deployable content types and target sites.

In the CMS, go to Settings → Settings → Feature Management → Content → Deploy Content.

With the feature enabled, the Configure button is displayed. If disabled, the 'Contact to Enable' button is displayed.

Click Configure.

Toggle ON to Enable to make a content type(s) deployable from this site.

A content type with 'locks', e.g., Article Locks, works with the Content Lock feature for deployment. This content type's data can only be deployed in 'locked' status to target sites.
Deployed locked content on target sites:
Content Lock feature is ON - deployed content is locked. Content is locked from editing and deletion unless 'unlocked' status is deployed from the source site.
Content Lock feature is OFF - deployed content is unlocked. Content can be edited and deleted by target site CMS users (as per their usual role permissions).

To save your configurations, click Save.

2. Select Destination Sites

All CV ecommerce sites in your Organisation ID are listed. For successful deployment, a valid destination site must be on the same version as the source site. If invalid sites have been selected, an alert message appears at the top of the page.

On the Deploy Content Feature Settings page, scroll down to the Target Sites section.

All sites in your organisation, including test sites, are listed. Sites on the same version as your (source) site are marked with . Sites on incompatible versions are marked with .
(Optional) If your organisation has many sites, use the filter to look up all compatible or incompatible sites. For compatible sites, select 'is true', then click Filter.

To make a site a selectable target site during deployment, toggle ON Target Sites next to it.
Enable all compatible sites in one go

i. First use the filter (step 3) to display only compatible sites
ii. Toggle ON the Toggle All button.
NOTE - To ensure all incompatible sites are disabled, you can use the filter to display all incompatible sites, then toggle OFF Toggle All. IMPORTANT - If Toggle All is enabled before using the filter, all sites will be selectable during deployment. However, the system will fail a deployment when a target site is not on the same version as the source site.
Save your settings.