additional tokens needed

At the moment only global tokens are supported. But it would be nice feature if we can support node tokens as well (if /node/X page is viewed).

Anyhow you will need to export profile user uid token in your own module.

I will try to implement 'specific' tokens replacement and advise in this issue.

Here is the patch for the implementation of support for users and node tokens and the extension of the help info that describe all the available tokens.

Patch applies cleanly and I see the additional tokens in the available replacements patterns but using them in a menu path results in:

The path 'path/to/[token-value]' is either invalid or you do not have access to it

@Khalor probably it happens when your are not seeing node/user profile, that's why this token could no be applied.

In general case there could be several possible cases of using node/user/taxonomy tokens, etc...

1) Context case: module could parse token in the menu title/path for the entity (node/user profile) that is being viewed.
2) Manually selected case: module could parse token for specified entity.
3) Probably more...

In general this is an Idea how it should look like:

Node tokens [v]
    [ ] Disabled
    [*] Context
    [ ] Manually selected
        Node [___________________o]
User tokens [v]
    [ ] Disabled
    [ ] Context
    [*] Manually selected
        User [_admin_[1]_________o]
Other...

We need to be able other modules to extend this functionality, hence we need a hook, which allows to add different kinds of menu token handlers for the tokens. Basically there should be an callback function which returns object.

hook_menu_token(&$tokens) {
  $token['<token_type>'] => array( // user, node, etc
    '<menu_token_handler_type>' => array(
      'title' => '<title>',
      'object_callback' => '<function_name>',
    )
  );
}

We need somehow to be able to alter form elements probably using form_later functions. Also we need to add a checkbox "Hide menu item if it could not be parsed".

i get this error when applying the patch.

patch: **** Only garbage was found in the patch input.

i applyied the patch manually...

i used the token [nid]...

but in the node, the link of the menu link was printed node/[nid]/pictures...

I have created separate brunch for it: http://drupalcode.org/project/menu_token.git/shortlog/refs/heads/7.x-1.x.... I am actually working on 7th version of this module, after it would be finished we could back-port changes.

It still needs work to have some kind of form support for the handlers.

It still needs work to have some kind of form support for the handlers.

sub, though I was able to get this working by adding my own version of the alter hook used in the module

function YOURMODULE_translated_menu_link_alter(&$item, $map) {
  $mlid = $item['mlid'];
  $menu_token_item = menu_token_get($mlid);

  // Check whether we should replace the path.
  if (isset($menu_token_item)) {
    // If item is generated by admin menu module, tokens should not be replaced and
    // indicator that tokens are used should be shown.
    if (_menu_token_menu_admin($item)) {
      $item['title'] .= theme('menu_token_uses_tokens');
      $item['localized_options']['html'] = TRUE;
    }
    else {
      // Replace with tokens.
	  $arg_node = node_load(arg(1));
      $item['title'] =  token_replace($item['title'], 'node',$arg_node );
      $item['link_path'] = token_replace($menu_token_item['link_path'], 'node',$arg_node );
      $item['href'] = $item['link_path'];

      // Override active trail if showing front page but translated link is not to front page.
      // NOTE: This relies on any parent of a tokenised menu item having "option" flag "alter" set,
      // which is most easily achieved by setting it to use token translation but not specifying a token.
      // Otherwise parent does not get processed through this function and because its untranslated child has
      // an href of <front>, the menu system thinks it is part of the active trail to the front page.
      if (drupal_is_front_page() && $item['href'] != drupal_get_normal_path(variable_get('site_frontpage', 'node'))) {
        $item['in_active_trail'] = FALSE;
      }

      // Check whether path is external.
      if (menu_path_is_external($item['link_path'])) {
        return;
      }

      // Load menu_item and check access.
      if ($menu_item = menu_get_item($item['link_path'])) {
        $item['access'] = $menu_item['access'];
        return;
      }

      $item['access'] = FALSE;
    }
  }
}

This allowed me to use the node arguments which include OG stuff (horay)

We now support plugins for advanced tokens like this... The most basic tokens are working (node from context, user from context, taxonomy term from context) and many others are to come. Check out this new feature in the latest dev version.

really? this is great!
for which version? D6, D7 or both?

thanks!

Currently only D7. I don't work with D6 and am therefore not really interested in a D6 backport.

That code I have posted is D6. If you download ELMS there is a working example that has some global tokens in it as I'll be dropping this project in favor of the functionality I've included.

The code in #13 might cause funny behavior on pages that are not node pages since it just blindly includes node_load(arg(1)) as a node not even knowing if arg(1) refers to a node. If you want a real implementation for this for D6 you might want to backport my code to D6.

I have added code to user defined and random handlers. However they still needs to be updated, so I am creating new issue.

Here is an issue http://drupal.org/node/1283804.

Now we need to back port it to D6.

Till #750352: Provide an option to also offer dev builds as updates if they are newer - for advanced users & beta testers is fixed, can someone please update the latest devs (both 6.x & 7.x) so that they are newer than stable ones? Thanx in advance ;)

Hi! Is there any progress?
I just trying to use this module with OG for group menu customizing.

This is a feature for D6 that I would very much appreciate as well. I've been looking for a way to dynamically create menus for different organic groups. This seems like the ideal solution. Is there any way to create a customized token workaround while waiting for a backport from D7? Thanks.

protoplasm, you can use Panels with custom panes for creating menu for OG. Sorry for off topic.

Are there any near term plans to add functionality to support additional tokens?

Thanks, Jim

The workaround at [#973882-13: additional tokens needed] worked for me.

Where do you add [#973882-13: additional tokens needed] to get it to work?

D6 is discontinued.

This is not required anymore, since the integration with Entity API allows to have tokens from all configure entities.