Skip Navigation

[Resolved] text search in title, body custom fields, different result then title and body

This support ticket is created 4 years, 2 months 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.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 13 replies, has 2 voices.

Last updated by Wim 4 years, 1 month ago.

Assisted by: Minesh.

Author
Posts
#1871437

Wim

I have a custom post type set up with custom fields and search in combination with relevanssi.
All is working except for one detail.
If the text search is set up to search in the title, post body and custom fields then the following query does not give any results on this page ( C# ):

hidden link

search parameters:
hidden link

If I disable the text search in the view query results to search also in the custom fields then the the query for " C#" does give the correct results

So relevanssi is working correct however it looks like enable or disable search in custom fields produces differrent results while the C# is both in the title also.

I do hope the above description is clear?

#1872809

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

First of all - After checking to debug the information you shared with us, I found that you are using outdated Toolset plugins. We always recommend running your site with the latest stable release plugin version.

*** Please make a FULL BACKUP of your database and website.***
Could you please update ALL Toolset plugins to it's latest officially released version. You can download the latest plugin release from your accounts page (You can find the Views plugin under Legacy Plugins tab):
=> https://toolset.com/account/downloads/

Once you update the plugins - Do you see any difference? If no:
If I disable the text search in the view query results to search also in the custom fields then the the query for " C#" does give the correct results
==>
when you say above, how you disable the text search?

Can you please share access details.

*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.

I have set the next reply to private which means only you and I have access to it.

#1872927

Wim

Hi Minesh,

I will update the pugin version to the latest this weekend after testing.

To elaborate more on this:
If I disable the text search in the view query results to search also in the custom fields then the the query for " C#" does give the correct results
==>
when you say above, how you disable the text search?

I do not disable the text search but I switch from search in title, post body and custom fields to search in title and post body alone.

If I perform a search with the option to only search in title and post body then the post with C# in the title is found
If I perform a search with the option to search in title, post body and custom field the post with C# in the title is no longer found if you enter C# as search term.

#1872941

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Can you please share access details and let me see whats going wrong with your setup.

*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.

I have set the next reply to private which means only you and I have access to it.

#1876791

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Thank you for sharing information. I'm able to see the issue.

Please allow me to escalate this issue to our next level support. Please hold on for further updates.

#1877217

Wim

Hello Minesh, thanks for the update and looking forward to the next reaction.

Kind regards,

Wim

#1877901

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

The thing is that when I run a test with my local host and created a post which has the title set has "Movie two C#" (without quotes).

And then I registered the custom fields to relevanssi and indexed it. But when I see the table that holds the keywords of Relevanssi namely wp_relevanssi - I see all other keywords are indexed. Only the C# keyword is missing.

It looks like Relevanssi do not index the works having the special chars.

Can you please check with Relevanssi support and check with them if they have any solution for this.

In addition to that, you could also setup a default relevanssi search (without using Views) and see if it works and check with Relevanssi support why C# word is not get indexed. (having said that words having special chars not get indexed)

I checked with your database table (wp_relevanssi) and found that the keyword C# not get indexed and not found within the table wp_relevanssi.

It does not seem to be issue with Toolset but you should contact Relevanssi support.

#1878217

Wim

Hi Minesh,

Well actually that is not really the problem I think because when you search in post title and post body alone with relevanssi activated too then you do get results, so that should not work either right if the problem was due to Relevanssi not indexing the special characters.

Once you activate relevanssie is bypasses the default search so it works or it does not.

Thing is once you active to search in the custom fiels of toolset then it does not work, so there might be a conflict there?

#1878661

Wim

Hi, I was just wondering if this issue is also still on your next level support like you said?

#1878891

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Let me try to explain again:

The option to search within "Posts content and title" and "Just post title" offered by Toolset that is why its working.

The option to search within " title, post body and custom fields" will be only offered if you installed and activated the Relevanssi plugin.

You can also try another way to test this, you should try to use the default WordPress search and try to search for C# keyword, do you see any results? As I do not see any results.

You can also create another post with title "my test post for C# language" and then reindex it from Relevanssi settings and check the table wp_relevanssi, and if you try to search for term column and search within that column for all words of the title, you will notice that all words like my, test, post, for, language will be registered but not the C#.

That is why I suggest you to contact Relevanssi support and check with them it its possible to register keyword with special chars.

#1878955

Wim

Hi,

Now I understand and thanks for the explanation! I have asked Relevanssi now for support ( https://wordpress.org/support/topic/hashtag-character-not-indexed/ ). Will update here once I have a reply.

#1878961

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Great - please let me know if they share anything to point out that it's a Toolset issue then we are happy to fix it.

#1879265

Wim

Hi,

It was indeed a relevanssi issue for which a solution was provided by the developer.
for the solution see: https://wordpress.org/support/topic/hashtag-character-not-indexed/#post-13802546

Thanks for your patience and the thinking along!

Kind regards

Wim

#1879267

Wim

My issue is resolved now. Thank you!