Every time I go to use it, it tells me I have to wait two minutes in between searches. Guess what! I’m talking about my first search!
Then, it has the nerve to add time to the ticker when I click search again! LOL I was just trying to see how much time I had left to wait… You don’t have to penalize me for it!
It’s not picking on you. It picks on everyone. There’s a two minute wait between searches for everyone. This was put in place several years ago to reduce the server load. It shouldn’t add time though. Usually you can click on it again to see how much time you have remaining. I’m not sure what happened there.
The OP seems to be saying he is being told to wait after he hits search the first time, not between searches. Maybe he had clicked New Posts before searching. Not everyone realizes that counts as a search, too.
I don’t think I’ve ever had the Search feature here result in a hit. And I’ve tested it by putting in queries that I KNOW should result in multiple hits.
No kidding. I found that the grease monkey script someone wrote, which puts a google search box for the SDMB into your toolbar, the best thing since sliced bread.
Now I can use this to find my ATMB OP where I was wondering if anyone remembered this great macro and script somebody had posted in ATMB and I lost it.
:: On re-read: For ECG: :dubious: :: Where were you when I needed you? ::
today and yesterday the search results show a blank empty screen. the usual refresh the browser brings up a ‘wait 120 seconds between searches’ screen.
It sounds like there is something wrong with the recognition of your system. I don’t know if that’s tied to other problems mentioned with tracking threads that have been read or unread, etc. It might be cookies, but I really don’t know how this board works.
I’m still not sure what causes this, but I figured out why it’s behaving the way it is.
The first time I click search, nothing happens. So I think I didn’t actually click it. I click it again, and blammo, I have to wait two minutes. It could be my laptop, it is a Toshiba after all… Or it might be on the SDMB’s end, IDK.