Cannot replace a search field in a view

This support ticket is created 3 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.

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.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	-
-	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-

Supporter timezone: Asia/Karachi (GMT+05:00)

Tagged: Custom search, Toolset Blocks, Views, Views plugin

This topic contains 2 replies, has 2 voices.

Last updated by matthiasV-2 3 years, 10 months ago.

Assisted by: Waqar.

Author

Posts

January 5, 2021 at 6:36 pm #1895269

matthiasV-2

I want to replace a search field in a view, but this is impossible.
Link to a page where the issue can be seen: hidden link
See screenshot attached.

January 5, 2021 at 10:42 pm #1895571

Waqar

Hi,

To replace the existing search filtering fields, you'll remove the ones that you don't need and then add the new ones in their place.

1. You can select any "Custom Search Filter" block by directly clicking it or by using the block navigation from the top.
( screenshot: hidden link )

2. Using the contextual menu from the block, you can remove it
( screenshot: hidden link )

3. After that, you can use the "Add Search Field" button, to add the new "Custom Search Filter" block for the field that you need and then drag it to the grid column.
( screenshot: hidden link )

This guide on adding search filters should make these steps more clear:
https://toolset.com/lesson-placement/lesson-placements-1622935-1621213/

regards,
Waqar

January 6, 2021 at 9:18 am #1895971

matthiasV-2

My issue is resolved now. Thank you!