I was looking at the record for one of our new players, and I saw that the list of his 2025 games doesn’t display all the names of his opponents.
However, oddly, if I click on the “NY” displayed instead of an opponent’s name, I call up the ratings page of his actual opponent.
I just thought I’d bring it to the attention of folks.
I have reproduced the error and reported it.
similar display issue, not sure if it is related,
some opponents have strange symbols displayed in their names:
I think that’s a language encoding issue that happens when people register for a membership online. Not much we can do about it except fix it on a record-by-record basis in the membership system.
the above screenshot is looking at YEAR: 2025 on page https://ratings.uschess.org/player/32116347
For the displayed name Abhimanyu $^29MEKA, click and get into member’s page, US Chess displays correctly without $^29
For the displayed name Steven +MSHUMSKIY , click and get into member’s page, https://ratings.uschess.org/player/32674097 displays correctly without +M
so I think, it is a randomly-happening display issue, not a mess in the membership system?
It is likely the rating system is pulling the name information that was inputted into the pairing program (swiss sys, win td ect..) when pulling game information from 2025 ect..
Pulling from the pairing program upload would also include any notes that the TD may have added to the name (expired membership ect..)
Should be two easy ways to fix this.
you could go record by record and fix the name in the tournament upload file
it is probabaly also possible to change the programming in the rating system to pull the name from the member database instead of pulling the name from the tournament upload file.
Both seem like reasonable solutions.
I’m not sure if US Chess would want to open a ticket on this issue (might be a low priority issue though)
Cheers.
Not the way the system works. It pulls all displayed names on crosstables etc from membership records, which are maintained on CIVI-CRM and synced to MUIR.
It also appears the issue above has been resolved (fixed).
At least I am no longer able to recreate the bug mentioned above.
we’ve had multiple bugfixes deployed in the last two days.
