Weird bug: "undefinedundefined" in Standard Place
While trying to explain to someone how to fix an incorrect standardized place, I discovered a weird bug. It occurs if the display and standard are not the same, i.e. there's a separate place field and standard place drop-down in the Edit popup. When I first open such a conclusion for editing, if I click the Standard Place drop-down, it shows "undefinedundefined" instead of the type and date range for the standardized place.
I checked several profiles, and the same thing occurred with all Vitals conclusions that were not displaying the standard value. (All of the places were something-something-Hungary, 'cause that's true of all of my ancestors, but I don't think it matters.)
Comentarios
-
Is this still happening? It looks like a program query to one section of the Places database not going through properly which should be just a temporary glitch.
1 -
Yep, still happening. I went and found a different vital on a different profile, just to make sure it's not just on my grandfather's birth.
(This is from my spouse's side, where I went looking in hopes of a non-Hungary example, but he's almost as monochrome as I am.)
1 -
Thanks, I've logged a issue with the team.
1
