Flood Control on searching member posts

[pushbrk 12,883]

Recently I get a flood control message whenever I attempt to search for posts by a member. I'm using the pull-down menu below the username. I'm not flooding. I'm just doing one search. What's up?

[Usui Takumi 1,562]

I get that too occasionally. Normally I have to wait about 30 seconds. Something to check in the beta I guess.

[Usui Takumi 1,562]

I get that too occasionally. Normally I have to wait about 30 seconds. Something to check in the beta I guess.

So basically if I try to search posts on a member here, then retry within a few seconds the flood error shows up. In the beta, it works smoothly.

[Kathryn41 3,205]

Pushbrk, are you getting the flood control issue the first time you try to view member's posts or is it to view posts of another member right afterwards? There is a 30 second 'wait' before you can check another member's posts after you have checked one. If you are getting the message when you are clicking on the command for the first time you try it, then it isn't working right.

[pushbrk 12,883]

So basically if I try to search posts on a member here, then retry within a few seconds the flood error shows up. In the beta, it works smoothly.

It happens to me on the first try. Perhaps it's Chrome. I just tried in IE with no issue.

Pushbrk, are you getting the flood control issue the first time you try to view member's posts or is it to view posts of another member right afterwards? There is a 30 second 'wait' before you can check another member's posts after you have checked one. If you are getting the message when you are clicking on the command for the first time you try it, then it isn't working right.

It's the first time but I now think it's an issue with Chrome. No problem when I login through IE.

[Laura & Kyle 16]

It happens to me on the first try. Perhaps it's Chrome. I just tried in IE with no issue.

It's the first time but I now think it's an issue with Chrome. No problem when I login through IE.

I get the issue too on Chrome.

[rsn 135]

It's a known issue with Chrome on, I believe, all IP.Board sites.

[K and L 27]

It's an issue with chrome on 2.x - they fixed it in 3.

[Darnell 8,478]

come on push, stop reading my posts, d#mmit !!

(I Use Opera, my browser ate your browser)

[pushbrk 12,883]

It's an issue with chrome on 2.x - they fixed it in 3.

I'm using 4.0.249.89 (38071)

[rsn 135]

It's an issue with chrome on 2.x - they fixed it in 3.

Not sure where you got this info from - it has never been fixed to my knowledge.

[rsn 135]

I'm using 4.0.249.89 (38071)

In all honesty, Chrome isn't currently better than Firefox, not by a long shot. It has too many annoying issues. Even Google Docs runs significantly better on Firefox, which is kind of surprising. They have some work to do before it will become more appealing than Firefox.

[K and L 27]

I'm using 4.0.249.89 (38071)

I was referring to the IPB release, not the Chrome release. VJ uses IPB 2.x, not IPB 3. Most IPB 2.x bugs were fixed in 3 and they opted to NOT release fixes for the 2.x series unless they were security-related.

As I said, it was something fixed in the IPB 3.x release, and since 3 is the current standard, it is NOT something that effects "all Invision forums".

Not sure where you got this info from - it has never been fixed to my knowledge.

I run a large Invision Power Board forum that's even more customized than VJ is. The search flooding problem with Chrome exists in the IPB 2.x codebase (which VJ uses) and does not exist in the IPB 3.0 code base (which Ewok is going to be migrating to).

IPB changed how they link to "find posts" in 3, and IME (as a Chrome/IPB3 user) this change eliminated the flood control problem with Chrome.

Edited March 8, 2010 by K and L

[rsn 135]

I was referring to the IPB release, not the Chrome release. VJ uses IPB 2.x, not IPB 3. Most IPB 2.x bugs were fixed in 3 and they opted to NOT release fixes for the 2.x series unless they were security-related.

I run a large Invision Power Board forum that's even more customized than VJ is. The search flooding problem with Chrome exists in the IPB 2.x codebase (which VJ uses) and does not exist in the IPB 3.0 code base (which Ewok is going to be migrating to).

IPB changed how they link to "find posts" in 3, and IME (as a Chrome/IPB3 user) this change eliminated the flood control problem with Chrome.

Oops, my mistake. I thought you were referring to Chrome versions.

[K and L 27]

It's all good -- I have the problem on VJ and all other 2.x IPB boards with Chrome (5.0.342.1) too, but wanted to clarify that it's a known bug that's been fixed with the next version.

The last time I talked to Ewok about geeky admin things, he said he was working on upgrading to 3, and I'm assuming that's what update announcement's about, so if I'm right and that's what he's doing in the update, never fear: this will be fixed soon