Search busted?

Trying a search for “Quake Live” got me this:

Search busted for anyone else?

Still busted for me; same error.

Sigh.

Anyone else?

I tried it, and the problem seems to be “live”. “Quake” by itself works fine.

Yep, “quake” works. But why would “live” throw an error, and why that one? Weird bug.

Tested it with “they live” – same error. This seems like a problem – the term “live” is fairly common and useful. Any chance of it actually getting fixed?

I am getting this error searching on the words “back shot”

Seems to work for me.

There are sometimes random words combos that just won’t work for me, no matter how often I try. It’s odd.

I got that error earlier today.

What does? “quake live”, “they live” or “back shot”? Or all of them?

Is there a difference between searches for mods and regular members? If, for example, you don’t have a 300-second wait time between searches, then your searches may not be the same as mine from a system priority standpoint. Although Colibri was able to replicate the problem earlier…

Since the bug is reproducible, search is a known problem for the SDMB (300 seconds between searches is a long time), and the error message references a specific line of code, this seems like the sort of thing that would be best dealt with by Jerry or whoever he escalates to at vBulletin tech support, if we have that.

This is about the twentieth thread I’ve seen on this subject.

However, I do not imply criticism. This is because if I search for ‘search problem’ I get a similar error to the one quoted above. As a matter of interest, a search for ‘problem child’ produces a like error, as does ‘weird problem’. It would therefore appear that search terms that include ‘problem’ cause a problem, which I would say is a definite problem.

I strongly suggest somebody posts a sticky to inform the masses that the search function is at least partially fucked.

Many thanks.

Yep, I got the error too:

The annoying part is that I’d like to try again with different terms, but I have to wait five minutes before doing so.

Zev Steinhardt

I’d say that was part of the annoying part – not only do you need to wait 5 minutes, you don’t know that it was one of your terms that did it (unless you are one of the special few that have read this or one of the other threads), and even if you do know it was one of them, you don’t know which one it was.

I’m not much of one for complaining, but this does strike me as the sort of thing that should get fixed on a board that expects return visits.

I tried to do a search for “tilt table test” (first without, and then with quotes) and I did not get an error, but none of the results were correct.

The first several pages of results were all posts from the “What if LOTR were written by someone else” thread. I only checked a couple, but none of them were relevant, and several did not have any of my search terms in them at all.

What’s the deal?

I just did a search for “change ipod battery” and got the same error message. “ipod battery” worked earlier but was less relevant to what I want to see.

Is it perhaps the frequency of a search term that leads to these errors – i.e. that the word ‘problem’ is mentioned in too many posts to fit in some allocated memory space?

That’s what I was guessing, as well. The word “change” probably came up too many times so it stalled out my search. I thought putting my phrase in quotes would fix that, though, and it didn’t.

I’m not sure the quotes actually do anything, though. I seem to remember once doing a search with and without quotes, and the same results came up.

Doesn’t work for me neither. Either gives me that jargle, or just…stops and gives me nothing, but Firefox tells me “done”. Refreshing gives me the ‘300 seconds’ again.

I am getting the same error any time I try to search for anything at all…

I also can’t search to see if this issue has been addressed before. :mad: