This is a pretty shocking bug (or lack of documentation?) from Google. There doesn't appear to be a consistent way to decode the post results that come from the BlobstoreUploadHandler. There was a bug in the issues list for this but I can't find it. I should put in another one really but there doesn't seem to be any point.
What I do is when the user hits the submit button I send the form results via an ajax request and once that returns I submit the form to do the file upload. Pretty sad you have to do that and it means you're requiring javascript for something that really shouldn't need it. On Oct 25, 10:49 am, Agustin Horischnik <[email protected]> wrote: > Hey, no luck with this? Did you solve this at all? > > On Aug 31, 12:40 pm, Agustin Horischnik <[email protected]> wrote: > > > > > > > > > I think I'm having the same issue... > > > I have a multi-part form posting to ablobstoreuploadhandler. > > There's four form fields: > > > 2 input type=file > > 1 input type=text > > 1 textarea > > > Those map to... > > > 2blobstore.BlobReferenceProperty > > 1 StringProperty > > 1 TextProperty > > > ... respectively, on my model class. > > > And the problem is... when I submit an input string such as "á é í ó ú > > and ñ", I get: "IuEg6SDtIPMg+iBhbmQg8SI=", both on the StringProperty > > and TextProperty. > > At least, this is what I see on the Data viewer or when I output on > > the app. > > > Any workarounds you can think of? Anybody else is having this problem? > > > On Aug 3, 3:54 pm, ekampf <[email protected]> wrote: > > > > yep.. > > > It doesnt happend on the local dev server... its definately something > > > undocumented happening on AppEngine > > > > On Aug 3, 10:54 am, alon <[email protected]> wrote: > > > > > it outputs as abase64string? im guessing the post is multi-part post > > > > right? > > > > > On Aug 3, 10:39 am, ekampf <[email protected]> wrote: > > > > > > This happens when text fields are sent via POST and go through the > > > > >Blobstoreuploadhandler. > > > > > When English text is used I get the text. > > > > > When Hebrew is used I get abase64string... > > > > > > I'm not looking at the datastore dashboard. I'm looking at the actual > > > > > POST data (via logging) > > > > > > On Aug 3, 10:18 am, alon <[email protected]> wrote: > > > > > > > Does that happen everytime on theblobstoreonly api? or regular text > > > > > > - > > > > > > > > datastore? > > > > > > > One more thing, there is a huge difference on how the text is being > > > > > > displayed on the datastore dashboard. are you sure its being saved > > > > > > as > > > > > >base64? the pageencodingfor the production datastore browser is > > > > > > massed up and cant display hebrew correctly in oppose to the local > > > > > > dev > > > > > > version which has utf8encodingdisplay. > > > > > > > On Jul 23, 2:09 pm, ekampf <[email protected]> wrote: > > > > > > > > I have a form with a file input and a text input field. > > > > > > > When users type Hebrew text I get aBase64encoded string on the > > > > > > > server. When typing English I get a nonBase64string. > > > > > > > On the development server I get a regular Unicode string (what I'd > > > > > > > expect) > > > > > > > > Cant find any mentions of this in the docs. > > > > > > > What the behavior I should expect on production? Is this a bug? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
