Forgot your password?
New user?
Document Actions
#242: Move manage-portlets link to site actions
- Contents
The multiple manage-portlets links are in an unintuitively placed and complicate many custom themes.
- Proposed by
- Wichert Akkerman
- Seconded by
- Danny Bloemeldaal
- Proposal type
- User interface
- State
- being-discussed
Definitions
Motivation
Both portlet columns feature a "manage portlets" link at the bottom. This has several problems:
- the location of the link and the fact that each column has its own manage portlet link leads users to believe that that link will go to a page to configure that specific column, which is not true.
- Many (if not most)l custom themes style the portlet column and have no room for the manage portlets-link below the portlets.
- all configuration options are in site or document actions, except for manage portlets- a needless inconsistency.
Assumptions
Proposal
Remove the manage portlets-link from the default portlet renderer template and replace it with a site action.
One could argue that this should be a document action since it reconfigures the current document, while site actions work globally. We already have many document actions, so adding another would clutter the user interface.
Implementation
Deliverables
Risks
Progress log
Participants
Framework team vote
Posted by
Andreas Zeidler
at
October 27, 2008 - 14:33
-1, i agree with Martin and the other that this shouldn't be changed in a minor release (see http://lists.plone.org/pipermail/framework-team/2008-October/002228.html + its thread). instead it should be done as an add-on or like Raphael suggested (see http://lists.plone.org/pipermail/framework-team/2008-October/002229.html)
3.3 Framework team vote
Posted by
Martijn Pieters
at
October 27, 2008 - 14:43
-1, in light of the recent consensus that the 3.x series UI needs to remain stable.
Framework-team vote
Posted by
Danny Bloemendaal
at
October 27, 2008 - 14:51
Ok, under protest: -1 and move it to an add-on.
Framework Team vote
Posted by
Tom Lazar
at
October 28, 2008 - 10:35
-1 The dealbreaker being less that it's a too invasive UI change for my gut feeling of what is permissible for 3.3 and what not, but more so because the portlet settings are contextual and a global setting wouldn't be able to address this easily (i.e. without making it more complicated for the user).
IMHO this needs to be addressed together with #244 in a consistent manner. perhaps even not before 4.0 because i can't imagine a solution that a) does not suck and b) still isn't too invasive...
IMHO this needs to be addressed together with #244 in a consistent manner. perhaps even not before 4.0 because i can't imagine a solution that a) does not suck and b) still isn't too invasive...
+1