Re: Multiple Form Feedback Messages / Showing one / Canceling of Form Processing? Filtering Feedback Messages?
A Simple Way? Implement your own FeedbackPanel and set the visiblity of listItem to false after one line has been rendered. The counter for the number of renderd feedback messages has to be global. Dirty but simple;) -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Multiple-Form-Feedback-Messages-Showing-one-Canceling-of-Form-Processing-Filtering-Feedback-Messages-tp4656643p4656655.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Why does a ModalWindow create a Tag to be rendered in?
The proposted patch in WICKET-3404 should really be in 7. Thanks for explaining! Sven Meier wrote >>Can anyone Tell me the reason for using a > > at this location? > > This is done to allow the following nesting: > > -- > > Form [1] > > > ModalWindow [2] > -- > > Form [3] > > > FormComponent [4] > > Note that in Wicket nested Forms [3] are rendered as > > s. > When ModalWindow [2] pulls its content [3] out of the dom tree and puts > it into a top-level > > , the nested input fields [4] have to be > wrapped in a synthetic > > : > > -- > > Form [1] > > > ModalWindow [2] > -- > > > > * generated by modal.js * > -- > > Form [3] > > > FormComponent [4] > > There have been proposals already on how to improve this, see > WICKET-1826 and WICKET-3404 for inspirations. > Hopefully this is something we can address in Wicket 7 (i.e. this won't > be possible without API breaks). > > Regards > Sven > > > On 02/15/2013 11:51 AM, mwwbf wrote: >> Hi Everyone, >> I'm using ModalWindows and AjaxEditableLabels and everything was working >> fine for me. >> But a stupid tester decided to use the return key(insted of just clicking >> the next item) after he entered something in a AjaxEditableLable within a >> ModalWindow. >> >> This caused the Form created in >> https://github.com/apache/wicket/blob/master/wicket-extensions/src/main/java/org/apache/wicket/extensions/ajax/markup/html/modal/res/modal.js >> Line 1181 >> to submit. >> After I Changed the > > Tag in lline 1181 and the > > in line 1243 of >> modal.js everything worked fine again. >> >> Can anyone Tell me the reason for using a > > at this location? >> >> Thanks and greetings >> michael >> >> >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/Why-does-a-ModalWindow-create-a-form-Tag-to-be-rendered-in-tp4656394.html >> Sent from the Users forum mailing list archive at Nabble.com. >> >> - >> To unsubscribe, e-mail: > users-unsubscribe@.apache >> For additional commands, e-mail: > users-help@.apache >> > > > - > To unsubscribe, e-mail: > users-unsubscribe@.apache > For additional commands, e-mail: > users-help@.apache -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Why-does-a-ModalWindow-create-a-form-Tag-to-be-rendered-in-tp4656394p4656412.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Why does a ModalWindow create a Tag to be rendered in?
Hi Everyone, I'm using ModalWindows and AjaxEditableLabels and everything was working fine for me. But a stupid tester decided to use the return key(insted of just clicking the next item) after he entered something in a AjaxEditableLable within a ModalWindow. This caused the Form created in https://github.com/apache/wicket/blob/master/wicket-extensions/src/main/java/org/apache/wicket/extensions/ajax/markup/html/modal/res/modal.js Line 1181 to submit. After I Changed the Tag in lline 1181 and the in line 1243 of modal.js everything worked fine again. Can anyone Tell me the reason for using a at this location? Thanks and greetings michael -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Why-does-a-ModalWindow-create-a-form-Tag-to-be-rendered-in-tp4656394.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
FileUploadField in ModalWindow via AjaxButton does not work anymore.(1.5.8 to 6.0.0)
Hi there, I'm migrating from Wicket 1.5.8 to 6.0.0 and solved almost every problem I encountered so far. But I could not figure out why my FileUploadFields do not work anymore. I'm using one FileUploadField in a Form in a ModalWindow and use the AjaxButton to submit the From. All other Fields work perfectly fine. But as soon as I add a FileUploadField to the Form i get the following error message on the Wicket Ajax Debug Panel. Wicket.Ajax: Wicket.Ajax.Call.failure: Error while parsing response: Could not find root element Did anyone encounter a similar problem? I dont even have an idea where to continue debugging cause non of my onValidate(..) onSubmit(..) or any methode of FileUploadPanel is ever called after the click. Thanks and regards michael -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/FileUploadField-in-ModalWindow-via-AjaxButton-does-not-work-anymore-1-5-8-to-6-0-0-tp4651936.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: FileUploadField in ModalWindow via AjaxButton does not work anymore.(1.5.8 to 6.0.0)
Well... I figured out that this error occurs when you use a AjaxSubmitLink or AjaxButton in a From with multiPart == true and only when using Opera 12.02. works with latest Firefox and Chrome. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/FileUploadField-in-ModalWindow-via-AjaxButton-does-not-work-anymore-1-5-8-to-6-0-0-tp4651936p4651976.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
