Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Can you share with me a scenario where this creates a problem? These values are used in the module even after the user has signed in. But if does create problems, we should do something about it.
Well, I would say it's in the middle -- I'd consider it bad practice. None of Drupal core modules keep so much data in the session for authenticated user. Maybe you can move it to the $user object, or provide your own tables to hold the info.
Comments
Comment #1
geokat commentedThis is not a bug, it's a feature.
Can you share with me a scenario where this creates a problem? These values are used in the module even after the user has signed in. But if does create problems, we should do something about it.
Thanks,
George
Comment #2
amitaibu> This is not a bug, it's a feature.
Well, I would say it's in the middle -- I'd consider it bad practice. None of Drupal core modules keep so much data in the session for authenticated user. Maybe you can move it to the $user object, or provide your own tables to hold the info.
Comment #3
geokat commentedComment #4
BenK commentedSubscribing
Comment #5
amitaibuMaybe ctools' object-cache can be handy in this case.
Comment #6
Roze-1 commentedSubscribing, Is it possible to direct them to appropriate widgets ??
Edit: Or is it possible to remove the "rpx_last_provider_info" during the login ??
A little help would be appreciated !