Views plugin lets you build your own custom search for any content type. These searches can be based on post content, taxonomies and custom fields.
When you ask for help or report issues, make sure to tell us settings for your custom search.
Viewing 15 topics - 2,161 through 2,175 (of 2,222 total)
Problem: I would like to apply custom styles to the distance filter elements.
Solution: Use custom CSS to apply any custom styles you want to the distance filter elements. Add the CSS to the Search and Pagination editor's JS panel.
The issue here is that the user wanted to disable past dates on their datepicker.
Solution:
Unfortunately this is not possible with just toolset. What you can do is to check out this link below as it should be able to help you get this working. https://codepen.io/ben108/pen/PqvaBR
Problem: I would like to place a custom search View in a WordPress Archive for Product Categories. I would like to show the correct, filtered results on the archive. I would also like to show filters that allow Users to easily filter the list by other Product Categories.
Solution: Something exactly like this is not possible in the current system. Your options are:
1. You can use a WordPress Archive to display the correct, filtered results at URLs like /websites/header. This will work without a View, but then your Users cannot use the search filters to show the other Website options like Footer, Navigation, etc. because a WordPress Archive for the term "header" cannot be filtered to show results for a different term. It is not possible in the current WordPress Archive system. One alternative here is to use a list of links to represent the other terms. They will not work together with other filters, but will allow your Users to easily navigate between term archives.
2. You can use a View to display the correct, filtered results inside a WordPress Archive. This will allow your Users to apply the other Website filter options like Footer, Navigation, etc. but it presents a different problem. Now you cannot filter the initial results automatically because the View only responds to URL parameters. It does not respond to the taxonomy term directory-based URL. One way to get around this problem is to update all the links in your menu to point to the archive pages with the proper URL parameters, like /websites/header?wpv-websites=header or /websites/footer?wpv-websites=footer. Another way to get around this problem may be custom code, but it falls outside the scope of support we provide here.