- This topic has 5 replies, 2 voices, and was last updated 11 months, 1 week ago by
.
-
Posts
-
Hi,
I’ve found more issues related to the Index Table search in Ajax Search Pro when testing:
“Minimum Word Length” Option Ignored
The Index Table search seems to completely ignore the “Minimum word length” setting. Even one-letter matches are being included regardless of the configured limit, even if I for example make it as a value of 3, expecting to ignore single and double letters. The other bothersome part is that even when I am using “AND with Exact Word Match” on some pages it matches completely different words where ONLY a SINGLE letter is present in them.Ernest, could you please take a look?
Thanks!
Hi,
I assume you are reffering to this option under the search instance settings? What that does is when set to 3 is, when a phrase is entered, say “3 5 666” it is considered as “666”. So 3 and 5 are ignored. If there is nothing left, then the an empty phrase search is executed.
There is a separate keyword lenght option on the index table settings here: https://i.imgur.com/fvKZCnG.png
I suggest setting that instead, so shorter keywords are not indexed whatsoever. After changing the option you will have to make a new index.On top of that, I recommend setting the minimum character count to 3 so the search doesn’t trigger under 3 characters, just to make it more user friendly: https://i.imgur.com/TcdLEd0.png
This configuration will ensure that no entries below 3 characters are triggered, and for longer entries phrases below 3 characters are completely ignored (as they aren’t in the index)
I tried your configuration suggestions and still have the same issues. I have even set stop words and no effect.
https://imgur.com/a/ZDAhGfA
https://imgur.com/Wtf8JHQWhen I try searching for “на силата” it matches correctly the pages where these exact words are. But if these exact words are not present as a text in certain page, it matches the first double letter word only, as shown in the picture.
Maybe it does not work with Cyrillic fonts only?
On the screenshot it’s highlighted, but that does not mean it was a match for that keyword. The highlighter script runs during the page load, after the query is completed. It is much more likely that either the other word, or a partial was matched somewhere and the highlighter highlights it as it only sees the search phrase – not the matching (it’s impossible).
Cyrillic should work the same way, it shouldn’t affect it.
If you want I can investigate this further, just make sure to add temporary back-end and FTP details, and I will run a debugging session.
Sorry, I did not express myself good enough on my previous post. The highlight is not the problem. The problem is that “Scroll to keyword” goes properly to “на силата” when it matches both words and is present on the page. But, on the other page that I have shown, where “на силата” is not present, “Scroll to keyword” goes on first match of “на”, right in the beginning of the page. Is it possible to make “Scroll to keyword” to ignore, one, two and three letter words?
Oh I see. I’m afraid no.
This is however a borderline bug in my opinion, so just in case I have made an issue request for it. I can see a possibility to try to fix this in some way to perhaps check the adjusted word length. You can expect some sort of an improvement on this for the upcoming release for sure.
- You must be logged in to reply to this topic.