Home› Welcome to the FamilySearch Community!› Ask a Question› Family Tree

Bug Report - Recent Update appears to have corrupted Family Tree Find results.

Options
  • Mute
Gordon Collett
Gordon Collett ✭✭✭✭✭
June 12, 2022 edited July 16, 2024 in Family Tree

(Note: this may be the same bug that has corrupted the results list for Records under Search)

Family Tree Record: Maria Elsabein Brinckmanns MPSR-L84

Screen Shot 2022-06-12 at 2.16.00 PM.png

Her displayed christening place name is: Evangelisch,Versmold,Westfalen,Prussia.

This is standardized to: Versmold, Kreis Halle, Westphalia, Prussia, Germany.

Screen Shot 2022-06-12 at 2.17.03 PM.png

Using Find by ID, the results list shows the standardized version of the place name as expected:

Screen Shot 2022-06-12 at 1.58.15 PM.png

This has been the usual performance for Family Tree since the program routines use the standardized version of place names.

However it was reported today under another post that if one uses Find By Name, the results list displays neither the displayed place name nor the standardized place name, but rather a completely different and incorrect place name plucked out of the Places database:

Screen Shot 2022-06-12 at 2.04.52 PM.png

The strangest part is that the place name shown in the results list is found nowhere on Maria Elsabein's record.

However, if one takes her Display place name and plugs it into the Places database, one sees:

Screen Shot 2022-06-12 at 12.02.58 PM.png

It appears that the results list for Find By Name is taking the Displayed place name and attempting, unsuccessfully, to find a standardized version even though the user declared correct standardized version is right there on her Family Tree record.

Please repair this bug so that the standard displayed in the Find By Name results list goes back to being the user declared standard as it is in the Find By ID results list.

3

Answers

  • Cheryl Viering
    Cheryl Viering ✭✭✭
    June 12, 2022

    @Gordon Collett Thank you for putting all this together.

    All I can add is that this happens for everyone in Versmold, and, I think, other nearby communities.

    0
  • Sam Sulser
    Sam Sulser admin
    June 13, 2022

    @Gordon Collett Yes, thanks for posting this issue separately here. I will make sure this gets to the engineers. Sam ☺️

    0
This discussion has been closed.
Clear
No Groups Found

Categories

  • All Categories
  • 43.3K Ask a Question
  • 3.5K General Questions
  • 577 FamilySearch Center
  • 6.8K Get Involved/Indexing
  • 652 FamilySearch Account
  • 6.6K Family Tree
  • 5.2K Search
  • 1K Memories
  • 2 Suggest an Idea
  • 480 Other Languages
  • 62 Community News
  • Groups