"This forum requires that you wait 1 seconds between searches. Please try again in.."

seamus

This is going to be a very vague and low priority report.

I have a shortcut on my toolbar to the "New Posts" page; http://www.boards.ie/vbulletin/search.php?do=getnew

Seemingly at random, when I click on the shortcut, I get the below message;

"This forum requires that you wait 1 seconds between searches. Please try again in 1 seconds."

It's usually when I haven't done a search in a while that it appears, rather than when I click it a lot. That's about all I can give you, I have no other pattern for it. Happens both in work and at home. Both running Chrome 27 and Windows 7 pro.

Just click search again and it works fine. So it's not a major or even important issue.

As best I can recall, it has happened to me with firefox, but not with the same frequency...

Boards.ie: Rónán

seamus wrote: »

This is going to be a very vague and low priority report.

I have a shortcut on my toolbar to the "New Posts" page; http://www.boards.ie/vbulletin/search.php?do=getnew

Seemingly at random, when I click on the shortcut, I get the below message;

"This forum requires that you wait 1 seconds between searches. Please try again in 1 seconds."

It's usually when I haven't done a search in a while that it appears, rather than when I click it a lot. That's about all I can give you, I have no other pattern for it. Happens both in work and at home. Both running Chrome 27 and Windows 7 pro.

Just click search again and it works fine. So it's not a major or even important issue.

As best I can recall, it has happened to me with firefox, but not with the same frequency...

Hey seamus, this is down to the crappy way vBulletin handles search floodchecking. It should be restricting queries based on the frequency of searches made by individual users but looks like its just pulling all searches made by all users at the moment, hence the perceived inconsistency on your end.

We're currently in the process of phasing vBulletin search out in favor of our Solr search implementation, so I don't think we'll be able to spend any time sorting this one out unfortunately.

Apologies, and thanks for the bug report all the same.