tedd wrote:
Hi gang:
This is probably trivial for most of you, but here's my solution to the
problem I presented earlier.
The problem was, I just wanted to be certain that if a use clicked a
button that they could only do it once. Sounds simple enough, huh?
Certainly, one can use
At 4:23 PM -0700 3/21/08, Jim Lucas wrote:
It would require a little JS, but you could use the onUnload feature
and pop up a warning that would tell them the problem(s) of leaving
this page. Then use the confirm() method from JS to either allow or
deny them to leave the current page.
I
At 7:21 AM + 3/22/08, Lester Caine wrote:
tedd wrote:
Hi gang:
This is probably trivial for most of you, but here's my solution to
the problem I presented earlier.
The problem was, I just wanted to be certain that if a use clicked
a button that they could only do it once. Sounds simple
Hi gang:
This is probably trivial for most of you, but here's my solution to
the problem I presented earlier.
The problem was, I just wanted to be certain that if a use clicked a
button that they could only do it once. Sounds simple enough, huh?
Certainly, one can use javascript, but I
On Fri, Mar 21, 2008 at 2:24 PM, tedd [EMAIL PROTECTED] wrote:
Hi gang:
This is probably trivial for most of you, but here's my solution to
the problem I presented earlier.
The problem was, I just wanted to be certain that if a use clicked a
button that they could only do it once.
tedd wrote:
Hi gang:
This is probably trivial for most of you, but here's my solution to the
problem I presented earlier.
The problem was, I just wanted to be certain that if a use clicked a
button that they could only do it once. Sounds simple enough, huh?
Certainly, one can use
] Double click problem
At 4:19 PM + 3/19/08, Richard Heyes wrote:
tedd wrote:
// ...
Your first (and the quickest by far) method to employ would be to
disable the submit button using Jabbascript when the form is
submitted. That will stop the vast majority of occurrences. You
could also
PROTECTED]
To: php-general@lists.php.net
Sent: Wednesday, March 19, 2008 11:43:06 AM
Subject: Re: [PHP] Double click problem
At 4:19 PM + 3/19/08, Richard Heyes wrote:
tedd wrote:
// ...
Your first (and the quickest by far) method to employ would be to
disable the submit
- Original Message
From: Eric Butera [EMAIL PROTECTED]
To: Lamp Lists [EMAIL PROTECTED]
Cc: tedd [EMAIL PROTECTED]; php-general@lists.php.net
Sent: Thursday, March 20, 2008 11:00:19 AM
Subject: Re: [PHP] Double click problem
On Thu, Mar 20, 2008 at 10:39 AM, Lamp Lists [EMAIL PROTECTED
Hi gang:
I have a situation where users can purchase stuff online.
In the last step in the process, the user clicks a confirm purchase
button and their credit card is checked and if it's valid, they are
awarded the product. Everything works, but it takes a little time to
check the credit
On Wed, Mar 19, 2008 at 11:48 AM, tedd [EMAIL PROTECTED] wrote:
In the last step in the process, the user clicks a confirm purchase
button and their credit card is checked and if it's valid, they are
awarded the product. Everything works, but it takes a little time to
check the credit card.
tedd wrote:
I have a situation where users can purchase stuff online.
In the last step in the process, the user clicks a confirm purchase
button and their credit card is checked and if it's valid, they are
awarded the product. Everything works, but it takes a little time to
check the credit
Hi gang:
I have a situation where users can purchase stuff online.
In the last step in the process, the user clicks a confirm purchase
button and their credit card is checked and if it's valid, they are
awarded the product. Everything works, but it takes a little time to
check the credit
Hi gang:
I have a situation where users can purchase stuff online.
In the last step in the process, the user clicks a confirm purchase
button and their credit card is checked and if it's valid, they are
awarded the product. Everything works, but it takes a little time to
check the credit
On Wed, Mar 19, 2008 at 11:48 AM, tedd [EMAIL PROTECTED] wrote:
Hi gang:
I have a situation where users can purchase stuff online.
In the last step in the process, the user clicks a confirm purchase
button and their credit card is checked and if it's valid, they are
awarded the product.
On Wed, Mar 19, 2008 at 11:48 AM, tedd [EMAIL PROTECTED] wrote:
Hi gang:
I have a situation where users can purchase stuff online.
In the last step in the process, the user clicks a confirm purchase
button and their credit card is checked and if it's valid, they are
awarded the product.
On Wed, Mar 19, 2008 at 12:01 PM, Eric Butera [EMAIL PROTECTED] wrote:
Unique form tokens.
Generate a token when the form is displayed and save that value in the
session.
Then on post check it and remove it. Then if they re-submit it will
not exist therefore be invalid.
I like
At 4:00 PM + 3/19/08, Edward Kay wrote:
Oh, I'd also add a bit of text near the button saying:
Please click this button ONCE only. Clicking again may result in your
credit card being billed twice.
I'm always much more precise with my clicking when such warnings are
displayed :)
That's
tedd wrote:
// ...
Your first (and the quickest by far) method to employ would be to
disable the submit button using Jabbascript when the form is submitted.
That will stop the vast majority of occurrences. You could also employ
an intermediary page which actually does the card processing and
At 4:19 PM + 3/19/08, Richard Heyes wrote:
tedd wrote:
// ...
Your first (and the quickest by far) method to employ would be to
disable the submit button using Jabbascript when the form is
submitted. That will stop the vast majority of occurrences. You
could also employ an intermediary
Daniel Brown wrote:
On Wed, Mar 19, 2008 at 12:01 PM, Eric Butera [EMAIL PROTECTED] wrote:
Unique form tokens.
Generate a token when the form is displayed and save that value in the session.
Then on post check it and remove it. Then if they re-submit it will
not exist therefore be
On Wed, Mar 19, 2008 at 12:44 PM, Jim Lucas [EMAIL PROTECTED] wrote:
Daniel Brown wrote:
I like Eric's method better than the timestamp method I proposed.
Much cleaner and easier to institute, and I'd hazard a guess at it
being more reliable as well.
The initial problem that
22 matches
Mail list logo