Rollout config | Community
Skip to main content
Krishna_C
Krishna_C
Level 3
October 16, 2015
Solved

Rollout config

  • October 16, 2015
  • 8 replies
  • 2178 views

Hi,

 
I am creating live copies using an existing page.This page has larger number of child pages(immediate level) to it.Now i want to inherit the properties only to the child pages .Since I have many child pages I cannot set the rollout config for each of them.
 
Is there any option such that I can restrict inheritance only to children?
 
Even inheritance only for a particular type of template also helps,do we have any such option ?
 
Regards,
Krishna
    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Scott_Brodersen

    On the MSM docs page, I added a link to the custom action page :)

    As the example custom liveaction shows, you can access the source node and check the node properties. The page's jcr:content node has the property cq:Template...

     

    scott

    8 replies

    smacdonald2008
    smacdonald2008
    Level 10
    October 16, 2015

    Here is the documentation topic on this subject:

    http://dev.day.com/docs/en/cq/current/administering/multi_site_manager.html

    Here is a community article that may help as well:

    http://aempodcast.com/2013/live-copy/live-copy-and-msm-custom-configuration/

    Hope these topics help. 

      Scott_Brodersen
      Scott_Brodersen
      Level 8
      October 16, 2015

      Hi Krishna,

      I don't quite understand your situation. The source page has many children, but I don't understand which properties you do not want to inherit.

      At any rate, if you have some exceptional rollout requirements, you can create custom synchronization actions and use them with your rollout configuration:

      https://dev.day.com/docs/en/cq/current/developing/multi_site_manager_dev.html#Creating%20a%20New%20Synchronisation%20Action

       

      scott

      Krishna_C
      Krishna_CAuthor
      Level 3
      October 16, 2015

      Hi Scott,

      I am using content update action and I have no exclude properties as i need all the titles and properties to get populated.But this should effect only my child pages.But When I am creating a new live copy even the parent page title gets populated which I am not interested in.So i thinking whether I could restrict copy at template level.Is there any possibility to restrict copy at page level (Not only for the above scenario but I may need it further ) 

      Thanks for sharing the link on creating a new sync action,I have been searching  for it  :)

      Can I add restrictions at template level by configuring new sync action?

      Krshna

      Krishna_C
      Krishna_CAuthor
      Level 3
      October 16, 2015

      Hi,

      Thanks for the reply.I had already went through them.But I could find any thing related to restricting replication at template level.I need some thing like changes should be populated across a particular template type.

       

      Krishna

      S
      sudeep_srivasta
      Level 2
      October 16, 2015

      Hey,

      I followed follwing link for creating LiveAction, at the last of the link it was mentioned that the liveaction would be called everytime a page is activated that is created using Livecopy.

      http://docs.adobe.com/docs/en/cq/current/developing/multi_site_manager_dev.html

      This does not holds true for me. LiveAction class is called only once, as soon as i click create livecopy button.

      I wanted to call it before/after live copy of each page is created.

      Would appreciate any help.

      Scott_Brodersen
      Scott_BrodersenAccepted solution
      Level 8
      October 16, 2015

      On the MSM docs page, I added a link to the custom action page :)

      As the example custom liveaction shows, you can access the source node and check the node properties. The page's jcr:content node has the property cq:Template...

       

      scott

        Scott_Brodersen
        Scott_Brodersen
        Level 8
        October 16, 2015

        Perhaps you could perform the rollout for all, and the custom sync action checks the template type, and if it's not the right type then don't do anything.

        Krishna_C
        Krishna_CAuthor
        Level 3
        October 16, 2015

        Scott Brodersen wrote...

        Perhaps you could perform the rollout for all, and the custom sync action checks the template type, and if it's not the right type then don't do anything.

         

        Thanks Scott I will try that .

        Terms & ConditionsAccessibility statement

        Loading footer...