- This topic has 16 replies, 2 voices, and was last updated 3 years, 10 months ago by
.
-
Posts
-
Hello,
How should we change Relevance Options for Custom fields weight (_sku) if we are using Regular engine (Ajax Search PRO)?
Hi,
The terms weight is used for the custom fields (_sku) as well.
If you see no noticable difference, then maybe using the index table engine is the better way to get around this.We can’t get direct hits on sku to the first place, whether it’s an Index table or a Regular engine. tried everything (screenshot attached).
maybe we can use some kind of hook or filter to achieve the desired results?
You don’t get matches for the SKU at all, or only some?
I suspect the issue might be somewhere else then. Can you please add temporary FTP and back-end details – I will check the configuration and debug the queries if needed.
If there are specific search phrases I should test with, let me know as well.
Thank you!
I have tried a few searches, but it seemed okay from my end. For example:
– SKU 1095, results: https://i.imgur.com/0TghKAK.png
– SKU 1253/L, results: https://i.imgur.com/sErIczP.png
Is this not correct?Basically in 90% of the time we search mostly by name or by SKU. I want that if there 100% match with SKU it must be always on the first place in search list. If there are two products with first products 100% match in the name and second product with 100% mach in SKU, then first should be product with SKU 100% match and then product with 100% name match.
Example:
– sku 202. there is a red glove. It shows 3-4th in the search list, but should be first. Screenshot attached.Okay – but all of those products have 202 in their SKUs, exactly a matching word.
Exact field matching is not possible with the Index table engine, it can only check the extracted words.Can you add temporary FTP access as well? I want to check if there is a way to somehow index custom fields as whole fields to a certain length. That might resolve this.
As I mentioned above, we do not have FTP. You can edit files thought admin panel.
With regular engine the same problem appear.
Thanks!
I managed to make an adjustment for better custom field exact matching. Most of the matches should be exact on the custom field. I can not guarantee a 100%, but it should be very very close to that.
Can you please test?
Only a single file was changed: wp-content/plugins/ajax-search-pro/includes/classes/etc/indextable.class.php
..and the index table was recreated using the “Create new index” button.I think I can keep this change in the upcoming release, so you don’t have to worry about it.
- You must be logged in to reply to this topic.