Should we set the parent form to multipart somewhere around the post-configure / pre-render of a FileUpload? It could find its parent Form and do it automatically. I guess the question is really: is there anytime that we *wouldn't* want that to happen automatically? If we do it post-configure / pre-render, we can do it anytime there is a visible file upload field.
On Tue, Jan 18, 2011 at 6:31 PM, Igor Vaynberg <igor.vaynb...@gmail.com>wrote: > what about cases where users swap in an upload field later? in this > case visibility isnt going to help. this is why we provide a way for > the user to hard-set the value to true via form.setmultipart(true) - > which is what i think exl should do. > > -igor > > On Tue, Jan 18, 2011 at 3:41 PM, Pedro Santos <pedros...@gmail.com> wrote: > > I tested the quickstart with the HomeForm multipart property set to true > and > > it is all ok. > > I'm 1+ to change Form#isMultipart implementation to don't test the form > > components visibility while visiting children. It is quite natural to > have > > them set to true and sent back to browser in an AJAX response, in which > case > > the form can possible do not have the correspondent enctype tag > attribute. > > > > On Tue, Jan 18, 2011 at 3:43 PM, Pedro Santos <pedros...@gmail.com> > wrote: > > > >> Set the root form as multipart in the onInitialize method, Wicket will > fail > >> in detect the form as multipart if the inner one with the upload field > is > >> not visible at the first render. > >> > >> On Tue, Jan 18, 2011 at 8:43 AM, exl <eric....@uwa.edu.au> wrote: > >> > >>> > >>> Encountering a show stopper for our project that involves being able to > >>> deal > >>> with a form containing a file upload that can be revealed depending on > >>> whether that particular workflow is desired. > >>> > >>> Please see attached quickstart project that shows this failing using > >>> Wicket > >>> version 1.4.15 ( > >>> > >>> > http://apache-wicket.1842946.n4.nabble.com/file/n3221308/nestedFormsWithMultipart.zip > >>> nestedFormsWithMultipart.zip ). Basically, first click on the New > button > >>> to > >>> reveal the hidden form (that has the file upload). Now hit the Cancel > >>> button and the form is hidden. Ok, but now if you click on New again > the > >>> an > >>> multipart exception is thrown. > >>> > >>> This may be somewhat related to "Nested Forms and Multipart Fileupload > >>> Issue" > >>> ( > >>> > http://apache-wicket.1842946.n4.nabble.com/Nested-Forms-and-Multipart-Fileupload-Issue-tp1844365p1844365.html > >>> ), > >>> but a quick read of that thread suggest it is dealing with modal stuff > >>> (thus > >>> I created this post). > >>> > >>> I think this is a bug, as I don't remember this failing in the previous > >>> version we were using (Wicket 1.4.9) - though this is still to be > >>> confirmed. > >>> > >>> ----- > >>> > >>> Eric is learning how to use Wicket and enjoying the experience so > far... > >>> -- > >>> View this message in context: > >>> > http://apache-wicket.1842946.n4.nabble.com/Multipart-issues-in-Wicket-1-4-15-tp3221308p3221308.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 > >>> > >>> > >> > >> > >> -- > >> Pedro Henrique Oliveira dos Santos > >> > > > > > > > > -- > > Pedro Henrique Oliveira dos Santos > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Jeremy Thomerson http://wickettraining.com *Need a CMS for Wicket? Use Brix! http://brixcms.org*
