Skip Navigation
Buy Now
Home » Errata » Unexpected options for the custom field filter in the View Custom Search Settings

Unexpected options for the custom field filter in the View Custom Search Settings

Resolved

Reported for: Toolset Views 2.7.2

Resolved in: 2.8

Topic Tags: Custom search, Views, Views plugin

Symptoms

There is an issue with the options available for the custom field filter in the View Custom Search Settings.

This issue happens in the following scenario:

  • You have a custom field, for example “Field A”, assigned to a custom post type.
  • You have a View with a Query Filter. For example, it filters the posts by taxonomy and you selected a specific category, for example “Category A” to filter by.
  • You add another Query Filter to filter by “Field A”, which filters the posts between two values of “Field A”. These values are passed through URL parameters.
  • In the “Search and Pagination” section, you added two fields as custom search filters to filter the posts depending on the “Field A’s” value. These fields pass their values as URL parameters so that query filters added in the previous step can use them.

These custom search filters should hold only values of the custom field which are are added to the “Field A”, in posts that have “Category A” assigned to them.

The problem is that the search filters will hold values from posts that do not have “Category A” assigned to it.

Workaround

This has been fixed in Views 2.8

7 thought on Unexpected options for the custom field filter in the View Custom Search Settings

  • I reported this and it’s slightly incorrect. One search filter will work correctly but the second one will not. This indicates that it’s some type of scripting problem where the hiding of the unwanted values will apply to one selector, but not to a second selector showing the same field.

    • This image shows the problem. The From field includes the unwanted amount of 450 while the To field correctly hides it.

  • Hi Farrel, I think that you are talking about the same problem.
    I’ve asked the development team to review the query that generates fields filters.this should fix the problem mentioned in the errata description and the one you try to explain in the comments.

  • Hi.

    Can you please tell me why this problem cannot be fixed. I assume it can’t be fixed because its been over a month and it’s still showing as Open.

  • Hi Farrel,

    I just want to let you know that we recently launched a new release with many nice features which took a lot of resources.
    But I know that this shouldn’t affect our products quality. So, I’m going to forward your complaint again to the development team to bring their attention.

Comments are closed