<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: When moving a page on Blueprint does not reflect on live copies in Adobe Experience Manager Questions</title>
    <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/when-moving-a-page-on-blueprint-does-not-reflect-on-live-copies/m-p/447601#M128110</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;LI-USER uid="17441488"&gt;&lt;/LI-USER&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is expected behaviour and&amp;nbsp;&lt;STRONG&gt;Moving&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;pages in a blueprint will&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;not&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;result in corresponding pages being moved in live copies after rollout with standard rollout configuration:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The reason for this behavior is that a page move implicitly includes a page delete. This could potentially lead to unexpected behavior on publish, as deleting pages on author automatically deactivates corresponding content on publish. This can also have a knock-on effect on related items such as links, bookmarks, and others.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;If you really want this behavior, then you need create custom rollouts. Please check below for more info.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://experienceleague.adobe.com/docs/experience-manager-65/administering/introduction/msm-best-practices.html?lang=en" target="_blank"&gt;https://experienceleague.adobe.com/docs/experience-manager-65/administering/introduction/msm-best-practices.html?lang=en&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 08 Apr 2022 11:24:07 GMT</pubDate>
    <dc:creator>Siva_Sogalapalli</dc:creator>
    <dc:date>2022-04-08T11:24:07Z</dc:date>
    <item>
      <title>When moving a page on Blueprint does not reflect on live copies</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/when-moving-a-page-on-blueprint-does-not-reflect-on-live-copies/m-p/447596#M128108</link>
      <description>&lt;P&gt;Hi all!&lt;/P&gt;&lt;P&gt;Hope you are doing fine!&lt;/P&gt;&lt;P&gt;We have managed "news" and "archived news" in a way that we move the pages from "news" parent to "archived news" parent. But, when we move a page from "news" to "archived news" on Blueprint, it does not reflect on Live copies. What are we doing wrong? Is this possible?&lt;/P&gt;&lt;P&gt;Also, is this the best way to manage this news and archived news logic?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 08 Apr 2022 11:04:58 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/when-moving-a-page-on-blueprint-does-not-reflect-on-live-copies/m-p/447596#M128108</guid>
      <dc:creator>AD-Engineer</dc:creator>
      <dc:date>2022-04-08T11:04:58Z</dc:date>
    </item>
    <item>
      <title>Re: When moving a page on Blueprint does not reflect on live copies</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/when-moving-a-page-on-blueprint-does-not-reflect-on-live-copies/m-p/447601#M128110</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;LI-USER uid="17441488"&gt;&lt;/LI-USER&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is expected behaviour and&amp;nbsp;&lt;STRONG&gt;Moving&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;pages in a blueprint will&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;not&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;result in corresponding pages being moved in live copies after rollout with standard rollout configuration:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The reason for this behavior is that a page move implicitly includes a page delete. This could potentially lead to unexpected behavior on publish, as deleting pages on author automatically deactivates corresponding content on publish. This can also have a knock-on effect on related items such as links, bookmarks, and others.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;If you really want this behavior, then you need create custom rollouts. Please check below for more info.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://experienceleague.adobe.com/docs/experience-manager-65/administering/introduction/msm-best-practices.html?lang=en" target="_blank"&gt;https://experienceleague.adobe.com/docs/experience-manager-65/administering/introduction/msm-best-practices.html?lang=en&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Apr 2022 11:24:07 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/when-moving-a-page-on-blueprint-does-not-reflect-on-live-copies/m-p/447601#M128110</guid>
      <dc:creator>Siva_Sogalapalli</dc:creator>
      <dc:date>2022-04-08T11:24:07Z</dc:date>
    </item>
    <item>
      <title>Re: When moving a page on Blueprint does not reflect on live copies</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/when-moving-a-page-on-blueprint-does-not-reflect-on-live-copies/m-p/447614#M128115</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Your LiveCopy content needs the Page Move rollout config on it.&amp;nbsp; It appears you have only the default config and you need to add page Move (moveAction) and have it trigger on rollout.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Apr 2022 12:13:44 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/when-moving-a-page-on-blueprint-does-not-reflect-on-live-copies/m-p/447614#M128115</guid>
      <dc:creator>PhaniRajuTanneru</dc:creator>
      <dc:date>2022-04-08T12:13:44Z</dc:date>
    </item>
  </channel>
</rss>

