Community forum for knowledge and support

Updated last year

Issue with double search bar in application shell

At a glance

A community member is having an issue with the application shell related to a double search bar. When they apply the search field attributes to the second search bar, it doesn't work as expected. They are wondering if there's an issue with having two search fields and two search forms connected to the same CMS collection. Another community member suggests using the Mirror Input fields as a workaround, which allows having only one search form in the DOM but displaying the field differently depending on the breakpoint. The original poster thanks the community member for the suggestion and says they will look into it. Another community member mentions that @Matt has solved this issue for them and offers to help anyone else with this problem.

Useful resources

Hey everyone, I’m having an issue with the application shell related to a double search bar. When I apply the search field attributes to the second search bar, it doesn’t work as expected. I’m wondering if there’s an issue with having two search fields and two search forms connected to the same CMS collection. If you have any insights or workarounds, please let me know. Thanks! https://www.loom.com/share/04142e59710249ef8dd7439a52ea3071?sid=6f1a3813-89ce-446b-91a1-233c28292d49

M
M
3 comments

I am not fully aware of any issues with multiple search boxes. I don't feel like I have all of the context so if you want to share a read-only I can better grasp where you are at and how you're doing things.

However, if this really is a limitation, you could try using the Mirror Input fields so that you only need one search form in the DOM, but can display that field differently depending on the breakpoint.
https://finsweet.com/attributes/mirror-input-values

Thank you for the suggestion will look into these!

@Matt has solved this one for me his support and this documentation. If any one needs support with this issue I’d be….happy to help anyone moving forward - thanks again Matt!

Add a reply
Sign up and join the conversation on Slack