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 the server and wicket gives controll to my application the same way it would be done when the user presses the submit button?
Am 01.10.2013 09:59, schrieb 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 <karl-heinz.g...@t-online.de >> wrote: > >> >> >> 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 form using the browser back button. When the user hits the submit >> button on that older version he will lose data. I would like to avoid >> that in some way. >> >> Suggestions and experiences are very welcome. >> >> Many thanks in advance >> Karl-Heinz >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
