Forum Suggestions & User Assistance - This forum requires that you wait 30 seconds between posts. Please try again in 29 se

Bikeforums.net is a forum about nothing but bikes. Our community can help you find information about hard-to-find and localized information like bicycle tours, specialties like where in your area to have your recumbent bike serviced, or what are the best bicycle tires and seats for the activities you use your bike for.




sailorbenjamin
05-26-10, 05:08 PM
Do you guys get this every time you try to post a reply? I have my mouse set on single click but it's been that way for years. This double post error message has only sprung up in the salt week or two.


retrofit
05-26-10, 05:24 PM
Frequently, over the past month.

cuda2k
05-26-10, 05:24 PM
That's a new one for me. You're getting it on the first attempt to post? I'm guessing it is related to the issues we've been having with duplicate posting. I do know there is a 30 second post timer, but you seem to be tripping it through normal usage. I'm going to move this thread into the user assistance sub-forum so it gets the right eyes on it.


Zaphod Beeblebrox
05-26-10, 05:25 PM
Frequently, over the past month.

same.

I get it whether using Firefox or Chrome, on Windows or Debian Linux.

unterhausen
05-26-10, 05:26 PM
I've seen that. I don't think moderators can post in less than 30 seconds either

unterhausen
05-26-10, 05:26 PM
testing that theory

Looks like we can, maybe that's why we get so many double posts

repechage
05-26-10, 05:50 PM
testing that theory

Looks like we can, maybe that's why we get so many double posts

If I reply with a "with quote" then no problem. If I do a quick reply or hit the reply to post button, ding ding ding. I get the don't double post deal.
A few times it ignored my initial post, so those threads never got my input. It must just be a new feature where the software felt I had not made my point.

So it goes.

Rabid Koala
05-26-10, 06:07 PM
I have gotten that message several times.

ItsJustMe
05-26-10, 06:55 PM
It's done that about every 2nd or 3rd post for me since they changed to this wretched new system. There have been other threads where people mention it. The mods give dumb explanations like "bouncy mouse key" which I know for absolute certain are not the case since it happens even if you tab to the post button and press the space bar. It's been months and no sign of fixing it, I think we have to just learn to live with it, unless there's a software update that fixes it.

20grit
05-26-10, 07:59 PM
i've not gotten that response but it has told me i must wait 1 minute between pm's.

Tom Stormcrowe
05-27-10, 11:47 PM
We're hoping the next update will fix it. The issue has been reported to the development team, though.

As to the time between posts, and time between PM's, those are set limiter parameters to prevent post floods from Spammers. It gives us time to deal with them before they get over the deletion limit on the software before an Admin like me has to delete their posts because there are too many for the macro that the mod staff has to work with. If you have to cull a thousand posts, for example, it burns a lot of server time, and slows the forums down dramatically while it's being done.


It's done that about every 2nd or 3rd post for me since they changed to this wretched new system. There have been other threads where people mention it. The mods give dumb explanations like "bouncy mouse key" which I know for absolute certain are not the case since it happens even if you tab to the post button and press the space bar. It's been months and no sign of fixing it, I think we have to just learn to live with it, unless there's a software update that fixes it.

DMF
06-02-10, 01:24 PM
The 30 second interval isn't an issue (at least, not to me). The problem - as I'm sure you're aware, Tom - is that some level of the software is trying to submit the same post (at least) twice. The first one goes through and gets posted but the second one triggers the interval timer.

Edit: As this reply just did.


Fwiw, the last update seems to have helped but not cured the problem.