[development] Menu Tree Access Control?

Ken Rickard agentrickard at gmail.com
Sun Apr 5 22:03:44 UTC 2009

With reference to http://groups.drupal.org/node/20913.

Reviewing the code, the recently released Menu Access module is NOT an
access control module in the Drupal sense. It is designed to restrict
the editing of menu items.  That is it. It does not cascade any ACL
functions to nodes or other content.

- Ken

On Sun, Apr 5, 2009 at 6:00 PM, Ken Rickard <agentrickard at gmail.com> wrote:
> I am the Palantir developer in question and have two modules just
> about to release that are relevant here.
> Release should be by end of month, if all goes well.
> 1) Menu Node API
> The menu/node API module keeps track of menu-node relationships for
> you, so that you can run JOINs from the {node} table to the
> {menu_links} table through the new {menu_node} table.
> This is a glue module that will allow for (among other things):
> -- Menu-based Views
> -- Node Access modules based on menu hierarchy,
> 2) Menu (Needs Name)
> The second module was called menu_access, and someone just took the
> namespace on d.o. It leverages the Menu Node API and rewrites
> node/%/edit using hook_menu_alter(). It then lets an administrator
> define menu 'sections' -- elements of the tree hierarchy that are used
> as ACLs.
> Individual users can then be assigned as "section editors".  A section
> editor has cascading rights down the menu hierarchy.
> This module is _deliberately_ not a Node Access module, since I have
> not yet figured out the necessary overhead for which menu parents
> would need to be stored in the {node_access} table as GIDs.  And since
> the client did not require View or Delete access control, Edit control
> was sufficient.
> I hope that any delay in releasing these won't force anyone to write
> duplicate code.  Larry and I will convene next week and see if we can
> get a firm launch date.
> - Ken Rickard
> agentrickard
> On Sat, Apr 4, 2009 at 11:59 AM, Earnie Boyd
> <earnie at users.sourceforge.net> wrote:
>> Quoting Simon Roberts <lyricnz at gmail.com>:
>>> I've also been doing fine-grained book-page access, per-user and
>>> per-role, and ended up coding more than I would have liked.  (Writing
>>> ACLs on the fly, and twiddling with menu-entries during theming -
>>> uugh).
>>> No idea if this is useful, but I saw this new project pop up a few days
>>> ago
>>> http://drupal.org/project/book_page_access
>> And then there is http://drupal.org/project/acl which give you an API.  The
>> page lists other modules using it.
>> --
>> Earnie
>> -- http://r-feed.com/           -- http://for-my-kids.com/
>> -- http://www.4offer.biz/       -- http://give-me-an-offer.com/
> --
> Ken Rickard
> agentrickard at gmail.com
> http://ken.therickards.com

Ken Rickard
agentrickard at gmail.com

More information about the development mailing list