wicket form and browser back

2013-10-01 Thread Karl-Heinz Golz
hello, I know that is an ongoing discussion point for years but nevertheless I would like to ask you whether there are good solutions in the meantime. In my web application (WICKET 6.5) there is a quite big form and I want to detect and react when a user goes back to an older version of this

Re: wicket form and browser back

2013-10-01 Thread Martin Grigorov
Hi, Mark the page as non-versioned (Page.setVersioned(false)). This way there won't be previous version of page. When the user uses browser back button she will go to the previous page, not to the previous version of the current page. On Tue, Oct 1, 2013 at 9:35 AM, Karl-Heinz Golz

Re: Wicket-bootstrap Bootstrap 3 support

2013-10-01 Thread Michael Haitz
hi, i've fixed wicket-webjars and pushed a new version (0.3.0) to maven central. https://github.com/l0rdn1kk0n/wicket-webjars/releases/tag/wicket-webjars-0.3.0 i've also deployed a new 0.9.0-SNAPSHOT version of wicket-bootstrap that uses wicket-webjars 0.3.0. Michael Am 26.09.2013 um 11:42

Re: wicket form and browser back

2013-10-01 Thread Karl-Heinz Golz
Thank you, Martin, that works well. But next question: when a user goes back and forward via browser back and forward buttons, then already filled in fields will be empty (using Firefox). Is it possible to handle browser back the same way like form submit? That is, browser back causes a trip to

Re: wicket form and browser back

2013-10-01 Thread Martin Grigorov
I'm not sure this is possible. But you can use AjaxFormComponentUpdatingBehavior(change) to update the server state once a form component is changed at the client side. On Tue, Oct 1, 2013 at 10:53 AM, Karl-Heinz Golz karl-heinz.g...@t-online.de wrote: Thank you, Martin, that works well. But

Re: wicket form and browser back

2013-10-01 Thread Michael Mosmann
AFAIK does a browser back bypass everything on the page. Maybe it is better to avoid paging if there is dependent state on different pages (use ajax instead and make it single-page). michael:) Am 01.10.13 10:53, schrieb Karl-Heinz Golz: Thank you, Martin, that works well. But next question:

How do I disable GZip compression in Wicket 6?

2013-10-01 Thread Marcus Ludvigsson
Hi, In Wicket 1.4.22 I used to be able to disable GZip compression like this: WebApplication.getResourceSettings().setDisableGZipCompression(true); That way seems to be removed in 6 and I can't find anything in the migration guides regarding this. Have anyone else stumbled upon this and

Re: wicket form and browser back

2013-10-01 Thread Karl-Heinz Golz
Thank you Martin and Michael. I will try that and hope, the combination of setVersioned(false) and using AJAX for all form components will solve my problem. Am 01.10.2013 11:57, schrieb Michael Mosmann: AFAIK does a browser back bypass everything on the page. Maybe it is better to avoid paging

Re: How do I disable GZip compression in Wicket 6?

2013-10-01 Thread Martin Grigorov
Hi, This setting has been removed with 1.5.0. Wicket does not compress the response anymore. If compression is needed then the application can use either web container's settings or a custom Servlet Filter. So you have nothing to do. Just remove this line from your config. On Tue, Oct 1, 2013

RE: How do I disable GZip compression in Wicket 6?

2013-10-01 Thread Paul Bors
Hey Karl, Would you kindly update the migration wiki page for the rest of us? ~ Thank you, Paul Bors -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: Tuesday, October 01, 2013 10:20 AM To: users@wicket.apache.org Subject: Re: How do I disable GZip

Re: how to connect elements - label and input (checkbox)

2013-10-01 Thread miguel
I found this searching for the same answer and my existing code was: input type=checkbox wicket:id=acceptTerms/ label wicket:for=acceptTermsI agree to the terms/label but the output is: input type=checkbox name=acceptTerms id=acceptTerms5/ label for=acceptTerms5I agree to the terms/label but

Re: how to connect elements - label and input (checkbox)

2013-10-01 Thread miguel
aha! it seems that the first time it renders it doesn't include the id in the checkbox. when it fails validation, the id appears and the label works as expected. i'll dig into the code when i get a chance. -- View this message in context: