The Real Name module is turned on (and the uLogin, of cource).
By default, it configured with [user:name-raw] token, then I have some attemts to login using uLogin service - all correct (except I didn't seen real name of logged in user, only like ulogin_facebook_100000469XXXXXX)
I change it to [user:name].
Then no response from web-site.
Chrome error
[RUS]: Error 324 (net::ERR_EMPTY_RESPONSE): Сервер разорвал соединение, не отправив данные.

Please take care on, I'm not sure is a problem in the Real Name or uLogin modules, but anyway.

Comments

Nick Fedchik’s picture

I see the problem every time when try to change RealName tokens with uLogin turned on.

duozersk’s picture

Hi,

ulogin_facebook_100000469XXXXXX - this one is actually the user name (machine-generated) for the created user if he logged in using the uLogin widget through Facebook. And it is correctly shown when Real name is set to show the raw name ([user:raw-name] token).
When you set it to show the [user:name] token (The real name of the user account.) then you instructed Real name to show the name that Real name constructs, so when it processes it it loops into itself again and again. As far as I have looked into Real name code it has some handling for such situation, but apparently it didn't work in your case.
So it is either an issue in the Real name module or just the misconfiguration that shouldn't be allowed.

Hope it helps.

AndyB

Nick Fedchik’s picture

I post to RealName module issues about:
#1510366: Crash with [user:name] token and uLogin module

duozersk’s picture

Status: Active » Closed (duplicate)

Marking as duplicate of #1510366: Crash with [user:name] token and uLogin module, should be fixed by this commit to Real name code - http://drupalcode.org/project/realname.git/commit/556ebcf and the release of realname-7.x-1.0 version.

AndyB