[Closed] Search broken in wordpress search and views, except for one.

[Author]

Posts

[ianG-5]

Tell us what you are trying to do?
Add custom fields in custom post types to all search

Is there any documentation that you are following?
Just the Relevanssi settings

What is the link to your site?
hidden link but isnt public available today, can be accessed via IP

I have one toolset view that the search is working fine on, and I want the same functionality on other views and elsewhere on the site, but nothing seems to work unless I directly duplicate the view.

I appreciate this may not be a toolset issue directly but hope there is somewhere you can point me.

[Nigel]

Hi Ian

Let me share the relevant guide for using Relevanssi to include custom fields in Views text searches: https://toolset.com/course-lesson/searching-texts-in-custom-fields-with-toolset-and-relevanssi/

Assuming that you have already followed those steps, if you are seeing results where it appears to be working in one View but not in others I would check the cache status of your Views and clear them if necessary.

Go to Toolset > Views, you can clear them from there. (If you can't see that menu option go to Toolset > Settings and opt to show both the block and legacy interfaces.)

Does that help?

[ianG-5]

Hi Nigel,
Yes I went through that originally and have now done it again.

Its not two different views, it actually a view which works great but a normal wordpress search on the front end that doesnt.
Originally it would only bring up content from front end pages, with a lot more content it now is bringing up some results but not much.

Does the filter at a top of a view rely on the standard search or is custom to the views.

[Waqar]

Hi,

Thanks for writing back.

The search form/filters added on top of Views or WordPress Archive, use the WordPress standard search but extends it based on the settings added in that View or WordPress Archive. But this only affects that specific View or WordPress Archive and not the search results globally.

If you'd like to customize or extend the standard search results, you can create a WordPress Archive specifically for "Search results":
https://toolset.com/lesson-placement/lesson-placements-1621271-1622285/

In case, you're experiencing something different on your website, you're welcome to share a video showing what you mean.

regards,
Waqar

[ianG-5]

I am still having massive trouble with search, I have even lost the one view that was working.

I have a backup of the site that I am able to go back to but I am still unable to find any setting that is blocking this.

I have been through the Relevanssi settings and all look the same, inputting a post id in Relevanssi Debugging tool in both sites reveals the same details.
Building the index makes no difference.

[ianG-5]

I have found the cause, but I really need to understand why this is happening.

The difference is when I add ...
Post status filter
Select posts with status of any.

Search stops.

[Waqar]

Thank you for sharing this update.

I've performed some basic tests, but couldn't reproduce this.

Can you please share a clone/snapshot of the website, so that I can investigate this on a different server?
( ref: https://toolset.com/faq/provide-supporters-copy-site/ )

Please also include some links to the example pages where these views can be seen.

Note: I've set your next reply as private.

[ianG-5]

Getting the database into a state my client is willing for me to share is a bit of work, so I have still been investigating.

I think it mush be a custom post status issue.

I have: publish pending draft auto-draft future private inherit trash request-pending request-confirmed request-failed request-completed wc-pending wc-processing wc-on-hold wc-completed wc-cancelled wc-refunded wc-failed hidden any

The issue was present when I select any, which is probably an uncommon usage. when I limit it to "publish pending draft" it works fine.

[Waqar]

Thanks for writing back.

Without actually seeing the involved search view and the plugins active on the website, it would be difficult to troubleshoot this. But limiting the post statuses to selected ones seems like a reasonable solution unless you do need the results from "all" post statuses.

You're welcome to share online access or a backup/snapshot of any website where this issue can be seen and we'll happy to investigate this further.