Topic Tag: Custom search

Problem:
Client is using Relevanssi for custom text searches, but searching for codes such as "A:66" or "C:53" doesn't work.

Solution:
It appears to be a limitation of Relevanssi where searches are broken by the colon. Searches for "A66" or "C53" do work.

This is not related to the Relevanssi - Toolset integration.

Problem:

The issue here is that the user wanted to filter his prefiltered view with his frontend filters.

Solution:

This can be done normally by adding a query filter to your view and setting that query filter to get the value by shortcode attribute.

Then you can add your frontend filters as normal. However when calling your view on the frontend you will provide the shortcode parameter so it can be prefiltered.

Example

[wpv-view name="view-1" wpvtaxonomy1="tax1"]

Problem:
Autocomplete select filters - dependent dropdown select filters

Solution:
You should take reference of it from our free test platform discover-wp.com and setup a test site using the real estate reference site. You should check this example:
=> http://real-estate-wordpress.discover-wp.com/
- Please check “State” and “City” dropdowns with search form.

You can find proposed solution, in this case, with the following reply:
https://toolset.com/forums/topic/autocomplete-select-filters/#post-919698

Relevant Documentation:
https://toolset.com/faq/how-and-why-to-create-a-test-site-in-discover-wp/

Problem:

The issue here is that after the User uses the views AJAX filters his posts don't show in the correct language

Solution:

This is possible due to the "Language filtering for AJAX operations" not being enabled in WPML.

Could you go to Toolset-> Language and scroll down to the Language filtering for AJAX operations settings.