Announcement

Collapse
No announcement yet.

Updating the Search

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • lesliekirk
    replied
    Originally posted by kayakbabe View Post
    did you figure out the placeholder text? I'm using the levels theme and it needs that place holder to make things look correct.
    I have not (sorry took me a minute to remember which site this was for).

    Leave a comment:


  • kayakbabe
    replied
    I've already done that. not heard back though. I submitted a ticket in the support system.

    Leave a comment:


  • Matt Zimmermann
    replied
    kayakbabe - I would recommend contacting either Professional Services or Support to have them look at the page and global coding in the administration portal.

    Leave a comment:


  • kayakbabe
    replied
    As you suggested, I changed the templates to use the <mvt:item name="searchfield" />

    so now the paging and facets work together.

    But doing that change broke the search page. The page doesn't recognize that a search term has been passed to it. So the result is a small form to enter a term into.

    As suggested, I went through the 9.7 template changes. now.. paging and facets also work on search results (once I get to them). But IF I use the global header search form, I still get the result is a small form to enter a term into and the SRCH page isn't recognizing a term has been passed to it.

    I decided to check out the global vars the SRCH page has.

    I see on the first visit to SRCH via the global header, the only var available is g.searchfield.

    If I use the form on the SRCH page, then the only var available is g.search.

    I double checked the 9.7 template changes. And NOOOO item search field is there. also NOOO g.searchfield is there.

    My conclusion is the the 9.7 template changes are not up to date for 9.7 regarding the SRCH and SRCHR and the <mvt:item name="searchfield" />.

    Leave a comment:


  • Matt Zimmermann
    replied
    kayakbabe - Are you using a customized search field or the default <mvt:item name="searchfield" /> ? If you are using the default one, I believe using JavaScript would be the only way to add a placeholder.

    Leave a comment:


  • kayakbabe
    replied
    did you figure out the placeholder text? I'm using the levels theme and it needs that place holder to make things look correct.

    Leave a comment:


  • lesliekirk
    replied
    Also, the previous search box had placeholder text in it. How do I add placeholder text?

    Leave a comment:


  • lesliekirk
    replied
    So now that I have it working, I'm finding styles that don't work very well with the layout in place. The fixed width of the search field is not compatible with the mobile version of the site. If I try to change the width it impacts the display width. If anybody has played around with tweaking this, I'd love some suggestions. I'll keep at it and post anything I might find.

    Leave a comment:


  • lesliekirk
    replied
    Looks like it was a caching issue. Once I got the cache cleared out of multiple browsers, it is now displaying much closer to what I am looking for.

    Leave a comment:


  • Matt Zimmermann
    replied
    Hi Leslie,

    You might want to verify that the element being output for the search preview is having the correct CSS applied and that they surrounding container is positioned relatively.

    Leave a comment:


  • lesliekirk
    started a topic Updating the Search

    Updating the Search

    I'm working my way through the template changes to update the search (with plans to include the facets). When I make the template changes for User Interface > Settings > Global Header & Footer > Global Header changing the input from

    Code:
     <input type="text" name="Search" id="searchfield" value="&mvte:global:Search;" class="textfield" />
    to

    Code:
     <mvt:item name="searchfield" />
    and then go test the search, it "works" but the results aren't in a modal or a drop down div, instead they seem to push the header div down resulting in a huge header. I did add the CSS and made sure the javascript matched the changes.

    For the time being I've rolled back the input to token change to see if anyone else has run up against this before I start digging.

Working...
X

This website uses cookies to identify visitors, track visitors to our website, store login session information and to remember your user preferences. By continuing to use this site you agree to our use of cookies. Learn More.

This website uses cookies. By continuing to use this site you agree to our use of cookies. Learn More.

Accept