Re: WOFileUpload Error After Change To 5.2
Re: WOFileUpload Error After Change To 5.2
- Subject: Re: WOFileUpload Error After Change To 5.2
- From: Jonathan Rochkind <email@hidden>
- Date: Mon, 14 Apr 2003 19:21:15 -0500
At 12:45 AM 4/15/2003 +0100, Jonathan Fleming wrote:
But the bug is: the filePath _should_ be null, but is instead set to the
name of the WOFileUpload element. The workaround is: manually set the
name element (create a 'name' binding on the WOFilePath, set it to some
constant, say "___FileUpload"). If the filePath equals this constant you
set it to, you know that it SHOULD have been null, but due to a WO bug it
wasn't.
Ok, my binding to filePath is sPicRefFull, should I now change this to
something like your suggestion for instance "___FileUpload1" for the 1st
fileUpload element and "___FileUpload2" for the other. What then do I do
with the original binding sPicRefFull?
Read what I wrote again. Do you currently have a 'name' binding on
WOFileUpload? I doubt it. My advice was to create one. This has nothing to
do with the bindings you already have.
That's interesting... so what do you do when say you want the user to
upload an image that is a thumbnail (gif) and one that is an enlargment
of the thumbnail (Jpeg)?
Give the two WOFileUploads two different names. I just haven't needed to do
that myself.
--Jonathan
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.