| 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
Terminology
Content Administrator
CMS Admin role created for the Content Lock & Deploy Content features that Multisite Content Management (MCM). This Role can enable/disable locking for content types Content Lock and Deploy Content in Feature Settings. It can also add linked sites so that they can be selected as target sites. NOTE - The general Administrator role also has these abilities. See also: Content Manager
Content Deployment Log
The page that contains a record of all deployment instances and whether each was successful or not. 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
ItemTop level item that can be locked (if lockable) deployed. Example: a whole page or templateitem
A lockable or deployable unit. Some content items are complex and contain other content items. For example, a whole page/template is a complex content item made up of other content items such as widgets and its layout. We can lock and/or deploy the whole page or just one or more of its content items.
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.ecommerce MCM function that allows some content types to be lockable.
Content Manager
A CMS user role that allows users to view, lock/unlock and deploy content but no administrative right to enable or disable MCM features.
Content type
How content objects for the Lock and Deploy feature are organised at the top level. It closely follows the CMS navigational menuitems are grouped. Content type organisation closely follow the arrangment of menu items in the CMS. Examples of content typestype: Pages & Templates, Articles, Campaigns, Products
Data
itemAn object beneath the level of content type that is a deployable unit
Deploy button
Thetype
A data type contains one or more content items. It is a useful term for understanding the deployment of Product and Category content items. These are not deployed individually but in data type groups. For example, a product data type is SEO Fields. It contains several content items, e.g., SEO Fields includes the 'SEO URL', 'Meta Page Title', etc. To deploy any of these items, the data group must be deployed.
Deploy button
A button usually located at the top of the screen that allows deployment of the whole displays when a top level content item can be deployed.
Deploy option
The A Deploy item from the Options menu that allows deployment of the data item at a specific level (usually below the Content item level)displays so that a specific content item in a complex content item can be deployed. Example: Selecting the Deploy item on a locked widget's Options menu will deploy only the widget and not the whole template.
Deployment
The action event of copying over content from a source CV site to a target CV site.
Deployment instance
One count of In a deployment event. where , one or more data content items are deployed to a target CV site from a source siteone or more target sites.
Deployment modal
The deployment popup screen where deployment takes place. Example: Anchor
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 Linked site
CV ecommerce sites grouped under one organisation on the CV ecommere platform. Only linked sites can be added as target sites.
Lockable content
Content types with items that can be locked. Not every content types have type is 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.Locked status
When a lockable content item is locked. On a single site, locked status restricts editing and deletion to CMS users with the Admin or Content Admin roles. On a target site, no CMS user can edit deployed locked content items. Admins on the source site can unlock the content item by re-deploying the item in unlocked status.
Source site
A CV website where data is deployed from.
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 on the source site and deploy. This will deploy only the unlocked status.
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
On this pageTerms:
|
Deployment Result Messages
There are two levels of deployment result messages for each deployment event:
- for a target site
- for result of the whole deployment event (was the whole deployment to all target sites successful?)
- result of 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 (per site) (was all content/data items deployed on a target site?)
Deployment event result
A deployment event can have one or more deployment instances depending on whether there is one target site or multiple target sites.
Anchor failed failed
Failed deployment
| failed | |
| failed |
Single target site: At least one item cannot be successfully copied over 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 linkedMultiple target sites: Nothing was copied over to any selected sites.
Partially successful
multiple linked sites -all changes to data types of selected data type(s) and items were successfully deployeddeployment
Single target site: n/a
Multiple target sites: All items were successfully copied over to at least one
site but also failed fortarget site, AND at least one item failed to be copied over to at least one other target 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.
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 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.
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.
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.
Click Next.
To check deployment results:
In the CMS, go to Content → Advanced Content → Content Deployment Log.
Use the Search tool to find the deployment instance.
Additional Information
| Multiexcerpt | ||||
|---|---|---|---|---|
| ||||
Minimum Version Requirements
| Multiexcerpt | ||
|---|---|---|
| ||
4.38 |
| Multiexcerpt | ||
|---|---|---|
| ||
Implementation by Commerce Vision |
| Multiexcerpt | ||
|---|---|---|
| ||
No |
| Multiexcerpt | ||
|---|---|---|
| ||
Content |
| Multiexcerpt | ||
|---|---|---|
| ||
Yes |
| Multiexcerpt | ||
|---|---|---|
| ||
Both |
| Multiexcerpt | ||
|---|---|---|
| ||
| n/a |
Related help
| Anchor | ||||
|---|---|---|---|---|
|
Single target site: All content/data items were successfully copied over to the target site.
Multiple target sites -All content/data items were successfully copied over to all target sites.
Content/Data items results (per site)
If errors are encountered during the deployment of specific data items to a target site, each error is logged. If there are data errors for a specific site, deployment will be flagged as 'failed' near the bottom of the Content Deployment Log page. A More Info button provides access to the specific errors found.Related Resources
| Content by Label | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Content by Label | ||||||||
|---|---|---|---|---|---|---|---|---|
|