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

As a portlet developer I can provide independent portlet settings at the portal instance, site and portlet instance levels

    Details

      Description

      Currently developers need to choose whether the portlet configuration is "owned" by the layout (portlet instance), site or company (portal instance). Furthermore, the configuration can also be "owned" by a user which conflicts with the concept of user preferences. All of this makes the API complicated and error prone.

      This Story proposes to simplify the current system and at the same time provide more flexibility to portlet developers. It will also allow setting default configurations everywhere it makes sense (depending on the scope of the configuration) instead of forcing all defaults to be a in a global portlet-custom.xml file.

      Finally, it will also allow for UX improvements in follow up stories.

        Attachments

          Issue Links

          1.
          Provide API to allow retrieving and setting portlet configuration and defaults at company, site and portlet instance level Technical Task Closed Brian Chan  
          2.
          Refactor Message Boards to use the new API for configuration Technical Task Closed Jorge Ferrer  
          3.
          Separate Portlet Settings from Service Settings Technical Task Closed Brian Chan  
          4.
          Move site level portlet configuration from the portlet wrench icon to site administration Technical Task Closed Brian Chan  
          5.
          Develop tests for PortletPreferencesLocalService Technical Task Closed Jorge Ferrer  
          6.
          Make it easier to access portlet settings Technical Task Closed Brian Chan  
          7.
          Refactor Blogs to leverage the new Portlet Settings API Technical Task Closed Jorge Ferrer  
          8.
          Include portletResource in portletDisplay Technical Task Closed Brian Chan  
          9.
          Upgrade Message Boards preferences to the new Service Settings Technical Task Closed Sergio Gonzalez (Inactive)  
          10.
          Introduce portlet specific settings wrapper to encapsulate settings related logic in Message Boards Technical Task Closed Brian Chan  
          11.
          Move preferences from message boards portlet-custom to portal.properties Technical Task Closed Brian Chan  
          12.
          Refactor Wiki to use the new API for configuration Technical Task Closed Brian Chan  
          13.
          Add decorators and base classes to portal-settings to standardize its use Technical Task Closed Brian Chan  
          14.
          Convert SettingsParamUtil into a Settings wrapper to avoid mismatch of default values Technical Task Closed Brian Chan  
          15.
          Make WikiSettings, DLSettings, etc not implement the Settings interface Technical Task Closed Brian Chan  
          16.
          Find a solution for "gatekeeper" like settings Technical Task Closed SE Support  
          17.
          Remove "default" owner types Technical Task Closed Brian Chan  
          18.
          Provide API to retrieve and set default settings for portlet instances and services Technical Task Closed Brian Chan  
          19.
          Adapt shopping portlet to the new settings API Technical Task Closed Jorge Ferrer  
          20.
          Abstract fallback keys into a FallbackKeys class Technical Task Closed Brian Chan  
          21.
          Add support for ${resource:URI} values inside properties files Technical Task Closed Brian Chan  
          22.
          Add support for localized values in Settings Technical Task Closed Jorge Ferrer  
          23.
          Add support for reset() method in Settings Technical Task Closed Brian Chan  
          24.
          Split DefaultConfigurationAction into two versions: one for PortletPreferences and another for Settings Technical Task Closed Brian Chan  
          25.
          Refactor DM to leverage the new Settings API Technical Task Closed Brian Chan  
          26.
          Adapt ConfigurationImpl classes to SettingsDefaultConfigurationAction wherever possible Technical Task Closed Ivan Zaera  
          27.
          Fix some bugs which cause some values not to be saved when the user configures them Technical Task Closed Brian Chan  
          28.
          Standardize handling of localized values for default portal locale Technical Task Closed Ivan Zaera  
          29.
          Move portlet instance specific properties to portlet configuration (as opposed to service configuration) Technical Task Closed SE Support  
          30.
          Refactor Bookmarks to leverage the new Settings API Technical Task Closed Brian Chan  
          31.
          Clean up PropsValues which have been migrated to Settings Technical Task Closed Brian Chan  
          32.
          Allow administrators to define all default values from portal.properties Technical Task Closed Brian Chan  
          33.
          Add methods to support import/export Technical Task Closed Mate Thurzo (Inactive)  
          34.
          NoSuchGroupException when trying to obtain PortletInstanceSettings Technical Task Closed Brian Chan  
          35.
          Provide a method to obtain the default settings used by any given Settings object Technical Task Closed Brian Chan  
          36.
          Add the necessary methods to the API to support archived portlet setups Technical Task Closed Jorge Ferrer  
          37.
          Change all boolean getters prefix from get to is in high level XXXSettings Technical Task Closed Brian Chan  
          38.
          Stop using PropsValues and PropsUtil in blogs, message boards, wiki, doclib and shopping portlet Technical Task Closed SE Support  
          39.
          Reorganize portal.properties to separate values into service and portlet sections Technical Task Closed Brian Chan  
          40.
          Modify the Archived Setups JSPs and action to use the Settings API, extending it as necessary Technical Task Closed Brian Chan  
          41.
          Test upgrade process from portlet preferences to settings Technical Task Closed Brian Chan  
          42.
          Refactor fallback keys registration in SettingsFactory to avoid errors in future implementations of high level Settings Technical Task Closed Jorge Ferrer  
          43.
          Refactor multiple value keys registration with ConfigurationActionImpl classes Technical Task Closed Jorge Ferrer  
          44.
          Make an upgrade process for all multi value keys of portlet preferences Technical Task Closed Jorge Ferrer  
          45.
          Review handling of all multi value settings in ConfigurationActionImpl classes Technical Task Closed Jorge Ferrer  
          46.
          Create an upgrade process for archived setups Technical Task Closed Brian Chan  

            Activity

              People

              • Assignee:
                brian.lee Brian Lee
                Reporter:
                jorge.ferrer Jorge Ferrer
                Recent user:
                Shalaka Tendulkar
                Participants of an Issue:
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Packages

                  Version Package
                  7.0.0 M1