Home› Welcome to the FamilySearch Community!› Suggest an Idea

Index Editing Function Not Working

LegacyUser
LegacyUser ✭✭✭✭
April 7, 2020 edited September 28, 2020 in Suggest an Idea
Carolyn Wheeler said: The function to correct indexing errors has ceased to work for me. Each time I try to correct an error using the "Improve the Name" edit function it will not accept the correction and instead generates an error message that states, "A highlight must be made or you must select no highlight possible."

In all cases when I try to correct a surname I do highlight that name as directed, yet it still generates the error message and will not complete the save action. This happens on both Safari and Chrome. I am using Safari 12.1.1 and Chrome Version 80.0.3987.149 (Official Build) (64-bit) on a MacBook Pro running OS 10.14.5.

See below for a screenshot
Tagged:
  • New
  • Indexing
0

Comments

  • LegacyUser
    LegacyUser ✭✭✭✭
    April 6, 2020
    Carolyn Wheeler said: It appears that the above error is generated when attempting to highlight a surname. If I choose the highlight given name option then the error message is not generated and the change saves correctly. But every time I attempt to highlight a surname it generates the above error message.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 6, 2020
    Brett said: Carolyn

    Question; and, something to consider ...

    Do you participate in the "Community.FamilySearch" Forum?

    If you do, have you raised this problem/issue in the 'Group' of "Indexing Chat" in the "Community.FamilySearch" Forum?

    Indexing Chat

    https://community.familysearch.org/s/group/0F93A000000LissSAC/indexing-chat

    https://community.familysearch.org/s/...

    That 'Group', in that Forum is, very active; and, a good place to raise problems/issues.

    Just a thought.

    Brett

    .
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 6, 2020
    Juli said: Her question has bubkus to do with indexing, though. She's talking about the after-the-fact index _correction_ feature, which I know you're aware of. I don't believe there is a Community forum dedicated to it.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 6, 2020
    Carolyn Wheeler said: No, in answer to Brett's question, I have not. I do tend to agree with Juli as I think it is more of a technical/programming issue. Seems to me that something in the code needs to be fixed. Wish a programmer would respond.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 6, 2020
    Jacob Reid said: Thank you for reporting this issue, the team is working to get it fixed.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 6, 2020
    Carolyn Wheeler said: Thank you so much for letting me know that it has been acknowledged and is being addressed!!! You are very much appreciated - in many ways!!!
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 6, 2020
    Brett said: Juli

    Well spotted.
    I hang my head in shame.

    Brett

    .
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 7, 2020
    Carolyn Wheeler said: I think you must have fixed this as it is now working. Thank you very much!!!
    0
Clear
No Groups Found

Categories

  • 28.4K All Categories
  • 22.8K FamilySearch Help
  • 111 Get Involved
  • 2.6K General Questions
  • 423 FamilySearch Center
  • 431 FamilySearch Account
  • 4.1K Family Tree
  • 3.2K Search
  • 4.5K Indexing
  • 591 Memories
  • 6.1K Temple
  • 308 Other Languages
  • 34 Community News
  • 6.4K Suggest an Idea
  • Groups