Can't log into my OGS account (blank screen)

#1

Um
I can’t get into my account.
forum.online-go.com works just fine
but when i go to ogs it shows a blank screen.
Is there a site maintenance thingy going on or something?
If so: i’ll wait until tomorrow.
If not: can i have help?

0 Likes

#2

The site is working for me.

0 Likes

#3

well shit

0 Likes

#4

so what do i do

0 Likes

#5

That happens to me sometimes too. I just click the reload button, or close the window and open a new one to fix it.

0 Likes

#6

If that doesn’t work, then clearing the browser cache may help.

0 Likes

#7

how to clear cache

0 Likes

#8

It depends on the browser. Just google “clear browser cache”.

0 Likes

#9

P.S.: Moved this thread to the Support category.

0 Likes

#10

I’m getting a blank screen too. Clearing cache didn’t help. I’m on an iPad iOS 9. The site works on my iOS 12 phone.

0 Likes

#11

I’m getting blank screen on windows phone. Naturally, PC browser works just fine.

0 Likes

#12

@AdamR, take a look at this.

0 Likes

#13

Hmmmm, I have notified the dev, thanks for the heads up.

Private browsing does not help either? Any details can help. If you press f12 and then go to console, any red errors?

0 Likes

#14

Getting a blank screen here also. Both with iPhone and iPad OS-9. I am attempting to play a correspondence game from Colombia. Same blank screen in private mode.

0 Likes

#15

Hello,

In Chrome Version 49.0.2623.112 m on XP

(I know they are no longer supported!)

I get

No WASM support detected, score estimator falling back to ASM.js mode
es6-shim.js:1827 Uncaught SyntaxError: Invalid flags supplied to RegExp constructor ‘igu’
raven.js:58 SE Initialized

Regards

1 Like

#16

:scream:

2 Likes

#17

Oh frak. @AdamR, at least in @home.pjs’s case, I know what’s the issue and who’s what’s to blame: me the updated profanity filter. The u flag, enabled to block some accented Portuguese words, isn’t supported by old, pre-ES6 browsers. I’ll take care of this.

EDIT: Opened an issue, updated the filter and submitted a pull request. Sorry for the trouble, everyone.

3 Likes

#18

Thanks for the quick fix @lucasfelix :slight_smile: I merged and pushed the update, @dachen11 let us know if this resolves the issue (or not).

1 Like

#19

Least I could do, @anoek. The fix should do for now, but I’ll see if I can download some older browsers and run them with WINE to do some testing with a try/catch. Thank you very much and sorry for the trouble.

2 Likes

#20

No trouble at all, I’ve broken the site more times than I can count, and usually it’s for everyone! :sweat_smile:

2 Likes