-enable the page
beneath -
the one with the form on it.
Chris
-Original Message-
From: Douglas Ferguson [mailto:doug...@douglasferguson.us]
Sent: Monday, 29 November 2010 6:53 PM
To: users@wicket.apache.org
Subject: Re: component not visible exception
Could this be happening
@wicket.apache.org
Subject: Re: component not visible exception
Could this be happening because of the back button?
D/
On Nov 28, 2010, at 4:54 AM, Chris Colman wrote:
I had a similar problem. In my scenario it occurred when a
ModalWindow
was brought up when a form failed validation. When they clicked ok
-
From: Douglas Ferguson [mailto:doug...@douglasferguson.us]
Sent: Monday, 29 November 2010 6:53 PM
To: users@wicket.apache.org
Subject: Re: component not visible exception
Could this be happening because of the back button?
D/
On Nov 28, 2010, at 4:54 AM, Chris Colman wrote:
I had a similar
disappear and thus re-enable the page beneath -
the one with the form on it.
Chris
-Original Message-
From: Douglas Ferguson [mailto:doug...@douglasferguson.us]
Sent: Monday, 29 November 2010 6:53 PM
To: users@wicket.apache.org
Subject: Re: component not visible exception
Could
the ModalWindow simply disappear and thus re-enable the page beneath -
the one with the form on it.
Chris
-Original Message-
From: Douglas Ferguson [mailto:doug...@douglasferguson.us]
Sent: Monday, 29 November 2010 6:53 PM
To: users@wicket.apache.org
Subject: Re: component
-Original Message-
From: Douglas Ferguson [mailto:doug...@douglasferguson.us]
Sent: Monday, 29 November 2010 6:53 PM
To: users@wicket.apache.org
Subject: Re: component not visible exception
Could this be happening because of the back button?
D/
On Nov 28, 2010, at 4:54
To: users@wicket.apache.org
Subject: Re: component not visible exception
Could this be happening because of the back button?
D/
On Nov 28, 2010, at 4:54 AM, Chris Colman wrote:
I had a similar problem. In my scenario it occurred when a
ModalWindow
was brought up when
[mailto:doug...@douglasferguson.us]
Sent: Monday, 29 November 2010 6:53 PM
To: users@wicket.apache.org
Subject: Re: component not visible exception
Could this be happening because of the back button?
D/
On Nov 28, 2010, at 4:54 AM, Chris Colman wrote:
I had a similar problem. In my scenario
[mailto:doug...@douglasferguson.us]
Sent: Monday, 29 November 2010 6:53 PM
To: users@wicket.apache.org
Subject: Re: component not visible exception
Could this be happening because of the back button?
D/
On Nov 28, 2010, at 4:54 AM, Chris Colman wrote:
I had a similar problem. In my
To: users@wicket.apache.org
Subject: Re: component not visible exception
Could this be happening because of the back button?
D/
On Nov 28, 2010, at 4:54 AM, Chris Colman wrote:
I had a similar problem. In my scenario it occurred when a
ModalWindow
was brought up when a form failed validation
To: users@wicket.apache.org
Subject: Re: component not visible exception
Could this be happening because of the back button?
D/
On Nov 28, 2010, at 4:54 AM, Chris Colman wrote:
I had a similar problem. In my scenario it occurred when a
ModalWindow
was brought up when a form failed validation
and thus re-enable the page beneath -
the one with the form on it.
Chris
-Original Message-
From: Douglas Ferguson [mailto:doug...@douglasferguson.us]
Sent: Monday, 29 November 2010 6:53 PM
To: users@wicket.apache.org
Subject: Re: component not visible exception
Could this be happening
on it.
Chris
-Original Message-
From: Douglas Ferguson [mailto:doug...@douglasferguson.us]
Sent: Monday, 29 November 2010 6:53 PM
To: users@wicket.apache.org
Subject: Re: component not visible exception
Could this be happening because of the back button?
D/
On Nov 28, 2010, at 4:54 AM
-
From: Douglas Ferguson [mailto:doug...@douglasferguson.us]
Sent: Monday, 29 November 2010 6:53 PM
To: users@wicket.apache.org
Subject: Re: component not visible exception
Could this be happening because of the back button?
D/
On Nov 28, 2010, at 4:54 AM, Chris Colman wrote:
I had a similar
That seems more likely to me.
Is there anything I could do to prevent this?
D/
On Nov 29, 2010, at 1:21 PM, Igor Vaynberg wrote:
another possibility, if this page is using hybrid url coding strategy,
is that the session expires and the form is submitted against a new
instance of the page -
this is a shortcoming of the hybrid coding strategy. you can try
tweaking it so that if it detects a url with page id but page id is
not found in session it can throw a stale page exception. submit a
patch and we can role it into core.
-igor
On Mon, Nov 29, 2010 at 2:31 PM, Douglas Ferguson
on it.
Chris
-Original Message-
From: Douglas Ferguson [mailto:doug...@douglasferguson.us]
Sent: Monday, 29 November 2010 6:53 PM
To: users@wicket.apache.org
Subject: Re: component not visible exception
Could this be happening because of the back button?
D/
On Nov 28, 2010, at 4:54 AM
I had a similar problem. In my scenario it occurred when a ModalWindow
was brought up when a form failed validation. When they clicked ok to
close the ModalWindow and then clicked Submit on the form again I got a
similar message saying that the Submit button was no longer visible.
It doesn't
Could this be happening because of the back button?
D/
On Nov 28, 2010, at 4:54 AM, Chris Colman wrote:
I had a similar problem. In my scenario it occurred when a ModalWindow
was brought up when a form failed validation. When they clicked ok to
close the ModalWindow and then clicked Submit
Look for any setVisible(false) or isVisible implementation changing your
form visibility in an undesirable way. Basically you user in clicking in an
not visible in the hierarchy submitting component.
On Fri, Nov 26, 2010 at 2:12 PM, Douglas Ferguson
doug...@douglasferguson.us wrote:
I have an
20 matches
Mail list logo
