EchoDitto Labs - Automenu.module: automatic menu parenting for Drupal 5.x - Comments

Due to an unusually large

Tom — Tue, 26 Aug 2008 13:35:02 -0700

Due to an unusually large amount of comment spam on this entry (even after changing captchas!) I'm disabling comments here. If anyone needs to chat about this module, please don't hesitate to email me (tom) or chris AT echoditto DOT... well, you know the rest.

chat Good, would be good to

chat — Thu, 21 Aug 2008 14:04:15 -0700

chat

Good, would be good to extend it to filter "Parent item:" options when editing a node type.

repositories. Then again,

rüya tabirleri — Thu, 21 Aug 2008 13:56:35 -0700

repositories. Then again, maybe OA policies aren’t as newsworthy or sexy as tuition and financial aid reforms. Seriously though, when you combine happened at Harvard yesterday with the recent NIH legislation, it looks like the OA movement has a much better chance to progress in our higher education system.

The link doesn't seem to be

Dylan — Fri, 18 Apr 2008 11:22:41 -0700

The link doesn't seem to be working to download this module...is it still available?

Good, would be good to

Pom — Thu, 07 Feb 2008 16:20:18 -0800

Good, would be good to extend it to filter "Parent item:" options when editing a node type.

Any Idea how this can be done?

Thaks

This module works well, with

sym@drupal.org — Mon, 04 Feb 2008 03:57:17 -0800

This module works well, with one exception:

When you are viewing a full node, it kills off the nodes tabs. I think this is because the MENU_LOCAL_TASK tabs are being built from the active menu item rather than the node.

I am not getting this to

jefbak — Sat, 29 Dec 2007 19:02:44 -0800

I am not getting this to work yet. Where do you enable it once it is running as a module?

Automenu.module: automatic menu parenting for Drupal 5.x

Chris — Mon, 10 Dec 2007 07:30:19 -0800

I've had a couple projects that needed the menu system to stay open when a full node was being displayed. The Drupal menu system, while dynamic and mostly awesome, didn't seem to allow for that, at least not in the way that I needed it to. So, I wrote Automenu.

For each content type, Automenu allows an administrator to set a default parent in the menu system. If a node is given an entry in the menu system, that default parent is ignored. Relatively simple.

To illustrate, let's say you'd like all nodes of type 'news' to show up under an entry in Primary links called 'Newsroom,' but you don't want to actually create an entry in the menu system for each one. Automenu will do that for you, specifically without creating additional entries in the menu system. If you want to give an individual news node its own special place in the menu system, you can still do that the standard way.

Give it a shot!

Thanks to merlinofchaos and the folks in the #drupal IRC channel for steering me in the right direction on this. They're a bunch of great and helpful folks.