Hi,
Sorry, I have to bump thread back up again. We still have no clear idea how
to address this issue, which only happens sporadically on our production
server (and we can't reproduce it locally).
We have screens with Ajax Buttons which submit forms, but also disable/hide
these Ajax buttons. I
You're probably experiencing double clicks on your ajax buttons.
When the second request reaches the button, is is already disabled again.
Check this:
http://wicketinaction.com/2008/12/preventing-double-ajax-requests-in-3-lines-of-code/
Sven
On 10/16/2012 06:24 PM, eugenebalt wrote:
Hi,
Thanks Sven, that was it! They were clicking again while the form was still
processing.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/WicketRuntimeException-Submit-Button-is-not-enabled-tp4651180p4653019.html
Sent from the Users forum mailing list archive at
Thanks a lot. In our case, we have an AjaxButton that maps to a input
type=submit.
Would using the input type Button get rid of this problem?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/WicketRuntimeException-Submit-Button-is-not-enabled-tp4651180p4651231.html
No, they are interchangeable.
On 14/08/2012 11:42 AM, eugenebalt wrote:
Thanks a lot. In our case, we have an AjaxButton that maps to a input
type=submit.
Would using the input type Button get rid of this problem?
--
View this message in context:
It is true that we have multiple buttons on our form that we are
disabling/hiding selectively.
Our scenario: a panel that contains the button Edit, and then when it's
clicked, the panel opens and Edit is replaced by two other visible buttons
- Submit and Cancel. Edit is gone. We need this dynamic
with
it.
~ Thank you,
Paul Bors
-Original Message-
From: eugenebalt [mailto:eugeneb...@yahoo.com]
Sent: Tuesday, August 14, 2012 12:16 PM
To: users@wicket.apache.org
Subject: Re: WicketRuntimeException: Submit Button ... is not enabled
It is true that we have multiple buttons on our form that we
Hi,
When a form is submitted, it checks whether the submitting component is
a Wicket component. If it is (your case), it makes sure that it's
enabled and visible. I guess this is to prevent users manipulating with
the form submission process. In any case, if any of the 2 conditions is
not
