[Resolved] Too slow to load next slide page or search results

[Author]

Posts

[francescoG-3]

For now I have solved the Slider issue setting the query as Custom Field "in_evidenza" is boolean different to constant "".
And the custom search also for now I think is solved too, I have tested it and it work fine.
But now, the time to load the next slide page and the next search results page or to do a custom search with filter is too long again....

And I need to display the selection box to wait the custom search results. Now the selection box appear only when I paginating into the results and not to wait the results after a custom search.

[Shane]

Hi Francesco,

The homepage slider you are referencing correct?

Also I've added this to your search and the graphic should now be displayed.
[wpv-filter-spinner spinner="hidden link"][/wpv-filter-spinner

Please let me know if this helps.
Thanks,
Shane

[francescoG-3]

Hi, thanks for your helpfull, but I still need more help.
I don't know what happened but now if I do a search with price value or the other between filter, the search return wrong results...
For example, if I do a search by price from 0 to 20.000, the results have some properties with price same as €120.000 or other value over 20.000.

Why?

New threads created by Christian Cox and linked to this one are listed below:

https://toolset.com/forums/topic/split-price-filters-do-not-work-as-expected/

[Christian Cox]

Hi Francesco, Shane is unavailable today and will return tomorrow if you need additional assistance with this issue. I noticed that you have a new question about price filters. To keep the forum organized, I have created a new ticket for that issue and I will follow up with you there.

[francescoG-3]

Hi, thanks.
Can you help me in the other ticket about the issue?

[francescoG-3]

Hi, the filter issue is solved thanks.

But now the results return after the custom search is too slow...

[Shane]

Hi Francesco,

I've re-enabled the caching plugin and the search seems to be moving faster on my end.

Could you check on this as well ?

Also it doesn't seem that you've added the spinner graphics shortcode to the filters.

[wpv-filter-spinner spinner="<em><u>hidden link</u></em>"][/wpv-filter-spinner

You can add that to the filter section of the archive and it will load the waiting spinner.

Please let me know if this helps.
Thanks,
Shane

[francescoG-3]

Thanks for the answer.
I have tried to insert the spinner, but it load every time when I select a filter not when I click on Search button.

[Shane]

Hi Francesco,

I've added it to the page and it seems to be working fine for me.

hidden link

Thanks,
Shane

[francescoG-3]

Yesterday I had added it also in homepage and in both search filter the spinner started every time I selected a filter.
Now it work fine on the link you have posted.
I have added it now on the homepage "ricerca avanzata" Views, but it is not displayed!!!!

[Shane]

Hi Francesco,

I see the issue, I believe this is cause by the search results and the search bar being separated. Ideally you have them on the same page but in a typical use case with your setup the results would be on a separate page.

So I suspect this is the issue.

Thanks,
Shane

[francescoG-3]

Other issue I have found is in the search results when there is only 1 property.
I have setted the width per properties = 19% + 0,5% for left and right margin.
From 2 to 5 property the width is correct, but when there is only one property it is displayed smoller but the width value is correct.

Sorry, I have found the issue!!!

[Shane]

Hi Francesco,

Could you send me a scenario that results in 1 result ?

Thanks,
Shane

[francescoG-3]

I have solved it. A css width value was not declared....

sorry me!

[francescoG-3]

<cite>
Hi Francesco,

I see the issue, I believe this is cause by the search results and the search bar being separated. Ideally you have them on the same page but in a typical use case with your setup the results would be on a separate page.

So I suspect this is the issue.

Thanks,
Shane
</cite>

What should I do to solve the issue?