Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-142162

As a page creator, I want to have different page variations per Site Variation based on Experiences

    Details

      Description

      Motivation

      Heavy users of the Staging feature may want to migrate from widget to content pages, finding out that not all the capabilities provided by Staging are supported, a for example, Site Page variations.

      The goal of this story is covering the need that Site Page Variations addresses, allowing users to have multiple versions of the same page tu be published in bulk through a Site Variation.

      Requirements

      • When Staging + Page versioning is enabled, it will be possible to create different versions of the same page for different Site variations
      • Each content page variation can have several experiences that will be only 

      Acceptance Criteria

      • Given a site where Staging with Page Versioning is enabled
      • When the user creates a content page
      • Then the user can see the Site Page variation dropdown from the view mode

      --

      • Given a site where Staging with Page Versioning is enabled
      • When the user creates a content page
      • Then the user can see the Site Page variation option from the kebab menu next to the Publish to live button

       --

      • Given a content page in the view mode with experience 1 and experience 2
      • When the user adds that page to another Site Page variation or creates a new site variation from the page
      • Then the new page includes only the default experience, that is shown by default

      --

      • Given a page that has two Site page variations
      • When the users selects any of the options available in the Site Page variation dropdown
      • Then the page changes accordingly

      • Given a content page that is included in two different site variations
      • When the user makes changes in the default experience
      • Then those changes "propagate" to all the variants of the page across site variations (that is, the default experience is the same for all page variations)

      -- 

      • Given a content page that is included in two different site variations
      • When the user makes changes in any of the experiences that is not the default
      • Then those changes /new experiences added or deleted are not "propagated" to all the variants of the page across site variations 

      [Moved to LPS-146398]

      • Given a page that belongs to one site variation
      • When the user changes the site variation from the Site Page variation dropdown
      • Then an alert shows:  The page Catalog is not enabled in New site variation, but is available for other pages variations.

      --

      [Tackled in LPS-95719]

      • Given a content page that is included in two different site variations (Page 1A and page 1B), with different experiences created in each variation 
      • When the pages have never been published and the user publishes the page 1A 
      •  Then only the experiences contained in the page 1A are published, while the page 1B remains as draft

      Test Scenarios

      Test Scenarios Test Strategy Kind of test Is it covered by FrontEnd ? (JS-Unit) Is it covered by BackEnd ? (unit or integration) Could it be covered by POSHI?
      The new site page variation only inherits the default experience Critical Manual TBD TBD Yes
      Only the changes from default experience will be propagated to all site page variations Critical Manual TBD TBD Yes
      The user could publish content page with experiences per site page variation Critical Manual TBD TBD Yes

        Attachments

          Issue Links

          1.
          Modify the LayoutCopyHelper API to allow publish the desired segments experiences LPS-143676 Technical Task Closed Product Team Echo  
          2.
          Don't show edit icon for incomplete pages LPS-143722 Technical Task Closed Eudaldo Alonso  
          3.
          Delete unnecessary method to get Data from LayoutPageTemplateStructure LPS-143726 Technical Task Closed Product Team Echo  
          4.
          Adds new layout set branch id column to segments experience table LPS-143727 Technical Task Closed SE Support  
          5.
          Creates new feature flag LPS-143825 Technical Task Closed SE Support  
          6.
          Take into account the different site page variations when we are ordering experiences LPS-143827 Technical Task Closed SE Support  
          7.
          Adds status columns to Layout Page Template Structure Rel LPS-143853 Technical Task Closed Eudaldo Alonso  
          8.
          Update segments experiences status when we are updating the page LPS-143871 Technical Task Closed SE Support  
          9.
          We should take into account the site page variation when we are adding a new experience LPS-143873 Technical Task Closed SE Support  
          10.
          When we are publishing to live, publish only the segments experience of the current site page variation LPS-143874 Technical Task Closed SE Support  
          11.
          Filter segments experiences by current site page variation LPS-143875 Technical Task Closed SE Support  
          12.
          Centralize layout update status when we are changing the editable values of a fragment entry link LPS-143942 Technical Task Closed Eudaldo Alonso  
          13.
          Improve segments experience priority LPS-151955 Technical Task Closed Product Team Tango  
          14.
          Delete segments experiences related data properly when we are copy layouts LPS-153453 Technical Task Closed Eudaldo Alonso  
          15.
          Test Scenarios Coverage | Test Creation LPS-142164 Technical Testing Closed Support QA  
          16.
          Page added to a Site variation without an explicit action LPS-145949 Impedibug Closed Support QA  
          17.
          Product QA | Test Validation - Round 1 LPS-156853 Technical Testing Closed Support QA  
          18.
          Product QA | UX Validation - Round 1 LPS-156854 Technical Testing Closed Support QA  
          19.
          Tests Automation LPS-156855 Technical Testing Closed Support QA  

            Activity

              People

              Assignee:
              support-qa Support QA
              Reporter:
              julia.molano Julia Molano
              Engineering Assignee:
              Julia Molano
              Recent user:
              David Gutiérrez Mesa
              Participants of an Issue:
              Backend Developer(s) Assigned:
              Eudaldo Alonso
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package