Re: restartResponseAtSignInPage()/continueToOriginalDestination() and dedicated LOGIN button
Keep it simple: just set the SignInPage as response page and give it an (optional) page reference to return to after login. Have fun Sven Am 14.11.2017 um 18:32 schrieb Henry Loenwind: Hi, I ran into a small issue when using restartResponseAtSignInPage() and continueToOriginalDestination() from a dedicated login button (i.e. a button that should keep the user on their current page, not link them into a restricted area). It basically works fine, but continueToOriginalDestination() sends them back into the onClick() of the login button...which no longer isVisible() because the user now is logged in. Naturally that doesn't work but gives a "friendly" error message. Now, "login in place" buttons are not that outlandish, so I wanted to ask how other people solve this problem. My first try was to manually wipe the page parameters from the InterceptData, but all that is accessible there is set(), get() and clear(). My next tries would then be to (a) re-implement my own InterceptData, which I do not really want to do---duplicating framework functionality by copy&pasting is ugly; or (b) subclass the Link to still be isVisible() but render as "" when the user is logged in. cu Henry - 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
restartResponseAtSignInPage()/continueToOriginalDestination() and dedicated LOGIN button
Hi, I ran into a small issue when using restartResponseAtSignInPage() and continueToOriginalDestination() from a dedicated login button (i.e. a button that should keep the user on their current page, not link them into a restricted area). It basically works fine, but continueToOriginalDestination() sends them back into the onClick() of the login button...which no longer isVisible() because the user now is logged in. Naturally that doesn't work but gives a "friendly" error message. Now, "login in place" buttons are not that outlandish, so I wanted to ask how other people solve this problem. My first try was to manually wipe the page parameters from the InterceptData, but all that is accessible there is set(), get() and clear(). My next tries would then be to (a) re-implement my own InterceptData, which I do not really want to do---duplicating framework functionality by copy&pasting is ugly; or (b) subclass the Link to still be isVisible() but render as "" when the user is logged in. cu Henry - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: WiQuery 6.x and JQuery UI draggable (auto-scroll) bug
Hi Rakesh, According to the github repo, WiQuery has not been updated since a while... You can give a try to wicket-jquery-ui if you like, it is running jquery-ui 1.12.1 Repo: https://github.com/sebfz1/wicket-jquery-ui Demo: http://www.7thweb.net/wicket-jquery-ui/draggable/ComponentDraggablePage Best regards, Sebastien. On Tue, Nov 14, 2017 at 2:08 PM, Rakesh A wrote: > Hi, > > We are using wiquery 6.13.0 to build some interactive UI. This includes > JQuery's UI draggable, droppable, etc. > jquery-ui-1.10.4 is used in wiquery-6.13.0 > > There was a bug with jquiery-ui in draggable component. The auto-scroll > does > not work properly, which can be seen using the below give jsfiddle link. > https://jsfiddle.net/mohammed_techie/5bv8wjuc/ > > It has been fixed along with few other bugs mentioned at below change log > link https://jqueryui.com/changelog/1.11.0/#interactions > > JQuery UI issue details can be found at > https://bugs.jqueryui.com/ticket/9379 > > It has been fixed by jquery ui, but unfortunately we cannot apply that fix > (in our code), only option is to have this latest JQuery UI (and draggable) > version as part of WiQuery. > > Are there plans to upgrade JQuery UI version in WiQuery 6.x branch ? > Any work around that we can use ? > > Regards, > Rakesh.A > > -- > Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum- > f1842947.html > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
WiQuery 6.x and JQuery UI draggable (auto-scroll) bug
Hi, We are using wiquery 6.13.0 to build some interactive UI. This includes JQuery's UI draggable, droppable, etc. jquery-ui-1.10.4 is used in wiquery-6.13.0 There was a bug with jquiery-ui in draggable component. The auto-scroll does not work properly, which can be seen using the below give jsfiddle link. https://jsfiddle.net/mohammed_techie/5bv8wjuc/ It has been fixed along with few other bugs mentioned at below change log link https://jqueryui.com/changelog/1.11.0/#interactions JQuery UI issue details can be found at https://bugs.jqueryui.com/ticket/9379 It has been fixed by jquery ui, but unfortunately we cannot apply that fix (in our code), only option is to have this latest JQuery UI (and draggable) version as part of WiQuery. Are there plans to upgrade JQuery UI version in WiQuery 6.x branch ? Any work around that we can use ? Regards, Rakesh.A -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
