| Info | ||
|---|---|---|
| ||
Content Lock and Deploy Content are part of the CV ecommerce platform's multisite features. Source and target sites must be on the same version (min. 2022.3). CV: 105298 |
Terms
Content Administrator
Admin role created for the Content Lock & Deploy Content features that can enable/disable locking for content types and Deploy Content in Feature Settings. NOTE - The general Administrator role also has these abilities.
Content Deployment Log
The page that contains a record of all deployment instances. The log keeps deployment data for the last 6 months. (Go to: Content → Advanced Content → Content Deployment Log.)
| Expand | ||
|---|---|---|
| ||
Go to: Content → Advanced Content → Content Deployment Log.
|
Content Item
Top level item that can be locked (if lockable) deployed. Example: a whole page or template
Content Lock
The CV lock feature that protects a locked content or data item from being edited or deleted by non-Admin CMS roles on the same site or when deployed, any role on the target site.
Content type
How content objects for the Lock and Deploy feature are organised at the top level. It closely follows the CMS navigational menu. Examples of content types: Pages & Templates, Articles, Campaigns, Products
Data item
An object beneath the level of content type that is a deployable unit
Deploy button
The button usually located at the top of the screen that allows deployment of the whole content item.
Deploy option
The Deploy item from the Options menu that allows deployment of the data item at a specific level (usually below the Content item level).
Deployment
The action of copying over content from a source CV site to a target CV site.
Deployment instance
One count of a deployment event. where one or more data items are deployed to a target CV site from a source site.
Deployment modal
The deployment popup screen where deployment takes place.
Failed deploymentAnchor failed failed
A deployment event where at least one data item sent to a target CV site was not copied over successfully. Where more than one target site was selected, the deployment result to each target site will be logged as 'Content Lock & Deploy Content Glossary' or 'failed'.
Lockable items
Content and data items that can be locked. Not every content types have lockable items.
Partially successful deployment
When more than one target sites were selected, all items were successfully copied over to at least one site but on at least one other target site, at least one item failed to be copied over.
Source site
A CV website where data is deployed from.
| Anchor | ||||
|---|---|---|---|---|
|
A deployment event where all data items sent to a target CV site were copied over successfully. Where more than one target site was selected, the deployment result to each target site will be logged as 'successful' or 'Content Lock & Deploy Content Glossary'.
Target site
A CV website where data is deployed to.
Unlocked status
A lockable item that is unlocked for editing. To unlock a deployed locked item on a target site, unlock the locked item and deploy. This will deploy only the unlocked status.
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
On this page:
|
Deployment Result Messages
There are two levels of deployment result messages:
- for a target site
- for the data items sent
Result Messages
Successful
- single linked site - all changes to selected data type(s) and items have been deployed on the destination site.
- multiple linked sites - all changes to selected data type(s) and items have been deployed on all destination sites.
Failed
- single linked site - at least one change to selected data type(s) and items cannot be deployed and the whole deployment instance was cancelled. Nothing was deployed to the selected linked site.
- multiple linked sites - at least one change to selected data type(s) and items cannot be deployed on all sites and all deployment instances were cancelled. Nothing was deployed to all selected linked sites.
Partially successful
- multiple linked sites -all changes to data types of selected data type(s) and items were successfully deployed to at least one site but also failed for at least one site.
Add linked sites
Sites that share an organisation Id are treated as in a network. You may not always want to deploy a set of changes to all available sites. What sites a deployment instance can select from is set in Feature Settings.
To add sites that content can be deployed to:
- Go to Settings → Settings → Content → Linked Sites.
- Click Configure.
- Scroll down to the Sites section.
- Toggle on one or more sites from the available sites.
- Click Save.
Deploying lockable objects
The contents of a lockable object must be in locked status to be deployable. if unlocked, only the unlock status is deployed. This is used to allow users on linked sites to edit content. You'll know when an object is deployable by the displayed Deploy button or link under Options. If your site uses Page Preview and an object is deployed before Publishing, it will be deployed in the Draft mode.
- Go to the locked object.
- Locate the Deploy button and click it.
- In the Deploy modal, select individual objects to deploy or toggle Select All.
- Click the Next button.
- Select one or more available deployment sites.
- Click Next.
- Check the summary of items to be deployed.
- To confirm deployment, click Deploy.
- Check the deployment results. NOTE - The result for each individual site is displayed separately.
- You can check the deployment details for more information. On the Results modal, click the link.
- Check the deployment details. You can enter notes about the deployment.
Deploying non-lockable objects
Non-lockable objects need additional setting to be enabled for deployment.
To deploy a non-lockable object:
- In the CMS, go to Settings → Settings → Content → Linked Sites.
- Click Configure.
- In Linked Sites Feature Settings, toggle ON the feature type(s) you want to deploy.
- Click Save.
Deploying Role Settings
Role settings changes are deployed from the Deployment section of the Linked Site Feature Settings page.
To deploy Role changes:
- In the CMS, go to Settings → Settings → Content → Linked Sites.
- Click Configure.
- In Linked Sites Feature Settings, toggle ON Enable Role Deployment.
- Click the Deploy button displayed.
- In the Deploy modal, select one or more Roles to deploy.
- Click Next.
- Select the linked sites for deployment.
Anchor deployment-log deployment-log
Viewing Deployment History & Results
| deployment-log | |
| deployment-log |
To check deployment results:
- In the CMS, go to Content → Advanced Content → Content Deployment Log.
- Use the Search tool to find the deployment instance.
- Click Edit for the deployment instance you want to view.
Additional Information
| Multiexcerpt | ||||
|---|---|---|---|---|
| ||||
Minimum Version Requirements |
| |||||
|---|---|---|---|---|---|---|
| Prerequisites |
| |||||
| Self Configurable |
| |||||
| Business Function |
| |||||
| BPD Only? |
| |||||
| B2B/B2C/Both |
| |||||
| Third Party Costs |
|
Related help
| Content by Label | ||||||||
|---|---|---|---|---|---|---|---|---|
|