Skip Navigation

[Resolved] no search results

This support ticket is created 6 years, 1 month ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

This topic contains 1 reply, has 2 voices.

Last updated by Beda 6 years, 1 month ago.

Author
Posts
#1186925

i made a simple search form here:
hidden link

It was working very fine.
i test it multiple times and suddenly it stop showing results , and I did't do anything
I am trying to figure out for some hours - what is the problem but I can't find it

I do have more then 1000 posts...is this a problem?

Can you help?

#1187299

It seems you load the results on a second page, is this correct?
So you have split the view in a search form and results in a section on another page, likely.
Currently there is an issue with that method, https://toolset.com/errata/toolset-maps-distance-search-location-input-cannot-be-used-when-the-views-is-displayed-in-split-mode/, however, that affects only distance filters so far.

I took a look at this after logging into your site.
I saw, the backend registers the filters to listen for article_lang and article_writer, however, the Query I see in the front end is corrupt:
article_writer%5B%5D and article_lang%5B%5D.
This is wrong since there are no special characters, nothing should be url encoded.
%5B means [, %5D is ], so those are opening and closing square brackets, that should not be in the URL at no cost, as it obviously will break the query and change the listening query args from article_writer and article_lang to article_writer[] and article_lang[].
That's wrong and will return no results.

I see also in your View, the shortcodes seem manually edited.
Normally the "field" attribute of the Custom Search ShortCodes should feature a wpcf-prefix if it's a Toolset Types Fields but they do not, even though those are Toolset Types Fields.
Also, it's the wrong filter shortcode, it should be a wpv-control-postmeta and not wpv-control only if this is a Post Field.

Now, since it seems there is quite a lot of manual edits that will break the filters and views, I suggest to create a new View and insert the Filters with our GUI we offer for it.
That should then work without issue.