Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.1.3
-
None
Description
There is a wish for implementing "edit_defaults" custom portlet mode as descripted in JSR168 portlet specification:
----------------------------------------------------------
PLT.A.3 Edit_defaults Portlet Mode
The edit_defaults portlet mode signifies that the portlet should render a screen to set the default values for the modifiable preferences that are typically changed in the EDIT screen. Calling this mode requires that the user must have administrator rights. Therefore, only the portal can create links for changing the portlet mode into edit_defaults.
Portlet developers should implement the edit_defaults portlet mode functionality by
overriding the doDispatch method of the GenericPortlet class and checking for
PortletMode("edit_defaults ").
In the deployment descriptor the support for the edit_defaults portlet mode must be
declared using
<portlet-app>
...
<portlet>
...
<supports>
...
<portlet-mode> edit_defaults </portlet-mode>
</supports>
...
</portlet>
...
<custom-portlet-mode>
<name> edit_defaults </name>
</custom-portlet-mode>
...
</portlet-app>
-----------------------------------------------------------
There is number of situations when there is need of different default preferences for same portlet type. There is a problem to change default preferences by administrator now. Because he must to edit psml files manually, without graphical interface.
For example, i want my portal shows to all users rss feeds from bbc and cnn with RSS Portlets at main page of my portal. But administrators of my portal needs to know psml format to change read-only preferences, and they can't do it thru grafical interface.
So, I think, many people wishes for edit_defaults portlet mode.
So, this jira record is wish for edit_defaults portlet mode
Attachments
Issue Links
- is blocked by
-
JS2-1106 Support auto-switching to edit_defaults even when the portlet doesn't support EDIT mode.
- Closed