- This topic has 7 replies, 2 voices, and was last updated 1 year, 4 months ago by
.
-
Posts
-
Hi Samuele,
Sure! You can enable that here.
Great! Many thanks indeed!
Speaking of live results, I excluded some product categories. It works, in that products belonging to those categories aren’t shown, however they are included in the result count, i.e. the number of results takes into account even the excluded categories.
Why is that?
Thanks again,
Samuele
I assume you mean the number reported on the results page? That should still account of the exclusions, however it is not controlled by Ajax Search Pro itself, but the theme. If it uses a custom query of some sort, that could explain the difference, but that is very rare.
If you want I can take a look, but for that I may need back-end as well as SFTP access to do a basic debugging.
I mean the number reported on the live results area.
Please have a look at the attachment. If I search for “Correnti” (a term of the ec_collana i.e. ‘book series’ taxonomy), the term shows 12 results. However, if I click on it I am redirected to the taxonomy archive page including only 7 results (https://www.musicandbooks.edizionicurci.it/ec_collana/correnti/), which is correct.
In fact, I excluded the digital editions (product_cat=‘digitali’) form the Ajax Search Pro settings as well as form the archive page query. Yet, they are included in the number count displayed next to the term in the live results area. For this specific ‘series’, 7 books are available in printed format + 5 are also in digital format (adding up to 12, hence the number next to the term). I’d expect that the term result count, in the live results area, indicated 7 results.
I hope I explained myself clearly enough.
Oh okay, that is different.
The number of items shown there is requested from the WordPress core itself via the get_term_by function, it is not the plugin querying it, it only prints the count reported by WordPress itself.
From what I know, this number is heavily cached for performance reasons. It is possible that you may have to update or visit the category page on the back-end to update it. If the number is still incorrect, then something else must be changing it – either a 3rd party code or a plugin via a custom code, but it should always report the correct count.
The number is indeed correct in that it corresponds to that shown on the backend. However, I thought it might be a way to take the exclusions in the Ajax Search Pro settings into account.
Thanks for clarifying
- You must be logged in to reply to this topic.