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.

Files: 
CommentFileSizeAuthor
#2 drupal-2054203-2.patch715 bytesdawehner
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] Unable to apply patch drupal-2054203-2.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]

Comments

Berdir’s picture

Note: 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.

dawehner’s picture

Issue tags:+Needs tests
StatusFileSize
new715 bytes
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] Unable to apply patch drupal-2054203-2.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]
Berdir’s picture

Status:Active» Needs review

I guess we want to avoid setting it twice :)

Still think whatever we have right now with session.inc is a crazy mess :)

Status:Needs review» Needs work

The last submitted patch, 2: drupal-2054203-2.patch, failed testing.

dawehner’s picture

Issue summary:View changes

Asked @znerol what to do here ... he is more into authentication/session stuff ...

znerol’s picture

I think this should be in AccountProxy::setAccount() because this also covers the account switcher service. Also the now suprious calls should be removed from SessionManager.

almaudoh’s picture

Status:Needs work» Closed (duplicate)

This seems to be covered now in #2328645: Remove remaining global $user which is RTBC.