Exposed Fulltext search input not showing

Created on 1 June 2023, over 1 year ago
Updated 17 June 2023, over 1 year ago

Problem/Motivation

Went through the basic set up with search api and views integration. I am using the basic db server since I needed a simple search of content, users, and some taxonomy lists. Server and index is set up and enabled. I added the view of the index and gave it a path of /search. Clicked yes for "Exposed form in block" and added the block to the block layout. I am only showing the block on /search page because I do not need it on every page. When I go to this page, I cannot get the search input field to show up. I can see the title and my no results text. But no exposed filter. I included screenshots to show my set up. Open to any questions and help on solving this issue. This is a new set up so I have never had this working before. And I have tried this on 8.x-1.28 and 8.x-1.29 so I do not think it is version specific, I simply cannot get the input to show. Other note: I am using bootstrap barrio theme as a base with a custom sub-theme for overrides. I am not seeing any custom template file that would be overriding this either. Thank you!

πŸ’¬ Support request
Status

Fixed

Version

1.29

Component

Views integration

Created by

πŸ‡ΊπŸ‡ΈUnited States kd_ace Oklahoma

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @kd_ace
  • πŸ‡ΊπŸ‡ΈUnited States kd_ace Oklahoma
  • Status changed to Postponed: needs info over 1 year ago
  • πŸ‡¦πŸ‡ΉAustria drunken monkey Vienna, Austria

    Thanks for reporting this issue!
    However, this works for me as expected.
    Could the block settings be the problem? Please try enabling it for all pages and see if that helps.
    Also, could you maybe attach an export of your view (as minimalistic as possible for reproducing the error)?

    PS: It seems you (like many others – it's really easy to misinterpret) are confused by the "Issue tags" field. As the guidelines β†’ state, they aren't meant for free text tags related to the issue, but only for specific categorization purposes, usually by module maintainers.
    So, if you aren't sure your current usage is correct, please just leave the field empty.

  • πŸ‡ΊπŸ‡ΈUnited States kd_ace Oklahoma

    Thanks for the info on tags. My bad!
    After digging in some more and changing some settings with the block, I was able to get the search input to display. I am thinking it was something odd with the theme or possible something as simple as cache. I am sorry for the mix up and thank you for the help!

  • Status changed to Fixed over 1 year ago
  • πŸ‡¦πŸ‡ΉAustria drunken monkey Vienna, Austria

    OK, good to hear, thanks for reporting back.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024