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@negyesi.net> wrote:
----- Start Original Message ----- Sent: Tue, 28 Aug 2007 08:57:19 -0400 From: "Ken Rickard" <agentrickard@gmail.com> To: development@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...