#1435 - Flood Control is happening for a particular user
-
By Lhasadreams
- Added
- 0 views
| Identifier | #1435 |
|---|---|
| Issue type | Major issue (breaks an entire feature) |
| Title | Flood Control is happening for a particular user |
| Status | Completed |
| Handling member | Chris Graham |
| Addon | General / Uncategorised |
| Description | Hi,
One particular user is reporting almost constant Flood Control warnings. I have a goto meeting session with the user and I observed it first hand - the user could not post to the General Chat forum without getting the flood control error and the post would not get posted. He has tried a couple of different Windows 7 boxes and gets the same issue. I have just got his login details and tried to post to general chat as him and get the same flood control warning. His username is foxymk1 His password is mk1scooby Please can you take a look for me. Cheers Ade |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
Also looking at this user again.
If he creates a new topic an error is put out at the top of the page:
"Photobucket gave The Mk1 Golf Owners Club an API error – code 0 – Token and Token Secret not returned in response"
I wonder if that is something to do with the problem? He is not synced to Photobucket.
The Flood Control still kicks in for his posts.
Cheers
Ade
I have reduced the "Flood control form-submission time" from 5 seconds to 1 second for all the Primary Groups that people could belong to.
That has stop the Flood Control waring for foxy1mk1.
I do not understand why 5 seconds would be too much - do you ?
Please can the Photobucket error message looked into - if it is not related to this then I can raised another request.
I was wondering if it is a combination of CometChat and Photobucket ?
Cheers
Ade
1) Flood control running before and after a redirect, which happens when you post a topic
2) Unauthorised photobucket access requests now tidied up after 1h