Skip Navigation

[Resolved] Fitlering Search Results (WordPress Archive) with Relevanssi activated

This support ticket is created 5 years, 11 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
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

This topic contains 17 replies, has 2 voices.

Last updated by Thomas AMX 5 years, 5 months ago.

Assisted by: Nigel.

Author
Posts
#1301687

Hello Nigel,

Thank you for coming back to me. I had great hopes after I saw in the changelog that "a number of issues with Relevanssi" were fixed in Views 2.9.

But unfortunately, this issue does not seem to have been fixed. I updated everything, cleared all cache, rebuilt the Relevanssi index - and still the same. Tested on 2 sites, a simplified case produces the same error.

This issue is still open in "Known Issues":

https://toolset.com/known-issues/?wpv_post_search=relevanssi&wpv_aux_current_post_id=399043&wpv_view_count=401205-TCPID399043

Apparently, there are many compatibility issues with Relevanssi (some of which have been resolved, yes, but still Relavanssi and Toolset don't seem to play nicely together). So, sometimes I wished Toolset had some native relevancy tool not relying on third-party products.

Cheers,
Tom

#1306417

Nigel
Supporter

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

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

Hi Tom

The remaining Relevanssi issues should now be resolved by today's release of Views 2.9.1, if you could please update and re-test.

Thanks for your patience.

#1306969

Indeed, Nigel. As far as I can tell, it works correctly now. In my quick test, both custom fields and taxonomies behaved correctly. Fantastic! Thank you!

Cheers,
Tom