duplicate posted shout

[MainFrame]

Hi,

There seem to be a problem for some of my members. A lot of the messages they post in the shoutbox got posted twice. Got it myself a couple of times as well.

Regards,
MainFrame

 

[jellybelly]

one of my members have aso complained of this

 

[Cosmic]

Can you find out what browser they are using?

 

[Fillip H.]

I'm unable to duplicate this in Firefox, Google Chrome or Internet Explorer.

The only way duplicate shouts can be posted is if the Time Between Shouts is turned off, in which case it's the user accidentally hitting Enter twice in quick succession.

 

[MainFrame]

One of my staff members had this issue when using Opera.
But I think it has something to do with slow connections. I experienced the problem in Firefox mysql, and when it happened I pressed enter to submit my shout but my shout input field didn't clear and the shout was submitted twice before clearing.

I've purchased infernoshout in the past and used it for years, but with vBulletin 4, I couldn't get inferno to work so I made my own shoutbox and had the exact same problem with my own shoutbox. I fixed this by clearning the input field right after my .js had gathered the posted data in stead of waiting for the ajax request return a status code to clear the input field.

I don't have the time to continue to work on my own shoutbox so I'm glad you guys are back with a shoutbox that has a nice style and good set of features.

Regards,
MainFrame

 

[Fillip H.]

The problem with clearing it before AJAX has returned success is that if AJAX has an error of some description, the user would lose their shout.
It's a matter of the lesser of two evils.

 

[Trekkan]

I've had this happen to myself as well as a couple of members. I'm not finding it a huge issue, but at times there's lag after you hit the enter key. So you don't realize that the request was sent, so you hit enter again. Creating two entries.

Not sure if it can be fixed, but if the text entered was cleared as soon as enter was hit, THEN the request was sent to the server. If the request didn't make it, reprint the entered text into the input box.

Again, no idea if that can be done, but I think that's at least where the issue comes from.

 

[Fillip H.]

I'll look into it, maybe it'll make it in the bugfix version that's coming next week, if I find a way of doing it that works out

 

[Fillip H.]

It seems that I've been able to implement that change.

The only downside happens in a very very specific scenario:
If an user types a shout, attempts to save it, gets an error (thus restoring the shout), and then deletes the contents of the editor, the next time an error occurs contents of the editor will re-appear, unless the user has typed something else.
In short, it doesn't detect when an user empties the shout area.

However, I consider this to be an acceptable trade-off because errors should only be temporary anyway, and it's better to restore the shout one time too many than one time too little.

 

[Trekkan]

Sounds good! I think that's the better way to go with it as well, thanks!