Current user tokens are duplicated [#1262918]

Hello,

I am having problems using tokens for the path of an (image-) field on a D7.7 install.
Even on a fresh install I am getting the following notice, whenever I edit a node that contains the field in question:

Notice: Array to string conversion in token_replace() (line 97 of ... \includes\token.inc).

Almost every token used for the path will result in the folder being named "array".
So if I set the path of an image field to i.e. "images/user/[current-user:uid]" the result is going to be "images/user/array". The only tokens that I got to work so far are the page number and the random ones (the above notice will remain though).

I have found only one similar issue (#1090596: Two modules with same token names cause notice and replace failure). I do not think though that this applies in my case.

Thanks a lot in advance!

Comment	File	Size	Author
#5	1262918-duplicate-current-user-tokens.patch	1.12 KB	dave reid

Comments

Comment #1

dave reid

he/him

English

Nebraska USA

commented 30 August 2011 at 21:09

Category:	bug	» support
Status:	Active	» Postponed (maintainer needs more info)

The only reason that the [current-user:uid] would be returning an array would be if another module is providing a token for it as well. Do you have any other modules enabled that provide tokens? Can you duplicate this with just a fresh core install + Token module installed?

Comment #2

Golem07 commented 1 September 2011 at 14:04

Hi Dave,

thanks a lot for the quick reply.

You are absolutely right. The module Realname Registration module (http://drupal.org/project/realname_registration) seems to be causing the problem. As soon as I remove it the problem goes away.

Do you reckon this problems is solvable at all? In this case i'd like to ask you to move the issue over there if it is possible- If not then I guess I'll have to live without realname registration.

Comment #3

dave reid

he/him

English

Nebraska USA

commented 1 September 2011 at 14:18

Title:	Notice: Array to string conversion in token_replace	» Token handling is messed up
Project:	Token	» Realname registration
Version:	7.x-1.0-beta4	» 7.x-2.x-dev
Category:	support	» bug
Priority:	Normal	» Major
Status:	Postponed (maintainer needs more info)	» Active

That was very helpful and led me to the real problem - realname_registration.tokens.inc is re-calling the current user tokens when it absolutely should not be doing that:

 140   if ($type == 'current-user') {
 141     $account = user_load($GLOBALS['user']->uid);
 142     $replacements += token_generate('user', $tokens, array('user' => $account), $options);
 143   }

That chunk of code needs to be removed or any current user tokens will *never* work for anyone with Realname registration enabled.