Forums › Forums › Search & Filter Pro › Results reinitialized between each search
Tagged: filtering, second filtering, second search
- This topic has 6 replies, 3 voices, and was last updated 8 years, 8 months ago by Ross.
-
Anonymous(Private) November 19, 2015 at 12:09 pm #30173
Hello,
I’m using Search And Filtering Pro 2.0.3 on a WooCommerce website.
I’m using “WooCommerce Shop” as “Display results method”.
It works fine the first time I use the widget, but if I use the search a second time, then entire page is reinitialized. If I try to use the search again, it works fine the first time one again, but not the second time. And so on and so on…
Any idea of what is happening?Thanks!
Ross Moderator(Private) November 19, 2015 at 12:11 pm #30175I’m guessing this is with Ajax enabled?
It sounds like your results container (set in the display results tab) is too broad, and also reloading the whole search form itself.
You should use a different selector which contains only the results to reload rather than a large area.
I think on WooCommerce actually its best to set this to
#main
if my memory serves me, but this might not be correct for all setups.Thanks
Anonymous(Private) February 24, 2016 at 4:06 pm #37839Hi, I have the same problem with the difference that I’m not using ajax. The filter made from the home page works fine but, when I try to do another filter from another page, returns all products without any filtering. The result URL for the second filter show domain.ca/?sfid=1170 but not the rest of the filtering parameters. Unlike the first filtered that shows domain.ca/?sfid=1170&_sft_location=montreal&_sft_apartmenttype=2-bedroom and retrieve the correct product. I’m using the same shortcode in all the pages so I do not find the problem. I don’t know if I’m doing something incorrect or something is happen with the URL in the second filtering.
Ross Moderator(Private) February 25, 2016 at 10:04 am #37906Hey Louise can you open a new ticket?
Thanks
Ross Moderator(Private) February 25, 2016 at 4:56 pm #37959Hey there, I had a look, I think this bug is resolved in S&F 2.1, can you update the plugin?
Thanks
-
AuthorPosts