This thread is resolved. Here is a description of the problem and solution.
Problem:
The issue here is that the user wanted to separate their view filters and results.
They wanted the results to appear on a different page.
Solution:
This can be done by following the instructions in the post below.
https://toolset.com/forums/topic/putting-filters-on-a-different-page/#post-1236320
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 |
|---|---|---|---|---|---|---|
| - | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | - |
| - | 13:00 – 18:00 | 13:00 – 18:00 | 13:00 – 18:00 | 14:00 – 18:00 | 13:00 – 18:00 | - |
Supporter timezone: America/Jamaica (GMT-05:00)
This topic contains 10 replies, has 2 voices.
Last updated by 5 years, 9 months ago.
Assisted by: Shane.
Here are the images of what I'm trying to accomplish. One is the home page where the filters will sit. The other is the page that the filters will take you with the results.
Hi Jessica,
Thank you for getting in touch.
So you essentially want the search bar on one page and when the search is made it leads to the results page.
Take a look at this link here.
https://toolset.com/documentation/user-guides/front-page-filters/#4-1-adding-the-custom-search-form-to-a-page-or-widget
When you are adding the search to a page you will be presented with some options.
"Only Search Form"
This should allow you to add the search form only to the page, then follow the instructions to add the results to a separate page. See Screenshot
It will allow you to create and add the results only to a separate page.
Please let me know if this helps.
Thanks,
Shane
Hi Jessica,
You're referring to the Text Search bar correct?
There is a text search button on the filters section , See Screenshot
You should be able to add it with this.
Thanks,
Shane
