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

Investigate if we can stop publishing assets configured to display portlets

    Details

    • Type: Spike
    • Status: Closed
    • Priority: Minor
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Staging
    • Conclusion:
      Hide
      We need to create at least 2 stories and probably 1 epic then:

      1. Implement the check for publishing/ignoring contents that the listed display portlets... uhhmm... display.
      2. Implement to check if the preference of a display portlet has been changed from the last publish date. If yes, we need to publish the displayed content also even if that has not bee changed to prevent errors.
      3. Refactor the framework to make that possible
        a. to collect all the contents and prevent missing references occuring and
        b. to be able to give a collected output of the problems to the end user during the publishing.
      Show
      We need to create at least 2 stories and probably 1 epic then: 1. Implement the check for publishing/ignoring contents that the listed display portlets... uhhmm... display. 2. Implement to check if the preference of a display portlet has been changed from the last publish date. If yes, we need to publish the displayed content also even if that has not bee changed to prevent errors. 3. Refactor the framework to make that possible   a. to collect all the contents and prevent missing references occuring and   b. to be able to give a collected output of the problems to the end user during the publishing.
    • Sprint:
      StagingIter12 - Dagobert bácsi

      Description

      Display portlets publish the content over and over again. In a typical customer scenario, the content is already published to Live. However when the pages are published, the display portlets fetch the content and export/import it. This can slow down the process significantly.

      In a typical use case, only a few new content is created since the last publication, so it is expected that the publication happens almost immediately.

      Similarly how we have been changed this behaviour at the Asset Publisher (LPS-128736) we want to change the behaviour at other display portlets also.

      For that we need to investigate all the display portlets what we can do. In generally, we want to know if we can push the stress to asset based publishing instead of portlet base publishing.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              zsigmond.rab Zsigmond Rab
              Reporter:
              zsigmond.rab Zsigmond Rab
              Engineering Assignee:
              Tamas Molnar
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package