"Validation error, please try again. If this error persists, please contact the site administrator." [#1135390]

Hi Guys,

I ran into a problem today, when I use the user.login web service second time after I login from the web service interface admin/build/services/browse/user.login it gives the error message "Validation error, please try again. If this error persists, please contact the site administrator." its a drupal_set_message error.

Whats weird is this is not happening always. If I refresh the page after logging in and then try to log in using some valid credentials it gives the "Already logged in as " response as it should. just to check I tried to put a print statement on the user.login callback, but that print statement never got executed. I think it is not even hitting the callback.

Has anyone encountered this scenario before.

Thanks in advance

Cheers,
Swarad

Comments

Comment #1

marcingy CreditAttribution: marcingy commented 23 April 2011 at 02:17

Category:	bug	» support
Priority:	Major	» Normal

Comment #2

marcingy CreditAttribution: marcingy commented 29 April 2011 at 00:48

Do you have a redirect of any form set up?

Comment #3

swarad07

English

Navi Mumbai, India

CreditAttribution: swarad07 commented 23 May 2011 at 13:08

Hi Marc Ingram,

Nopes. No form set up or anything. I am simpy calling the WS from the UI. (amin/build/services/user.login). It works perfectly first time and returns me the user object, then if I click the call method button again the error shows up. Then I refresh the page and call the method again (still logged in), then it shows the "Already logged in as username", which should have been shown the first time also.

Sorry for the late reply was away from Internet for a while.

Comment #4

marcingy CreditAttribution: marcingy commented 23 May 2011 at 23:16

Status:

Active

» Closed (won't fix)

The above happens when the session id has changed and this is the case when the user login method is called. Given this only affects the browser and the browser has been removed in 6.x.3 I'm marking this as won't fix mainly because there is no real way round this issue given the interaction between fapi and user sessions.