# Search function completely non-functional

**URL:** <https://boards.straightdope.com/t/search-function-completely-non-functional/738376>\
**Category:** About This Message Board\
**Created:** [November 23, 2015, 6:38pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376 "2015-11-23T18:38:44Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![Northern\_Piper](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/northern_piper/32/5304_2.png) [@Northern\_Piper](https://boards.straightdope.com/u/Northern_Piper)\
**Post date:** [November 23, 2015, 6:38pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/1 "2015-11-23T18:38:44Z")

</div>

When I try to do a search, either advanced, or just the popup from the Search button, I get a white screen.

---

<div class="post-metadata">

**Author:** ![engineer\_comp\_geek](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/engineer_comp_geek/32/504_2.png) [@engineer\_comp\_geek](https://boards.straightdope.com/u/engineer_comp_geek)\
**Post date:** [November 23, 2015, 7:03pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/2 "2015-11-23T19:03:43Z")

</div>

You’re not the first person to report this problem.

I don’t know what causes it. For some people, the search function works pretty well. Some people have all kinds of problems though, including the white screen that you are reporting.

I’ve never had the problem myself.

---

<div class="post-metadata">

**Author:** ![minor7flat5](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/minor7flat5/32/258_2.png) [@minor7flat5](https://boards.straightdope.com/u/minor7flat5)\
**Post date:** [November 23, 2015, 7:25pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/3 "2015-11-23T19:25:52Z")

</div>

I gave up on search ages ago…

…Google works much better, with “site:straightdope.com” after the search terms.

---

<div class="post-metadata">

**Author:** ![billfish678](https://avatars.discourse-cdn.com/v4/letter/b/7bcc69/32.png) [@billfish678](https://boards.straightdope.com/u/billfish678)\
**Post date:** [November 23, 2015, 9:11pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/4 "2015-11-23T21:11:04Z")

</div>

So things have improved?

---

<div class="post-metadata">

**Author:** ![Idle\_Thoughts](https://avatars.discourse-cdn.com/v4/letter/i/838e76/32.png) [@Idle\_Thoughts](https://boards.straightdope.com/u/Idle_Thoughts)\
**Post date:** [November 23, 2015, 10:07pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/5 "2015-11-23T22:07:51Z")

</div>

> [@engineer\_comp\_geek](#):
>
> I’ve never had the problem myself.

Me either…sometimes I wonder if it has to do with being a mod.

---

<div class="post-metadata">

**Author:** ![engineer\_comp\_geek](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/engineer_comp_geek/32/504_2.png) [@engineer\_comp\_geek](https://boards.straightdope.com/u/engineer_comp_geek)\
**Post date:** [November 23, 2015, 10:23pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/6 "2015-11-23T22:23:31Z")

</div>

I never had a problem before I was a mod either.

I have always run an adblocker and a script blocker. Not sure if that makes any difference.

---

<div class="post-metadata">

**Author:** ![BlankSlate](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/blankslate/32/80_2.png) [@BlankSlate](https://boards.straightdope.com/u/BlankSlate)\
**Post date:** [November 23, 2015, 10:29pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/7 "2015-11-23T22:29:05Z")

</div>

It would be useful to collect device/OS info from those having the issue.

---

<div class="post-metadata">

**Author:** ![TroutMan](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/troutman/32/6721_2.png) [@TroutMan](https://boards.straightdope.com/u/TroutMan)\
**Post date:** [November 23, 2015, 10:51pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/8 "2015-11-23T22:51:32Z")

</div>

I’ve noticed I almost always get a 500 error when I search for a very common word, but it seems to work fine when it’s something not as common. I tested searching for “white” three times today and it crashed every time. Other searches worked.

---

<div class="post-metadata">

**Author:** ![Section\_Maker\_Jupe](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/section_maker_jupe/32/1424_2.png) [@Section\_Maker\_Jupe](https://boards.straightdope.com/u/Section_Maker_Jupe)\
**Post date:** [November 24, 2015, 2:52am UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/9 "2015-11-24T02:52:18Z")

</div>

I use Chrome. I added Adbock and Ublock…no more cheerleader pics!!!

Search is not working at all however. Didnt really put 2 and 2 together:smack:

I will disable the Adblockers and report back later.😃

---

<div class="post-metadata">

**Author:** ![Section\_Maker\_Jupe](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/section_maker_jupe/32/1424_2.png) [@Section\_Maker\_Jupe](https://boards.straightdope.com/u/Section_Maker_Jupe)\
**Post date:** [November 24, 2015, 3:02am UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/10 "2015-11-24T03:02:33Z")

</div>

I disabled both blockers, but no Search still. I use an HP Chromebook, on local WiFi and have minimal IT skills.

---

<div class="post-metadata">

**Author:** ![Northern\_Piper](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/northern_piper/32/5304_2.png) [@Northern\_Piper](https://boards.straightdope.com/u/Northern_Piper)\
**Post date:** [November 24, 2015, 3:46am UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/11 "2015-11-24T03:46:20Z")

</div>

I’m on safari. No ad blockers, because I’ve got a membership.

---

<div class="post-metadata">

**Author:** ![Merneith](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@Merneith](https://boards.straightdope.com/u/Merneith)\
**Post date:** [November 24, 2015, 4:41pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/12 "2015-11-24T16:41:35Z")

</div>

> [@Section\_Maker\_Jupe](#):
>
> I disabled both blockers, but no Search still. I use an HP Chromebook, on local WiFi and have minimal IT skills.

Don’t use two adblockers at once. Pick one or the other. I use uBlock Origin, but that’s a personal preference. I also use NoScript.  
On topic - no idea, I never have that problem, personally, but I second the suggestion of doing a google search and including the phrase site:straightdope.com in the search box. It’s faster and it doesn’t make you wait 60 seconds.

---

<div class="post-metadata">

**Author:** ![TroutMan](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/troutman/32/6721_2.png) [@TroutMan](https://boards.straightdope.com/u/TroutMan)\
**Post date:** [November 24, 2015, 5:39pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/13 "2015-11-24T17:39:57Z")

</div>

Assuming the rest of you have the same problem as me, this is something on the server, and your browser version and ad blocker (or lack thereof) have nothing to do with it. If you get a 500 error when you attempt a search, this means something failed on the server. For whatever reason, certain words crash the search for me every time.

As for the suggestions to use Google search, it is a good suggestion and I do this 90% of the time. But there are some things the site search does better, like searching for posts by a specific user or returning links to the specific posts instead of links to the entire thread.

---

<div class="post-metadata">

**Author:** ![septimus](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/septimus/32/410_2.png) [@septimus](https://boards.straightdope.com/u/septimus)\
**Post date:** [November 24, 2015, 7:47pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/14 "2015-11-24T19:47:00Z")

</div>

> [@TroutMan](#):
>
> … there are some things the site search does better, like searching for posts by a specific user or returning links to the specific posts instead of links to the entire thread.

Yes.

BTW, I suppose it is logical not to allow searches for common words, but why are UNCOMMON short words also disallowed? That is … inconvenient.

---

<div class="post-metadata">

**Author:** ![TroutMan](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/troutman/32/6721_2.png) [@TroutMan](https://boards.straightdope.com/u/TroutMan)\
**Post date:** [November 24, 2015, 8:04pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/15 "2015-11-24T20:04:23Z")

</div>

After a little more testing, I don’t think it’s common vs rare words that are a problem. Instead, it seems like there are specific words that cause a crash (e.g., “black” and “white”). If that’s true, then it suggests there is a corrupt search index that needs to be rebuilt or repaired.

> [@septimus](#):
>
> I suppose it is logical not to allow searches for common words, but why are UNCOMMON short words also disallowed? That is … inconvenient.

That’s common in any search engine to reduce load and cut down on searches that return too many results. Search engines will have lists of words that aren’t searchable (like “the”) or won’t search on words shorter than a certain length. Most engines have both restrictions.

---

<div class="post-metadata">

**Author:** ![Section\_Maker\_Jupe](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/section_maker_jupe/32/1424_2.png) [@Section\_Maker\_Jupe](https://boards.straightdope.com/u/Section_Maker_Jupe)\
**Post date:** [November 24, 2015, 8:57pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/16 "2015-11-24T20:57:10Z")

</div>

hmm thanx everyone for user tips.  
I do get the “500” server errror. I’ve been looking for a thread on Public Morals (TNT show) in Cafe Society…Google sends me all over the Dope…

perhaps there is NO thread:eek: although that would have to be a first…😃

maybe thats it?

I typed “Russia” and of course got 4 gazillion threads…

---

<div class="post-metadata">

**Author:** ![crypto](https://avatars.discourse-cdn.com/v4/letter/c/b3f665/32.png) [@crypto](https://boards.straightdope.com/u/crypto)\
**Post date:** [November 24, 2015, 9:14pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/17 "2015-11-24T21:14:53Z")

</div>

> [@TroutMan](#):
>
> **I tested searching for “white”** three times today and it crashed every time. Other searches worked.

The search function is racist!  
Foghorn Leghorn

I said that’s a JOKE, son!

/Foghorn Leghorn

---

<div class="post-metadata">

**Author:** ![TroutMan](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/troutman/32/6721_2.png) [@TroutMan](https://boards.straightdope.com/u/TroutMan)\
**Post date:** [November 24, 2015, 9:24pm UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/18 "2015-11-24T21:24:46Z")

</div>

> [@Stink Fish Pot](#):
>
> The search function is racist!

Well, “black” crashes it too, so it’s equal opportunity racism.

“Blue” works, though. Maybe it’s anti-human, pro-alien.

---

<div class="post-metadata">

**Author:** ![Northern\_Piper](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/northern_piper/32/5304_2.png) [@Northern\_Piper](https://boards.straightdope.com/u/Northern_Piper)\
**Post date:** [November 25, 2015, 1:00am UTC](https://boards.straightdope.com/t/search-function-completely-non-functional/738376/19 "2015-11-25T01:00:13Z")

</div>

> [@TroutMan](#):
>
> Assuming the rest of you have the same problem as me, this is something on the server, and your browser version and ad blocker (or lack thereof) have nothing to do with it. If you get a 500 error when you attempt a search, this means something failed on the server.

I’m not getting a 500 message. I’m getting a white, blank screen. Sort of like the ol’Blue Screen o’Death, but white.
