Wedge
Public area => The Pub => Features => Topic started by: Nao on March 20th, 2012, 04:22 PM
-
Silly idea or not?
Instead of disabling the submit button we could check at post time the last post by the same author in the same topic or board. If it has the same contents, just skip posting it and return to the topic.
Would solve problems that occur when clicking submit and the server is down at that precise moment.
-
I don't have a problem with that :)
-
+1 :yobrother:
-
Would it be worth making as a plugin first to see how well received it is?
-
Would it be worth making as a plugin first to see how well received it is?
-
I already have 15 in my repositories, with fragments and ideas for a few more on top :P What's another plugin between friends?
Main reason is that while I like the idea, I'm not yet entirely sold on its usefulness.
-
Would it be worth making as a plugin first to see how well received it is?
such a function (if not mistaken) is in vb
check for duplication of a handy feature
-
As you like, Pete... ;)
Usefulness?
Just do it my way. Have a Wifi or 3G device. Type while you're moving to another place where reception isn't as good. Sit down. Press Submit. "Server not available". Oops. Moving back to that place 3 meters farther... Submit. Oh crap, it doesn't register it.
Solution: pray that you can copy the contents of your message (sometimes it'll also disable the textarea IIRC, making it impossible to copy it), press Reload, paste your post, submit.
It has happened to me quite a few times because on my porch, right where I'm used to smoking my cigarette with my iPod in hand, I'm about 30 centimetres away from the limit of my Wifi connectivity. Meaning if I bend a bit too much, I'll lose connectivity. Not fun.
-
In that case, there should actually be no reason to do so. There is still a duplicate-post check being made on the server through the internal system (where it stores a unique value between form and session and checks one against the other)
I'm not really sure why the submit button actually gets disabled in that situation, there's little reason for it...
-
Useful because to get rid of crossposters / spammers. I like this idea.
-
It won't solve either. The sole point of this suggestion is to prevent the same post being posted twice in the same thread. That said we could expand it to prevent that kind of spam, though I'm not sure how effective it would really be.
-
In that case, there should actually be no reason to do so. There is still a duplicate-post check being made on the server through the internal system (where it stores a unique value between form and session and checks one against the other)
I'm not really sure why the submit button actually gets disabled in that situation, there's little reason for it...
-
Correct. Take out the checkSubmitOnce call as part of the form and see what happens ;)
-
Then what is checkSubmitOnce there for...?!
-
Doing it on the client side and preventing server load... I think.
-
Meh... How often does that happen!
-
Not nearly that often actually. Certainly rare enough that it should be OK to drop the client side stuff.
-
Yup.
I think we should make a poll out of this...?
-
Can do :)
-
Thanks ;)
-
As you like, Pete... ;)
Usefulness?
Just do it my way. Have a Wifi or 3G device. Type while you're moving to another place where reception isn't as good. Sit down. Press Submit. "Server not available". Oops. Moving back to that place 3 meters farther... Submit. Oh crap, it doesn't register it.
Solution: pray that you can copy the contents of your message (sometimes it'll also disable the textarea IIRC, making it impossible to copy it), press Reload, paste your post, submit.
It has happened to me quite a few times because on my porch, right where I'm used to smoking my cigarette with my iPod in hand, I'm about 30 centimetres away from the limit of my Wifi connectivity. Meaning if I bend a bit too much, I'll lose connectivity. Not fun.
My two centavos :)