[development] Changing Roles (was Deleting Cached Permissions)
David Metzler
metzlerd at metzlerd.com
Tue Aug 28 14:25:40 UTC 2007
It's a design hole. You cant' have an entry in node_access table to
control behavior of a node that doesn't exist yet. If we took a
different approach to node access using a relationship API. Modules
would all need to implement permissions along the lines "Add Book
Pages" differently than "Create Books", and have that concept scale
similarly to concepts like organic books.
Dave
On Aug 28, 2007, at 7:10 AM, Peter Wolanin wrote:
> Is that a bug in node_content_access() ?
>
> -Peter
>
> On 8/28/07, Karoly Negyesi <karoly at negyesi.net> wrote:
>> ----- Start Original Message -----
>> Sent: Tue, 28 Aug 2007 08:57:19 -0400
>> From: "Ken Rickard" <agentrickard at gmail.com>
>> To: development at drupal.org
>> Subject: Re: [development] Changing Roles (was Deleting Cached
>> Permissions)
>>
>>>
>>> Isn't hook_node_access() the proper way to handle this requirement?
>>
>> Create is a bastard here because it's not overrideable. I had a
>> patch long long ago which tried to create a 'create' op in nodeapi...
>>
More information about the development
mailing list