<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>A bit off-topic and not super critical, but this will also need to
spur a discussion of a more manageable access control page if we have
something like 5 perms for each content type. Is there an issue/any
ideas on how to simplify the access control page? Or, is a super long
matrix format still the best way to go?</tt><br>
<pre class="moz-signature" cols="72">Rob Roy Barreca
Founder and COO
Electronic Insight Corporation
<a class="moz-txt-link-freetext" href="http://www.electronicinsight.com">http://www.electronicinsight.com</a>
<a class="moz-txt-link-abbreviated" href="mailto:rob@electronicinsight.com">rob@electronicinsight.com</a></pre>
<br>
<br>
Zohar Stolar wrote:
<blockquote cite="mid459435D2.3010602@gmail.com" type="cite">
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<div class="moz-text-html" 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>
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.<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 class="moz-signature">-- <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>
</blockquote>
</body>
</html>