[development] Even more flexibility in content management
cog.rusty at gmail.com
Fri Dec 29 01:11:45 UTC 2006
A great idea. As a user active in our support forums, I would also love to
see "view own TYPE content". For some of the other there are roundabout ways
to achieve, using taxonomy access control, but for "view own" there is none.
Requested use cases for private workspaces do exist, and the current ways
are rather convoluted (1-user OG groups, 1-user user categories, unpublished
nodes... and the like)
On 12/28/06, Zohar Stolar <z.stolar at gmail.com> wrote:
> (might arrive twice... excuse me if it does)
> I was looking through Drupal.org to find if there is work towards
> granulating the permissions table a bit more, by adding a way to limit
> administer/access to nodes by type.
> The idea (which has certainly been raised before) is to add, next to:
> "create TYPE content", - adding new nodes of that content type
> "edit own TYPE content", - editing *the contents* of own nodes of that
> content type
> "edit TYPE content", - editing *the contents* of all nodes of that content
> type (whether or not the user has right to create nodes)
> two more possibilities:
> "view TYPE content" - roles that are allowed to view the content type's
> "administer TYPE content" - roles that are allowed to modify the
> publishing options on all nodes of that content type
> I encounter more and more situations where I want to delegate the
> publishing options permission to a specific role, but only to one content
> type, otherwise I have to give the person control over the whole site's
> Such a change should be done through core, so actually my questions are:
> Is there any work on this direction / open issue?
> Are there already any conclusions?
> Should I start writing a patch :-) ?
> Zohar Stolar | זהר סטולר
> לינווייט תשתיות תוכן קהילתיות
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development