某些 Creative Cloud 应用程序、服务和功能在中国不可用。
Ogledujete si pomoč za različico :
- 6.5
- 6.4
- 6.3
- 6.2
- Starejše različice
You can create a live copy from a page or blueprint configuration, then can manage inheritance and synchronization.
Create a blueprint configuration to identify an existing website that you want to use as the source for one or more live copy pages.
Opomba:
Blueprint configurations enable you to push content changes to live copies. See Live Copies - Source, Blueprints and Blueprint Configurations.
When you create a blueprint configuration, you select a template that defines the internal structure of the blueprint. The default blueprint template assumes that the source website has the following characteristics:
- The web site has a root page.
- The immediate child pages of the root are language branches of the web site. When creating a live copy, the languages are presented as optional content to include in the copy.
- The root of each language branch has one or more child pages. When creating a live copy, child pages are presented as a chapter that you can include in the live copy.
Opomba:
A different structure requires another blueprint template.
For example, the Geometrixx Demo Site has /content/geometrixx as a root page, and contains the language branches en, fr, de, es, it, ja, and zn. Each language branch contains chapters such as Products and Services.
After you create the blueprint configuration, you configure the following properties:
- Name: The name of the blueprint configuration.
- Description. (Optional) A description of the blueprint configuration. The description appears in the list of blueprint configurations to choose from when creating a site.
- Source Path: The path of the root page of the site that you are using as the source (blueprint).
- Thumbnail Image: (Optional) An image to associate with the blueprint configuration. The image appears in the list to choose from when creating a site.
When your blueprint configuration is used, you can associate it with a rollout configuration that determines how the live copies of the source/blueprint are synchronized. See Specifying the Rollout Configurations To Use.
-
Open the Tools console in the classic UI. (http://localhost:4502/miscadmin#/etc)
Opomba:
In the touch-optimized UI you can navigate to the classic UI Tools console using the rail entries Tools, Operations and then Configuration.
-
In the Create Page dialog, provide the following information
- Title: A title that identifies the blueprint configuration.
- Name: (Optional) A name to use in ithe URL. If left blank, the name will be derived from the Title property.
- Select the required template from the list provided.
Then click Create.
-
You can now use your blueprint configuration to create a new site and specify the rollout configurations to use.
You can create a live copy of any page or branch. When you create the live copy, you can specify the rollout configurations to use for synchronizing the content:
- The selected rollout configurations apply to the live copy page and its child pages.
- If you do not specify any rollout configurations, MSM determines which rollout configurations to use. See Specifying the Rollout Configuration To Use.
You can create a live copy of any page:
- Pages are that are referenced by a blueprint configuration,
- And pages that have no connection to a configuration.
- AEM also supports creating a live copy within the pages of another live copy.
The only difference is that availability of the Rollout command on the source/blueprint pages is dependent on whether source is referenced by a blueprint configuration:
- If you create the live copy from a source page that is referenced in a blueprint configuration, then the Rollout command will be available on the source/blueprint page(s).
- If you create the live copy from a source page that is not referenced in a blueprint configuration, then the Rollout command will not be available on the source/blueprint page(s).
Create a live copy using a blueprint configuration to create a site based on the blueprint (source) content. When you create a live copy from a blueprint configuration, you select one or more language branches of the blueprint source to copy, then you select the chapters to copy from the language branches. See Creating a Blueprint Configuration.
If you omit some language branches or chapters from the live copy, you can add them later; see Creating a Live Copy Inside a Live Copy (Blueprint Configuration).
Pozor:
When the blueprint source contains links and references that target a paragraph in a different branch, the targets are not updated in the live copy pages, but remain pointed to the original destination.
For example, a live copy is created from the Geometrixx Demo Site blueprint. Links in the Toolbar branch that target the Services branch are not updated in the live copy, and continue to target the original pages in the Geometrixx Demo Site.
When you create the site, provide values for the following properties:
- Initial Languages: The language branches of the blueprint source to include in the live copy.
- Initial Chapters: The child pages of the blueprint language branches to include in the live copy.
- Destination Path: The location of the root page of the live copy site.
- Title: The title of the root page of the live copy site.
- Name: (Optional) The name of the JCR node that stores the root page of the live copy. The defaut value is based on the title.
- Site Owner: (Optional)
- Live Copy: Select this option to establish a live relationship with the source site. If you do not select this option, a copy of the blueprint is created but is not subsequently synchronized with the source.
- Rollout Configs: (Optional) Select one or more rollout configurations to use for synchronizing the live copy. By default, the rollout configurations are inherited from the blueprint; see Specifying the Rollout Configurations to Use for more details.
When you create a live copy inside the existing live copy (created using a blueprint configuration), you can insert any language copy or chapters that were not included when the live copy was originally created.
For example, after you created a live copy of the Geometrixx Demo Site blueprint having specified that only the English languge copy is included in the live copy and only a sub-set of the English chapters.
The properties of a live copy page show the following information about the live copy:
- Source: The source page of the live copy page.
- Status: The synchronization status of the live copy. The status includes whether the live copy is up to date with the source, and when the last synchronization occurred and who performed the synchronization.
- Configuration:
- Whether the page is still subject to live copy inheritance.
- Whether the configuration is inherited from the parent page.
- Any rollout configurations that the live copy uses.
Blueprint pages (that are referenced in a blueprint configuration) provide you with a list of the live copy pages that use the current (blueprint) page as the source. Use this list to keep track of the live copies. The list appears on the Blueprint tab of the page properties.
Roll out a blueprint page to push content changes to live copies. A Rollout action executes the rollout configurations that use the On Rollout trigger.
Opomba:
Conflicts can occur if new pages with the same page name are created in both the blueprint branch and a dependent live copy branch.
Such conflicts need to be handled and resolved upon rollout.
-
In the Sites console, select the page in the blueprint and open the References panel (from the toolbar).
Opomba:
Synchronizing executes the rollout configurations that use the On Rollout trigger.
To change live copy content, you can:
- Add parapraphs to the page.
- Update existing content by breaking the live copy inheritance for any page or component.
Opomba:
If you manually create a new page in the live copy, then it is local to the live copy, meaning it does not have a corresponding source page to attach to.
The best practice to create a local page that is part of the relationship would be to create it in the source and to do a (deep) rollout. That will create the page locally as live copies.
Opomba:
Conflicts can occur if new pages with the same page name are created in both the blueprint branch and a dependent live copy branch.
Such conflicts need to be handled and resolved upon rollout.
Add components to a live copy page at any time. The inheritance status of the live copy and its paragraph system does not control your ability to add components.
When the live copy page is synchronized with the source page, the added components remain unchanged. See also Changing the Order of Components on a Live Copy Page.
When you create a live copy, the live copy configuration is saved on the root page of the copied pages. All child pages of the root page inherit the live copy configurations. The components on the livecopy pages also inherit the live copy configuration.
You can suspend the live copy inheritance for a live copy page so that you can change page properties and components. When you suspend inheritance, the page properties and components are no longer synchronized with the source.
Opomba:
You can also detach a live copy from its blueprint to remove all connections. The Detach action is permanent and non-reversible.
Suspending live copy inheritance for a page is a temporary action. Once suspended the Resume action becomes available to re-instate the live relationship:
Opomba:
When you re-enable inheritance, the page is not automatically synchronized with the source. You can manually request a synchronization if this is required.
On an existing live copy you can change the depth for a page; i.e. whether child pages are included.
- Switching to a shallow live copy:
- Will have immediate effect and is non-reversible.
- Child pages are explicitly detached from the live copy. Further modifications on children cannot be preserved if undone.
- Will remove any descendant LiveRelationships even if there are nested LiveCopies.
- Will have immediate effect and is non-reversible.
- Switching to a deep live copy:
- Child-pages remain untouched.
- To see the effect of the switch, you can make a roll-out, any content modifications are applied according the roll-out configuration.
- Child-pages remain untouched.
- Switching to a shallow live copy, then back to deep:
- All children of the (formerly) shallow live copy are treated as if they had been created manually and are therefore moved away using [oldname]_msm_moved name.
-
In the Configuration section, set or clear the Live Copy Inheritance option depending on whether child pages are included:
- checked - a deep live copy (the child pages are included)
- clear - a shallow live copy (child pages are excluded)
Pozor:
Switching to a shallow live copy will have immediate effect and is non-reversible.
See Live Copies - Composition for more information.
Cancel the live copy inheritance for a component so that the component is no longer synchronized with the source component. You can enable inheritance at a later point if required.
Opomba:
When you re-enable inheritance, the component is not automatically synchronized with the source. You can manually request a synchronization if this is required.
To enable inhertance for a component, click or tap the Re-enable Inheritance icon on the component toolbar.
If a live copy contains components that are part of a paragraph system, inheritance of that paragraph system adheres to the following rules:
- The order of components in an inherited paragraph system can be modified, even with inheritance established.
- On rollout, the order of the components will be restored from the blueprint. if new components were added to the live copy before rollout, they will be reordered along with the components above which they were added.
- If inheritance of the paragraph system is cancelled, the order of components will not be restored on rollout and will remain as is in the live copy.
Opomba:
When reverting a cancelled inheritance on a paragraph system, the order of components will not be automatically restored from the blueprint. You can manually request a synchronization if this is required.
The page properties of a Live Copy page are inherited (and not editable) from the source page by default.
You can cancel inheritance for a property when you need to change the property value for the live copy. A link icon indicates that inheritance is enabled for the property.
When you cancel inheritance, you can change the property value. A broken-link icon indicates that inheritance is cancelled.
Opomba:
When you re-enable inheritance, the live copy page property is not automatically synchronized with the source property. You can manually request a synchronization if this is required.
To enable inhertance for a property, click or tap the Revert Inheritance icon that appears next to the property.
Reset a live copy page to:
- Remove all inheritance cancellations and
- Return the page to the same state as the source page.
Resetting affects changes that you have made to page properties, the paragraph system and components.
Detach permanently removes the live relationship between a live copy and its source/blueprint page. All MSM-relevant properties are removed from the live copy and the live copy pages become a standalone copy.
Pozor:
You cannot reinstate the live relationship after you detach the live copy.
To remove the live relationship with the option of later reinstating it, you can cancel live copy inheritance for the page.
-
When this operation is performed on a sub-page (or branch) within a live copy the live relationship is removed for that sub-page (or branch) and the (sub-)pages in the live copy branch are treated as if they had been manually created.
However, the sub-pages are still subject to the live relationship of the parent branch so a further rollout of the blueprint page(s) will both:
- Rename the detached page(s):
- This is because MSM considers them as manually created pages that cause a conflict as they have the same name as the livecopy pages it is trying to create.
- Create a new (livecopy) page with the original name, containing the changes from the rollout.
Opomba:
See MSM Rollout Conflicts for details of such situations.
- Rename the detached page(s):
