Want to take over module
| Project: | Menu per Role |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Hi fargo,
I'm copy-pasting our recent conversation here. Please confirm to this issue so that i can apply for a CVS account as stated by http://drupal.org/node/59
> Hi
>
> i've created a module to have more fine grained control on the menu
> administration.
>
> It is .. the module allows you acces control over
> * administering menu's (be able to create/delete menu's)
> * administering menu items (be able to create/delete menu items)
> * which parent menu's are available to attach nodes to.
>
> Although this module is not totally related with your menu per role
> module (which control viewing menu's) i think it could be approriate
> to merge my module into yours. I will put a copy of the menu online
> during the weekend, together with a demo-site to play with.
>
> I'm also looking into the patch to core required to get your module
> working. I *think* I might be able to remove that requirement by
> overriding some drupal hooks.
Hi!
That sounds fine.
Perhaps you have noted, I don't have as much time to look after the
module as I should have.
So I would be glad, if you could combine our modules to one and proceed
maintaining it.
However I think, it shouldbe possible to use the menu_per_role feature
("restrict view access") only without getting a performance penality by
the unused features (administer menu, items, available parents). Do you
think you could get this working?
Hm, we could also add settings to the module, which allows turning some
functionality off.

#1
confirmed :)
#2
any updates on this?
#3
From mid February i will invest more time in this..
#4
If you can describe your planned approach to removing the patch I want to look into this as well and can do so now.