Please keep the forum protocol in mind when posting.

Judging Technology » Post: WER - country bug

WER - country bug

Oct. 19, 2013 02:26:17 AM

Amand Dosimont
Judge (Level 1 (Judge Academy))

BeNeLux

WER - country bug

I can't add two players to a GPT. When I add their country and try to enroll, I have this message
“country is invalid. Please select the valid country”
How can I solve this?

Oct. 19, 2013 02:49:38 AM

Richard Drijvers
Judge (Uncertified)

BeNeLux

WER - country bug

I have been contacted by another judge who has the same problem right now.

This appears not to be an isolated incident.

A fix would be nice. :)

-R.


2013/10/19 Amand Dosimont <forum-6557-0a37@apps.magicjudges.org>

Oct. 19, 2013 02:51:50 AM

Monsuporn Lauhaphand
Judge (Level 3 (International Judge Program))

Southeast Asia

WER - country bug

I found the work around solution.

Add the problem player in local player tab and enroll player from that
local player tab.

hope this help.

Oct. 19, 2013 03:12:46 AM

Richard Drijvers
Judge (Uncertified)

BeNeLux

WER - country bug

work around confirmed.


Thank you, Mr. Smith!


-R


2013/10/19 Monsuporn Lauhaphand <forum-6557-0a37@apps.magicjudges.org>

Oct. 19, 2013 03:25:12 AM

Kim Warren
Judge (Uncertified)

United Kingdom, Ireland, and South Africa

WER - country bug

Ah hah. Not just a Wales problem, then.

Oct. 19, 2013 03:33:43 AM

Amand Dosimont
Judge (Level 1 (Judge Academy))

BeNeLux

WER - country bug

thanks

Oct. 19, 2013 03:43:57 AM

James Do Hung Lee
Judge (Level 3 (Judge Foundry)), Hall of Fame, Scorekeeper, Tournament Organizer

USA - Pacific Northwest

WER - country bug

I had this problem yesterday evening, contacted the WER team, and they have it at the top of their priority list. Until the fix is pushed, the aforementioned work around is confirmed and valid.

Oct. 19, 2013 08:50:45 AM

Jim Shuman
Judge (Level 2 (Judge Academy)), Scorekeeper, Tournament Organizer

USA - Southwest

WER - country bug

I was at a Wizards info meeting for Retailer's on Thursday and this bug was generated in the last update and is known.

My understanding is it is to be fixed by Thursday this upcoming week.