Home › Forums › Product Support Forums › Ajax Search Pro for WordPress Support › How trigger live search after Custom Code: automatically select filter values? › Reply To: How trigger live search after Custom Code: automatically select filter values?
Dear Ernest
Thank you for your fast reply. It helped and it works now. I am happy. 🙂 I used the option 2: auto-populate. I hope I will not notice any negative
For Option 1. I wouldn’t know how to add ?asp_s= to the custom code or the Ajax search instance.
The only a bit negative detail is that you see the page refresh moment. The post widget shows first all images and then automatically refreshes to show the selected search results. This makes the user experience a bit slower and could look like a bug. But ok, I can live with that.
But now let’s continue the user experience. The problem is now the URL. Is it possible to redirect from the Archive URL, Categories, Tags URL automatically to the main downloads-post URL?
If Ajax Search Pro is handling all search results, it would make sense, that WordPress shows no category & tag archive URLs, but always just this base URL for all downloads-post types:
https://www.illuminatoren.com/downloads/
Otherwise it will be somehow confusing if the user is watching the URL while selecting other taxonomies. It looks confusing because Ajax Search Pro takes over the WordPress Search results. So in functionality anything is fine, the user can deselect the “evodia-aus-philiippi” category and choose new categories or tags and Ajax Search Pro will show the correct results, but the URL looks strange, because it remains at the the first WordPress archive query. So the user will see search results that are the opposite of the URL. Some critical user with technical attention could think that there is something wrong and that they are missing some search results because of this wrong URL.
https://www.illuminatoren.com/downloads/category/bibelfiguren-charaktere-der-biblischen-geschichten/evodia-aus-philippi/
This is not a very dramatic problem, I could live with this, but it would be nice if it is possible to solve. But I am not sure if this is a problem from Ajax Search Pro or I have to solve it differently.
Thank you for your answer. 🙂