Jetspeed 2
  1. Jetspeed 2
  2. JS2-540

Default Preferences should be flagged as READ-ONLY

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.2.0
    • Component/s: Portlet Registry
    • Labels:
      None

      Description

      Default Preferences should be flagged as READ-ONLY
      Default Preferences are the ones defined in the portlet.xml
      A user should be able to store their own version of this preference
      At this point, the preference is no longer READ-ONLY

        Activity

        Hide
        Ate Douma added a comment -

        Modifying default preferences could be allowed through a custom config portlet mode as described in the Portlet Specification (PLT.A.2).
        Right now, Jetspeed doesn't have a config portlet mode, but as we now do support custom modes, it shouldn't be too difficult providing one.

        Show
        Ate Douma added a comment - Modifying default preferences could be allowed through a custom config portlet mode as described in the Portlet Specification (PLT.A.2). Right now, Jetspeed doesn't have a config portlet mode, but as we now do support custom modes, it shouldn't be too difficult providing one.
        Hide
        Ate Douma added a comment -

        Note: the Portlet Specification also describes a custom edit_defaults portlet mode (PLT.A.3).
        As I understand it, that one is meant to edit "modifiable" as well as "instance" specific preferences, in contrast to the config mode which should be used for "global" (e.g. not instance specific) and thus normally "unmodifiable" preferences.

        Show
        Ate Douma added a comment - Note: the Portlet Specification also describes a custom edit_defaults portlet mode (PLT.A.3). As I understand it, that one is meant to edit "modifiable" as well as "instance" specific preferences, in contrast to the config mode which should be used for "global" (e.g. not instance specific) and thus normally "unmodifiable" preferences.
        Hide
        David Sean Taylor added a comment -

        Moving this issue to 2.2-dev
        There has been some interest in getting this implemented and its moved up the priority list recently

        Show
        David Sean Taylor added a comment - Moving this issue to 2.2-dev There has been some interest in getting this implemented and its moved up the priority list recently
        Hide
        David Sean Taylor added a comment -

        Ensuring that default preferences are not updated should be handled by the implementation (Jetspeed). Marking these defaults ALL as readonly will distort the actual setting for this preference i.e. if its really read only we will have no way to differentiate.

        Show
        David Sean Taylor added a comment - Ensuring that default preferences are not updated should be handled by the implementation (Jetspeed). Marking these defaults ALL as readonly will distort the actual setting for this preference i.e. if its really read only we will have no way to differentiate.

          People

          • Assignee:
            Unassigned
            Reporter:
            David Sean Taylor
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development