Port Menu Block to D6

* subscribing. 'nuff said ;-)

subscribing ... let me know if I can help.

Now that Menu block 5.x-1.0 has been released, the module can now be ported to Drupal 6.

The biggest piece that needs converting is the menu_block_tree() function. In 5.x, that function is a modification of D5's menu_tree function. But in D6, that functionality is completely different.

Wendy, how good are your PHP skills? Do you know CVS or how to do patches?

All those skills are minimal, but increasing. I can probably help if clear directions can be provided. Feel free to contact me directly.

Wondering why none of menu trim, menu restricter or sliced menu has drupal 6 port yet.
I'm using local menu for the moment, but it's got a bug that's quite irritating.

Subscribe ;)

The Drupal 5 version of menu_block was branched to DRUPAL-5 on Monday and I started the porting to D6 in HEAD.

http://drupal.org/project/cvs/265945

subscribing

Would lurve a D6 version. Will help out where I can. No time to delve into the new menu system for a few weeks at least.

just subscribing

Done.

Bonus points for getting Menu block’s administrative interface to match the interface of core’s block module. :-)

Everything works perfectly, the active menu trail is there also. Great!!
This.. has been a smooth ride.

Appreciate your work here, John :)

Wondering why none of menu trim, menu restricter or sliced menu has drupal 6 port yet.

Well, since the Drupal 6 menu system was rebuilt, the menu API that modules used to get menu tree data has completely changed. Menu block required nearly a complete rewrite to port it to Drupal 6.

the active menu trail is there also. Great!!

Yeah, for expanded menu trees (returned by core's menu_tree_all_data()), I had to create a menu_tree_add_active_path() just to add the active path back into the data structure. :-p

Automatically closed -- issue fixed for two weeks with no activity.