Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
In persistent login after version 2.2.1, the method \Drupal\persistent_login\TokenManager::createNewTokenForUser is updated, which uses \Drupal\persistent_login\RawPersistentToken::getHashedSeries to create a new token. So, to support persistent login, we need to use the new method \Drupal\persistent_login\RawPersistentToken::getHashedSeries in autologout_autologout_prevent()
Issue fork autologout-3500246
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #5
deaom commentedI can confirm that MR works as expected, as without it, the if check is never true. Rebased branch and setting status to RTBC.
Comment #6
the_g_bomb commentedWould it be worth mentioning anywhere that this needs an up-to-date version of persistent login? Perhaps we can add the note in the README that support is offered for version 2.2.2 onwards.
Willing to accept this as is, if not, as I don't use the module myself, and I note that 2.2.2 was a security update, so anyone running a version lower than that is running an insecure version.
Comment #7
the_g_bomb commentedThe other thought I have is that it would be better to consider using the validateToken() method per #3398250: Add persistent login module support D10. I can't say I am 100% confident about which is the best approach.
Comment #8
the_g_bomb commentedMerged, thank you