Psst... We're working on the next generation of Chowhound! View >
HOME > Chowhound > Site Talk >
Aug 6, 2012 08:59 AM

Search not working properly

I was just searching for information on a new Boston restaurant, The Bearded Pig.

So I searched for it:

... and, nothing except a mention of its having opened recently.

Later, I stumbled across a thread about the restaurant, started five days ago:

I'm guessing that the problem is that the search isn't indexing the title, only the body text. Possible to fix that?

  1. Click to Upload a photo (10 MB limit)
  1. Thanks for pointing this out - we're aware of the problem and are working to fix it asap.

    No content (whether thread title or body text) that was created after July 29th, 2012 is currently showing up in search results. We'll hopefully have this fixed very soon.

    1. Search engine (using box on SF Bay Area board) does not find this post when I search for "chaat house" or using dahi as the search term.

      5 Replies
      1. re: Melanie Wong

        That appears to be due to the date filter- searching "dahi" for all years turned out that thread a little more than half way down the page:

        1. re: Engineering

          The one-year default date filter shouldn't make a difference as that thread has been updated within the date range.

          However, I've now tried it again with full site and the thread pops up now both in default 12 months and all years. Whatever was suppressing it before has disappeared.

          1. re: Melanie Wong

            That being the case, what I saw was probably due to the same reindexing lag time we're seeing with the site footer; the newest post in that thread had not been indexed yet when you originally searched for it. We are actively pursuing a solution to these delays and hope to have them resolved in the near future.

            1. re: Engineering

              IIRC, the newest post was in May 2012. That long of a delay?

              1. re: Melanie Wong

                Ah, sorry, I had assumed that the thread had been recently updated. That's probably not related to the delay; please let us know if this or a similar oddity resurfaces.