[AndrewD]

Originally Posted by vbboarder

The saved search feature is not working correctly. There's 3 issues:

1. When the search option to find "all words" is selected, it acts the same as "any words." For example, if you put in: mp3 audio, "any words" search would find entries that have either mp3 or audio in its text, "all words" search would find entries that have both mp3 and audio (mp3 & audio do not need to be adjacent) in its text, and "exact phrase" search would find entries that have mp3 audio (mp3 & audio needs to be adjacent to each other) in its text. Well, LDM doesn't do that when "all words" is selected.

2. When I save a search and edit it later, then old settings still remain. For example, I saved a search of "mp3 audio" and selected "exact phrase", then I edited that search to change it to "all words" and marked "update saved search", then I visit the "Saved Searches" link, the search description will read both "exact phrase" and "all words." It might just be a descriptive bug versus a functional bug because when I click on the "mp3 audio" search link, the header states that it's searching "all words" only (though it's searches incorrectly - see bug #1).

3. The saved searches for Profile Searches can not be edited by the user. Though not a functional bug ('cause it works), it results in a logical bug because the search semantics is not correct. For example, if the admin enabled occupation profile searching in LDM settings and the user put in "web developer" in his profile, then when he goes to the LDM Search menu, he gets 2 separate saved searches: "web" and "developer" when it should be "web developer." I think the solution is 2 parts: enable an option to allow profile saved searches to be delimited by commas, and enable the profile saved searches to be edited similar to the self-made saved searches.

I'd noticed the first two problems, and I think I've fixed them in 2.3.0 beta 1. There were bugs particularly in the highlighting code (particularly nasty to fix for languages requiring utf8 character sets) . Thanks.

The third one (profile searches) is a bit more problematic, because, as you say, the feature is working as originally designed. But it's a bit of a fossil and needs rethinking. The inconsistency with other saved searches has only just become apparent, because I only recently made this feature visible - it was there for a couple of years but only to admins.