<div><span class="gmail_quote">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)
<br><br><br>On 12/28/06, <b class="gmail_sendername">Zohar Stolar</b> <<a href="mailto:z.stolar@gmail.com">z.stolar@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr" bgcolor="#ffffff" text="#000000">
<p style="margin-bottom: 0cm; margin-top: 0pt;"></p>
<div lang="x-unicode">
<p style="margin-bottom: 0cm; margin-top: 0pt;">(might arrive twice...
excuse me if it does)<br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;"><br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;"></p>
I was looking through <a href="http://Drupal.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Drupal.org</a> 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.<br>
The idea (which has certainly been raised before) is to add, next to:<br>
<code><br>
"create TYPE content", </code>- adding new nodes of that content type <br>
<code>"edit own TYPE content",</code> - editing <u>the contents</u> of
own nodes of that content type <br>
<code>"edit TYPE content", </code>- editing <u>the contents</u> of
all nodes of that content type (whether or not the user has right to
create nodes)<br>
<br>
two more possibilities:<br>
<code><br>
"view TYPE content" </code>- roles that are allowed to view the
content type's nodes<br>
<code>"administer TYPE content" </code>- roles that are allowed to
modify the publishing options on all nodes of that content type<br>
<br>
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 content.<br>
<br>
Such a change should be done through core, so actually my questions
are: <br>
Is there any work on this direction / open issue? <br>
Are there already any conclusions?<br>
Should I start writing a patch :-) ?<br>
<br>
Cheers,<br>
Zohar<br>
<br>
<br>
<br>
<div>-- <br>
<div style="border-top: 1px dashed rgb(0, 0, 153); margin: 1em 0pt 0.5em; padding: 0.5em 0.3em; font-family: Arial,Helvetica,sans-serif; font-size: 12px; font-weight: bold; color: rgb(119, 119, 119);">Zohar
Stolar | זהר סטולר<br>
<span style="font-weight: normal;">לינווייט תשתיות תוכן קהילתיות</span>
</div>
</div>
</div>
</div>
</blockquote></div><br>