I am trying to: Change from having the wpv-filter-search-box filter only searching titles to also searching contents. I've changed the option on the view and it shows "Filter post content and title based on the frontend input search filter." More information: my service areas are titled by zipcodes. People put in their zipcode and it tells them if it is serviceable and links to service area page. We now have service areas for cities that have multiple zipcodes so I'm trying to put the extra zipcodes in the content of the post so it shows as serviceable.
Link to a page where the issue can be seen: hidden link
I expected to see: When searching for zipcode 46699 it should show that the zipcode is serviceable. You can see it is in the contents of the post by doing a normal search for it: hidden link
With the "Zipcode" text box I entered the zipcode value as 46699 and click on the "Search" button and as soon as I click it it redirect me on the following URL:
- hidden link
I've just create a brand new custom search view and added the text serch and set it to search in post content and title.
=> hidden link
I've added above view to the following page:
- hidden link
When I search for the zipcode "46699" is does show the correct result. It seems with your view you have added some custom JS code that leads to issue. Also I found your view set to displa all result but I changed the views purpose to "Display the results using a custom search".
Can you check above test view and tell me what exactly you want with that test view.
Thank you. I was able to make it work by editing and utilizing the new view that you created. I then added that view to my homepage instead of the old view.
I'm wondering if there is a bug, where editing a view that already had the filter set to searching only the title only, to changing it to search the title and contents doesn't actually edit the filter properly.
UPDATE: Well I had two other views with similar settings... when I updated those to also search the contents, it updated the filter correctly, so it isn't a bug across the board. Must have just been something with that one view.