Skip to main content
Known Participant
Nov 13, 2019 1:58 AM UTC
Released

P: Deleting a keyword from the keyword list doesn't remove it from auto complete

If someone has already reported this I apologize. I did try to search for it but couldn't find anything with the keywords I was using.

If I enter a misspelled keyword accidentally it continues to show up in "Autocomplete" even though I delete it from the Keyword List.

I've never had this happen before. I recently upgraded to the 9.0 release.

My specific example of this behavior is when I go through to keyword basketball photos one of my keywords is Dribble. In the past I could type in dri and hit enter and it would autocomplete Dribble. I accidentally entered dri9 (the 9 is above the right side of the I key) and when I hit RightArrow to move to the next photo it entered dri9 into the keyword list. On the next dribbling photo when I typed dri it showed dri9 as the top option in autocomplete. I went into the keyword list and deleted the dri9 keyword. That removed it from the photo and from the keyword list but it still shows up in autocomplete.

I tried to see if I could remove it by entering dri9 in a different photo. This added it back to the keyword list. I went into the list and deleted the dri9 keyword again. That removed it from the photo and autocomplete again but then when I tried to enter dribble I noticed that I now had two instances of dri9 in the autocomplete popup. I continued to try exiting lightroom and backing up/optimizing the catalog and entering and deleting the keyword. Nothing worked although I now have four instances of dri9 in the autocomplete popup. There is also another keyword that it has happened on although I can't remember what it is now.

One other thing I did try using the Filter Keywords box in the keywords list and can't find dri9 anywhere.

This topic is closed to new replies. Start a new post to keep the conversation going.

38 replies

Inspiring
Jun 9, 2020 12:55 AM UTC
Thanks for the reply! Hm, not sure how I added a keyword with a space, actually I don't see the space, but when I hit the space bar the problem keyword always appears.

I did just find it in the keyword list and deleted it, that seems to have worked, thanks again.
Translate
johnrellis
Legend
Mar 23, 2020 7:25 PM UTC
Can you provide a precise step-by-step for reproducing the problem?  (I and others have confirmed that the bug appears fixed in our LR 9.2 installations, but that doesn't mean there aren't still problems lurking.)
Translate
Spiketrain
Inspiring
Mar 23, 2020 10:48 AM UTC
Excellent! - So happy! - Now just waiting for the Apple side of things to help me out... can't be far away
Translate
Lauca
Participating Frequently
Mar 23, 2020 10:46 AM UTC
I confirm that in my LR 9.2 on Windows the problem has been fixed.
Translate
Spiketrain
Inspiring
Mar 23, 2020 10:41 AM UTC
Hi - Well it's 23rd March 2020 and I'm running 9.2 on a Mac and this problem still exists..... am I doing something wrong?
Translate
Inspiring
Feb 16, 2020 5:58 PM UTC
Works fine for me so far. Thanks.
Translate
Rikk Flohr-Retired
Adobe Employee
Feb 11, 2020 2:18 PM UTC

Updates to Lightroom Classic, Camera Raw, and the Lightroom Ecosystem were released yesterday and contain a fix for this issue.  Please install the appropriate update and see if it solves this problem. You can read more about the updates here.

Thank you for your patience. 
Translate
Rikk Flohr: Adobe Photography Org
Lauca
Participating Frequently
Feb 2, 2020 5:34 PM UTC
As john said, I used a special tool and my knowledge of databases to fix it (and I'm on Windows).
Agreed to your remark about deleting the whole database (that's why I tried to remove only the bad record).
Translate
johnrellis
Legend
Feb 2, 2020 4:40 PM UTC
Fully agree.
Translate
Participating Frequently
Feb 2, 2020 4:10 PM UTC
Thanks, John, but I have been using LR for many years and it seems like deleting the helper.lrdata completely is taking a hammer to the problem, when all one is trying to do is remove maybe 5-10% of the keywords that are misspelled. The fact the LR has this error (I wouldn't give it the satisfaction of calling it a "bug"), it should be fixed.
Translate