Closed (won't fix)
Project:
Publish Content
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
25 Feb 2013 at 15:29 UTC
Updated:
23 Aug 2013 at 07:57 UTC
Hello,
Publish Content is a very good module, and helps a lot, but there are some times when it's not enough.
Let's say I want user to be able to publish, and to change authorship of a node, then the only permission that would allow me so is "administer nodes".
I wrote a rough base for a module that would provide new permissions, maybe we could join force and try to make Publish Content more powerful?
I know that my code is not enough, and needs more work, but working it together may be more effective.
Any opinion on this is welcome.
Regards,
David
Comments
Comment #1
simon georges commentedFor me, changing authorship is not the same as publishing (a publisher is the final step to the review process, but the author should stay the same).
I'm afraid adding such features would add some complexity to the module.
I agree that what you're proposing is related to the publishing workflow, but shouldn't it be addressed by a publishing workflow module, instead of one that (simply) adds some UX goodness to core?
Comment #2
johnennew commentedClosing this issue.