Ticket #9547 (closed PLIP: wontfix)
Integration of PloneWorkflowTransitions in to Plone
Reported by: | dukebody | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Future |
Component: | General | Version: | |
Keywords: | Cc: | grahamperrin@… |
Description
http://plone.org/products/plone/roadmap/130
Make the "state" action able to redirect to url defined in "Display in actions box URL" attribute of a workflow transition.
Proposed by
Riccardo Lemmi
Proposal type
User interface
State
being-discussed
Motivation
Some use cases require, when a user try change the state of a content, to redirect the user to a form, currently the only way to do it is to customize 'global_contentmenu.pt'.
Proposal
The product "PloneWorkflowTransition" customize the 'global_contentmenu.pt', so that the url showed in the 'state' action be the "Display in actions box URL" attribute and rewrite all the old urls in the workflow definitions to be the real.
Implementation
To have this feature integrated in Plone it is needed to integrate 'global_contentmenu.pt' of "PloneWorkflowTransition" and to rewrite all the workflow transition definitions in PloneWorkflow.py and FolderWorkflow.py.
Risks
A product like "PloneWorkflows", or in general products installing new definitions of workflows require to rewrite the actbox_url to the real url, for example in plone_workflow there is:
actbox_url = "%(content_url)s/content_publish_form"
this should be transformed in:
actbox_url = "%(content_url)s/content_status_modify?workflow_action=publish"
to work correctly. Participants
Riccardo Lemmi, Vincenzo Di Somma
Change History
comment:2 Changed 5 years ago by rossp
- Status changed from new to closed
- Resolution set to wontfix
PLEASE READ THIS AND RE-OPEN VALID PLIPS!
As we launch the new PLIP process we'd like to see which PLIPs:
- are still appropriate/needed
- still have owners/proposers/champions
- still have available implementers
If this PLIP should still be considered for future releases of Plone please do re-open this ticket and assign an appropriate milestone. If it should be considered for the next release of Plone, use the 4.2 milestone. Also be sure to update the PLIP description, requester, owner, etc. and include a comment detailing recent progress and new plans. We will use all these details in the new continuous PLIP process.