[Resolved] Display related posts in Relevanssi search result

[Author]

Posts

[Vane]

Thinking about it more:
Toolset is useful mainly for creating and managing directory style websites, managing non-WP-default entities, their attributes (CF, CT, etc.) and their relationships and their different displays (single, archive, custom), etc.
It allows us to display them in very complex ways, but a directory site is not only about displaying data, but also about preparing and providing their data properly for searches.
In most cases the user doesn't browse but searches,
so if I have a university website with CPTs like
- campus
- classroom
- professor
- subject
- course
- event
etc.
with complex relationships, cross referencing to data of another CPT (like Book Author Name in Book CPT in my OP),
user, who searches for string
"math"
wants to find all related results of every each CPT.
It is not a must have only now in 2020, but it was that also long years ago.

I honestly don't believe how this search feature doesn't work properly,
and no, I won't waste my time to add it as a feature request... ( my 2nd reason not to do: I won't get even a response at all )

So pls. Toolset fix it ASAP, not only for me but for the Toolset community!

[Luo Yang]

Hello,

Thanks for the comments, but according to our document:
https://toolset.com/documentation/user-guides/views/searching-texts-custom-fields-views-relevanssi/

You are asking for some features which are not Toolset built-in features:
wants to find all related results of every each CPT

So the best appoach is file a feature request here:
https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/

Your request will be took care of by our support manager.

And according to our support policy:
https://toolset.com/toolset-support-policy/

we cannot guarantee adding everything that you request and we cannot always do it in time for your upcoming project.

So you might not get a response.

Since this problem is related with Relevanssi plugin, it is also a limitation of Relevanssi plugin itself, as a workaround, you might consider these:
1) Output all related post's information into the single post content:
https://toolset.com/documentation/post-relationships/how-to-display-related-posts-with-toolset/
2) Use CSS codes to hide above "related post's information"
3) Rebuild the Relevanssi index, and test again

[Vane]

Hello,

as I described in my OP, being able to search text and find all relevant results on a website (mainly directory websites) is and has been a must have for years, for decades.
Either with Relevanssi or without that.

I studied a WP course at Udemy which builds up a directory theme from zero to live product (in 15 hours, slowly speaking) from hardcoded HTML and existing CSS, (changing hardcoded HTML to PHP and javascript) what properly finds all strings in related entities like:
- campus
- classroom
- professor
- etc.
I referred to in my OP.

It uses ACF though...

------

Feature requests:
I added a couple, but never got a response, so I don't have any glue whether it is on the roadmap or not, do you find it useful or not, etc.

You can see how others are doing it, eg.:
hidden link

------

The issue basically would not be related to Relevanssi, if Toolset could do that text search properly.
You created the custom search PHP code what work in my specific case - and I really appreciate that -, but Toolset should include a general one in its pack, either with Relevanssi or without.

https://toolset.com/documentation/post-relationships/how-to-display-related-posts-with-toolset/
you could check that my Relevanssi settings were correct (new CPTs and all CFs were selected) and you had to create a custom code, a filter to work properly.

In this docs Toolset writes:
"Other fields, like checkboxes and radios should not contain textual data."
In default WP we can search for blog Categories and Tags, in Woocommerce we can search for Product Categories, Brands, selectable Product Attributes etc. , which are clearly checkbox, radio or dropdown type,
so I really don't understand Toolset's imperfect text search operation...

[Luo Yang]

The feature request list was removed for some reason, so only our supporter managers and devs can see future request list.

In order to search the result in custom fields and taonomy using search input box outputted from shortcode [wpv-filter-search-box], it requires Relevanssi plugin, see our document:
https://toolset.com/documentation/user-guides/views/searching-texts-custom-fields-views-relevanssi/

As the above document mentioned:

This is because these types of fields normally include text. Other fields, like checkboxes and radios should not contain textual data.

That means, it is not recommended to search the result in checkboxes and radios fields.

More help:
https://toolset.com/documentation/user-guides/views/views-shortcodes/#wpv-filter-search-box
Adds a search input to your filter

[Vane]

I never ever wrote I want to do text search in a View, sorry.
I didn't even wrote I want to do it in Toolset.
I'd prefer to use WP's default search, but I don't mind if Relevanssi, Toolset or whatever search method and tool finds all related strings which assigned directly or indirectly (via Relationships) to a Toolset entity, like CPT, CT, CF or whatever.

Here in Toolset Forum in top right there is a Search icon and neither me nor Toolset cares what provides the results if that is good and relevant!

The text search is not the strong point of Toolset...
If I want to find Toolset's Changelog and I either try:
- https://toolset.com/?s=+changelog&lang=en
or I try in Google:
- changelog site:toolset.com
none of them finds it ( though the Google result finds a support forum thread which refers to the Changelog's URL, but doesn't list the Changelog itself on the first result page);
the Toolset page search (which is not a Forum search, seeing the search URL) find totally irrelevant, forum related results.

I'm honestly very disappointed with this, wasting days and working on basic stuffs like text search, which should work without any customization.

(BTW I searched for Changelog because latest update screw up one of my site and that change also was not listed in Views 3.0.2's changelog. Some Support person in another thread referred to a way of operation change which worked the way I wanted with 3.0.1 but wrote it doesn't work that way in the next (I suppose 3.0.2).
I honestly didn't believe Toolset changes an operation logic without either giving us the option to select how we want to use it or simply keeping that old way...)

So I'm very frustrated for days (weeks), because basic use cases are not handled by Toolset properly.

[Luo Yang]

For the WordPress built-in search box, you can try the Relevanssi workaround I provided in my first answer:
https://toolset.com/forums/topic/display-related-posts-in-relevanssi-search-result/#post-1455691

you might consider these:
1) Output all related post's information into the single post content:
https://toolset.com/documentation/post-relationships/how-to-display-related-posts-with-toolset/
2) Use CSS codes to hide above "related post's information"
3) Rebuild the Relevanssi index, and test again

Above workaround is simple, you just need put all related post information into the post content, use CSS codes to hide them, so Relevanssi will be able to index them and display them in the search result.

[Vane]

- You might missed the point that in this ticket, what you splitted from another, I don't need a help in a specific case.
I tried to convince you and basically Toolset, that this level of text search I described is a must have.
I appreciate that code, I know how to tweak that, so thank you for that, but this is not the level what most of the Toolset clients want, it should be a feature included into the GUI.
Now, if we see either Toolset's or Relevanssi plugin's setting pages, we can suppose it works properly, but it isn't!

- "Output all related post's information into the single post content":
Are you serious that in such a complex case I described in my OP, where I have related CPTS of:
"- campus
- classroom
- professor
- subject
- course
- event"
I should add "all related post's information into the single post content" ?
This is when you eat your soup with a knife...

I'm not happy, but not because of you, I think Toolset support personnel is basically good (knowledge, attitude),
but I'm not happy because of Toolset's product development concepts, feature selections etc.

I close the ticket because I don't have more time for this.