Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The reason this happens just for them is that the timezone is set based on the user configuration during session authentication.
That should probably be pulled out of there, which would affect the cases that still include it manually.
Comment | File | Size | Author |
---|---|---|---|
#2 | drupal-2054203-2.patch | 715 bytes | dawehner |
Comments
Comment #1
BerdirNote: There are other tests too that fail, but this IMHO indicates an actual bug: That user timezone settings aren't respected when a different authentication is used.
Comment #2
dawehnerComment #3
BerdirI guess we want to avoid setting it twice :)
Still think whatever we have right now with session.inc is a crazy mess :)
Comment #6
dawehnerAsked @znerol what to do here ... he is more into authentication/session stuff ...
Comment #7
znerol CreditAttribution: znerol commentedI think this should be in
AccountProxy::setAccount()
because this also covers the account switcher service. Also the now suprious calls should be removed fromSessionManager
.Comment #8
almaudoh CreditAttribution: almaudoh commentedThis seems to be covered now in #2328645: Remove remaining global $user which is RTBC.