Forgot your password?
New user?
Document Actions
#74: Add cut/copy/paste/delete and batch links to the content menu bar
- Proposed by
- Alexander Limi
- Seconded by
- David Convent
- Proposal type
- User interface
- Repository branch
- uiteam-plip74-copypastecontentmenu
- State
- completed
Motivation
Users should not have to go to the 'folder_contents' page each time they want to cut/copy or paste a single item.
the 'content' tab is used only when an owner/manager needs to perform actions on multiple items in a folder. It is more natural to call that action 'batch' and to place it close to the cut/copy/paste/delete links in the content menu.
Assumptions
* Bug #3653 (Contents tab is hidden when default document is set to state = 'published') Must be resolved before this plip/branch can mergeable, assuming that it is now related to the 'Batch' link appearing in the content menu.
Proposal
Add actions to the content menu bar that lets the user cut/copy/paste/delete an object from any page related to that content.
In addintion, remove the 'content' action from the content tabs and replace it by a 'batch' link in the content menu.
Implementation
Use of the patch written by Martin Opstad Reistadbakk (sent to plone-devel on march 2nd)
add i18n tags
In ActionTool
* Three actions were added under the 'edit_menu' category. This is done at Plone instanciation, ported to migration script 2.1 alpha.
* Actions actually look from left to right because of a float:right property in the CSS.
content menu CSS will probably be rewritten so this has be kept as is for now.
In skins/plone_templates/global_contentmenu.pt
* I18N is based on how content buttons are translated (for now is is a litterate expression, they should get a msgid).
* The 'alert_really_delete' is translated from a python expression, as it will appear in a javascript expression for an onclick attribute of the anchor. This might not be recognized by i18ndude (to be tested) so it should be added to the manual pot (after having tried this issue)
* The template tests if the object is the actual view page of it's container, if yes the actions are performed against the container instead of the object itself
Risks
not known
Progress log
must be completed by the end of the UI sprint.
delayed because of bug #3653 (see above).
