{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by McMesser:
7/19/2014 4:57:03 PM
12
I've also got the problem now, with no clear way too fix it. Anyone know of a way to contact Bungie to let them know this has happened to us?
*Edit* Just sent a tweet regarding the error to #bungiehelp. See if that gets their attention, others might wanna do the same.
English
-
I just sent an Bungie an email. Couldn't find one for the Beta but found an email to report bugs found on the website but I'm sure it will go to the same place.
-
Edited by Nofyn: 7/19/2014 6:31:46 PMWhat is Bungie's email/what email did you send it to? I have more test data for them.
-
The only email I could find was bnetbugs@bungie.com. I sent everything that I did before it happened. I hope they notice this problem.
-
Cool, I'll throw them a email myself. The more messages we send the more likely they'll see it and get to it!
-
I didn't email them, I don't think they have a email for beta info. I just sent them a tweet on Twitter about my error code using the #bungiehelp tag
-
I'm talking to a person who seems to be working to fix the problem so we are getting somewhere at least.
-
Sweet, how did you get through to someone BTW?
-
Did you try my fix? It's only a workaround and the issue definitely needs to be addressed but it's gotten me up and running after hours of frustration.
-
No, couldn't get it to work. But I'm not very computer savvy. But thank you anyway :)
-
Bummer. Hope Bungie addresses this soon.
-
Yeah, I just want to hear something from them about it all. I hope it get's fixed for the downtime on Monday/Tuesday.
-
They are working on it getting but are getting info right now though.
