You might be also interested in using https://github.com/l0rdn1kk0n/wicket-clientside-logging
On Wed, May 21, 2025 at 2:04 PM Johan Stuyts <johanstu...@squins.com> wrote: > Op Tue, 20 May 2025 16:00:25 +0200 schreef Ernesto Reinaldo Barreiro < > reier...@gmail.com>: > > > The real problem for me is to find out why those requests fail and fix > > infrastructure. If this happens always in the same place. You could: > > A web application firewall may use heuristics which may block things very > sporadically. > > But it turned out to be a JavaScript error. See my response to Martin. > > > - Have a hidden refresh UI button (this could be added for instance as > > an AJAX behavior to be added to some panels. This button will trigger > a > > normal AJAX repaint (not a post) > > - Combine the previous point with the listener... Then the request > fails > > => 1) you show some notification telling the user request failed 2) > make > > the button visible. Another variation would be if the request fails > you > > don't tell the user but click on this hidden refresh button. > > Good options. It is better that the user knows something is wrong instead > of just trying, and maybe corrupting, stuff. The dialog could also tell the > user to copy any changes made to prevent them from getting lost. > > > - I would also only enable the submit button once the UI is correct. > > But this also depends on Ajax calls succeeding. > > -- > Best regards / Met vriendelijke groet, > > Johan Stuyts > Squins IT Solutions BV > Oranjestraat 30 > 2983 HS Ridderkerk > The Netherlands > www.squins.com > Chamber of commerce Rotterdam: 24435103 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
