{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
1/13/2013 1:08:35 PM
5
Well i'm from the UK and the site was working for me from the first minute.
English
-
The way Achronos explained it, it was a bug to do with your system clock. If you were in any timezone later than GMT, the site would think your cookies had expired even if you'd just logged in. While I'm in the US at the moment, my computer's system clock is set to my native Australian time, which is why I couldn't use my own computer to log in, but Harlow could log me in just fine using his.
-
Edited by WurstsaIat: 1/13/2013 6:06:44 PMI'm in CET (UTC+1) and it still worked, but I heard that someone from Finland had problems. So it was probably just a problem for everyone in UTC+2 or later.
-
What the hell?! That must haved sucked.. :(
-
Yeah, the worst thing is that if I'd known that was the problem, I'd just have reset my system clock. But I had no way of knowing that was it, so I was stuck clearing cookies, restarting my computer, etc. etc. constantly in the hope that it'd suddenly all click into place. To the webteam's credit, they responded really well to mine and other people's constant pestering and fixed the issue as soon as they could.
-
Good old Bungie. I did wonder where half of the community had gone too..
