Skip Navigation

[Resolved] Search results no longer include content from custom fields

This support ticket is created 3 years, 6 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.

This topic contains 2 replies, has 2 voices.

Last updated by shelleyK 3 years, 6 months ago.

Author
Posts
#2052375

I am trying to:

Search the custom type I created several months ago by various custom fields. Everything was working fine until recently, and nothing has been done to change the configuration of the site except updates to WordPress and plugins.

Link to a page where the issue can be seen:

hidden link

Here's a sample search results screen:

hidden link

I expected to see:

Dozens of results, since these search terms appear in the Author custom field for dozens of these CPT entries.

Instead, I got:

One single result, which includes the search terms in the title. All the custom fields are being ignored.

More background:

This whole system is set up using Relevanssi, and I've rebuilt the index, enabled this custom type, and enabled all these custom fields exactly per the Toolset documentation.

#2052741

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi there

For Views created with the Block editor this broke in version 1.5 (it doesn't affect Views created with the legacy editor).

We already have a fix in place (version 1.5.2) and are just completing final testing. We don't release at the end of the week, so that update is expected to be available Monday.

Please use the Check for Updates button on the custom Toolset installer page then, or check your account downloads page here.

Sorry for the inconvenience in the meantime.

#2059053

Thank you. I waited till the update was released, applied it, and found that indeed it resolves the issue.

I did need to manually update the plugin for some reason.

Thank you.