Home › Forums › Product Support Forums › Ajax Search Pro for WordPress Support › Getting Mixed Search Results and Need Help with Filter Menu › Reply To: Getting Mixed Search Results and Need Help with Filter Menu
Hi,
1. Unfortunately no. Conditional filters are not yet supported at this moment.
2. I have changed that on the back-end to this. The values are indeed correct now, and the filter works correctly as well.
3. Okay. First I changed the minimum number of word characters to 1 here with a secondary logic. That will allow singular character numbers to match partially.
The numbers are covered, but the problem with these searches is the “bed” and “beds” keywords. Those do not occur anywhere in the text, nor in any taxonomy, nor any custom field – so it does not match.
However the way you want this to work is not possible without massive keyword additions. Basically you would want the plugin to somehow “recognize” which numeric field to look for, depending on what exactly is entered. That is way beyond the capabilities of this plugin, that needs some machine learning stuff, and those are extremely expensive and very hard to implement.
The kind of workaround for this is:
– Creating a simple text custom field
– Entering these desired phrases comma separated
– Selecting this custom field for search
– And also only allowing exact matches without secondary matching in the plugin settings
With that, you have a comma separated list of additional keywords – which can be matched almost exactly. By “almost exactly” I mean some exceptional cases, where for example the field content is:
3 beds, 1234 square ft, 4 baths
The user enters 234 square ft, and it will still match the query. To get around that, each additional keyword would have to be placed in a separate custom field, and that is just not worth it at all in my opinion.
This could be potentially even automated with a snippet, upon post saving it could fetch the values from the bedroom, bathroom and sq ft fields, and generate the additional keywords manually, and then put them into that new custom field to search for.
I think that is the least amount of work for the best acceptable results, but this is only my opinion. It is beyond this support, but I am trying to help as much as possible.