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

As a pages administrator I can convert a widget page to a content page automatically

    Details

      Description

      **Context

      Liferay 7.2 introduced the possibility of creating custom column layouts within Content Pages and adding widgets to them. Thanks to these functionalities, the large majority of cases where widget pages were being used is now better served by Content Pages. Furthermore Content Pages have powerful new capabilities including the use of fragments and personalization capabilities.

      However, for customers upgrading from older versions of Liferay will already have many sites with pages created as Widget Pages. In order to benefit from some of the new features they need to manually convert the pages.

      This Feature:

      In this Story, we aim to provide a new action within Pages Administration that allows a user to automatically convert a widget page into a content page. In order for this to be possible the page must meet certain criteria that makes the conversion possible. In particular, out of the box, the limitations are as follows:

      • The widget page must use one of the default layout templates
      • The widget page must not be set as customizable by end users
      • The widget page must not use the Nested Applications widget

      These limitations must be documented in Liferay's official documentation.

      In addition to the conversions supported out of the box, an API will be provided that allow 3rd party developers to support additional conversion cases. The API should have at least two methods (method names are tentative):

      • isConvertible(): Determines whether the converter can convert this page. If no registered converter can convert a page, the "Convert" action will not appear in the UI.
      • convert(): takes a layout object representation of the page and returns a representation of the converted page.

      Acceptance Criteria

      • Given an existing site with a widget page that does not meet the criteria, when the pages administrator clicks the three dot menu, then an option to convert the page should not appear.
      • Given an existing site with a widget page that meets the criteria, when the pages administrator clicks the three dot menu, then an option to convert the page should appear.
      • Given an existing site with a widget page that meets the criteria, when the pages administrator clicks the three dot menu and clicks the option to convert the page, then the page must be converted and the user should see the result in the list of pages along with a success message.
      • Given an existing site with a widget page that meets the criteria, when the pages administrator clicks the three dot menu and clicks the option to convert the page and there is a failure, then the user should be presented with an explanatory error message and the page should continue as a Widget Page without any modification.

      Design Deliverables

      This story does not require design deliverables since it does not require new UIs 

      Features that doesn't need to be implemented (yet)

      • Support for bulk conversion
      • Support for widget pages with one or more Nested Applications widgets
      • Support for previewing the result of the conversion from a Widget Page to a Content Page before accepting it as final

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              michael.williams Michael Williams (Inactive)
              Reporter:
              jorge.ferrer Jorge Ferrer
              Engineering Assignee:
              SE Support
              Recent user:
              Manoel Cyreno
              Participants of an Issue:
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  Master