Why is manage_pasteObjects protected with "Modify portal content"?
Sean Upton <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CANjV-2O7KOd92SmmXbqmghJsVUBPwuSDA=aRsYJimEeAUjy2og@mail.gmail.com> |
The subject-line is self-explanatory: https://github.com/plone/Products.CMFPlone/blob/master/Products/CMFPlone/Portal.py#L46 https://github.com/plone/Products.Archetypes/blob/master/Products/Archetypes/BaseFolder.py#L42 https://github.com/plone/plone.dexterity/blob/master/plone/dexterity/content.py#L580 Ideally, this really should be 'Add portal content' -- so that folks who have permission to view the content in source, and add content to target can paste? Working around this requires jumping through hoops (for example, I have a workflow definition that only allows those with the manager role to Modify an item in a "Published" state, which forces me to workaround by creating a distinct workflow definition for my folder just to route around the wrong, but long-standing conventional permission). Is this a simple long-standing mistake that could eventually be corrected? Am I missing something? If not, should I PLIP changing this for Plone 5? Sean ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk