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

Options "Publish to live" and "Export pages" share pages tree but layout IDs are different between staging and live sites

    Details

    • Fix Priority:
      4

      Description

      Steps to reproduce:

      1. Create a new site and activate staging.
      2. Add public pages with a similar organization:
      • Page A
      • Page B
      • Page C
        • Page C.1
      • Page D
      1. Add a Dictionary portlet (23) to "Page A".
      2. Add a Site Map portlet (85) to "Page B".
      3. Publish to live.
      4. Check in database that layout IDs are different for staging and live sites. For example:
        SELECT layoutId, parentLayoutId, name FROM Layout WHERE groupId = [groupId of staging site] order by layoutId;
        
        SELECT layoutId, parentLayoutId, name FROM Layout WHERE groupId = [groupId of live site] order by layoutId;
        
      5. Add a Navigation portlet (71) to "Page D".
      6. Add a new page "Page E" (same level that pages A, B, C and D).
      7. Add a Currency Converter portlet (16) to "Page E".
      8. From Staging, select "Publish to live". Click on "Change" in "Pages" section.
        • A tree is showed:
          • Page A
          • Page B
          • Page C
            • Page C.1
          • Page D
          • Page E
      9. Check nodes "Page A", "Page B", "Page D" and "Page E". Click "Ok".
      10. Click on "Choose Applications" in "Application Configuration" section. It shows a list of four portlets:
        • "Currency Converter"
        • "Dictionary".
        • "Navigation".
        • "Site Map".
      11. Cancel the publication process closing the window.
      12. Go to "Admin" menu and select "Pages" from "Site Administration".
      13. Click on "Export". Click on "Change" in "Pages" section.

      Expected behavior:

      1. A tree is showed:
        • Page A
        • Page B
        • Page C
          • Page C.1
        • Page D
      2. Check nodes "Page A", "Page B" and "Page D". Click "Ok".
      3. Click on "Choose Applications" in "Application Configuration" section. It shows a list of two portlets:
        • "Dictionary".
        • "Site Map".

          Because both portlets were published to live.

      Observed behavior:

      1. A tree is showed:
        • Page A
        • Page B
        • Page C
          • Page C.1
        • Page D
        • Page E
          Note that this tree is the same that staging's
      2. Check nodes "Page A", "Page B", "Page D" and "Page E". Click "Ok".
      3. Click on "Choose Applications" in "Application Configuration" section. It shows a list of two portlets:
        • "Dictionary".
        • "Site Map".

          Because both portlets were published to live.
      4. If pages tree HTML code is tested (with navigator's developer tools) it can be observed that every node references to staging site groupId. Example:
        <li class="tree-node" id="layoutsExportTreegroup ID of live sitefalse_layoutId_layout ID relative to staging siteplidnumbergroupIdgroup ID of staging site"
        <li class="tree-node" id="layoutsExportTree22701false_layoutId_1_plid_22729_groupId_22721">
        

      Conclusion:

      "Export pages" is building a pages tree with pages of staging instead of pages of live. But applications belong to live site.

      Correct tree node's HTML code:

      <li class="tree-node" id="layoutsExportTree22701false_layoutId_1_plid_22729_groupId_22701">
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                support-lep@liferay.com SE Support
                Reporter:
                sergio.alonso Sergio Alonso
                Participants of an Issue:
                Recent user:
                Esther Sanz
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  4 years, 6 weeks, 1 day ago

                  Packages

                  Version Package