Skip to main content
7 events
when toggle format what by license comment
Dec 22, 2014 at 10:06 comment added Clive It's weird that they make that claim, when you consider that they couldn't affect the operation of the Services module without changing its code, and it's plain-as-day what the Services module is trying to do. Definitely a mistake on the part of the tutorials' authors if they're making such claims (in my opinion anyway)
Dec 22, 2014 at 10:02 vote accept E.A.T
Dec 22, 2014 at 10:02 comment added E.A.T Accepted @clive... but so many tutorials and drupalgap's submodule with logintoboggan do at least make that claim it's a working feature.
Dec 22, 2014 at 8:15 comment added Clive Yes that's the expected behaviour. The original user is restored, even if that user is anonymous. By design, the user register resource is not supposed to log the newly created user in. It just creates it. There's no bug here, your expectations are just wrong. Once you accept that the Services module is not supposed to log the newly created user in, in fact the opposite, you'll be able to move on with your development
Dec 21, 2014 at 23:01 comment added E.A.T Additionally @Clive, it appears these functions happen in the incorrect order. Essentially, _services_controller_execute_restore_user() overwrites the newly authenticated user with the 'original' anonymous user during register.json
Dec 21, 2014 at 22:23 comment added E.A.T i'm expecting to keep the same session but just change the user object from anonymous to authenticated and related user data. Eitherway, it does not seem that a session is created at all here. My dblog reports show the user object passed around but ALWAYS as an anonymous user except for within the Core User module at user_login_finalize. Then I'm assuming the drupal_session_regenerate within removes the authenticated session as well.
Dec 21, 2014 at 14:19 history answered Clive CC BY-SA 3.0