Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File and image uploads broken if using google appengine sdk 1.9.x #81

Open
rogerthat-platform opened this issue May 14, 2014 · 6 comments

Comments

@rogerthat-platform
Copy link

Hello,

We have problems uploading images and files if we switch to the 1.9.x appengine sdk versions. The request handling code just does not get any FILES.

I could simulate the same error using sdk 1.8.9 when using the webob 1.1.1 library. Using the webob 0.9 version with the newer sdk does not seem to solve the problem, and is actually not supported by appengine as well.

Please help.

@aburgel
Copy link
Member

aburgel commented May 24, 2014

Can you provide any more information on this issue? Its hard to diagnose based on what you've posted so far.

@rogerthat-platform
Copy link
Author

Hi Alex,

We have a webshop working on django / appengine version 1.8.9

One of the models we defined had an image field, and is maintained by the
normal django admin forms.

When we run the site with SDK 1.8.9 it works perfectly, we can upload
images and they are stored correctly.

When we run the site with SDK 1.9.4 the image uploads fail.

I tried to debug, and what I found is that it probably is due to the newer
webob versions which are pushed starting from SDK 1.9.1

When I tried running the site with SDK 1.8.9 and configure webob 1.1, I get
the same problem.

I hope this helps.

I have used django in some projects, but I ain't an expert.

Regards,

Geert

On Sat, May 24, 2014 at 6:23 PM, Alex Burgel notifications@github.comwrote:

Can you provide any more information on this issue? Its hard to diagnose
based on what you've posted so far.


Reply to this email directly or view it on GitHubhttps://github.com//issues/81#issuecomment-44092173
.

Geert Audenaert

Email: geert@mobicage.com
Mobile: +32 474 20 15 41
Phone: +32 9 324 25 64
Fax: +32 9 324 25 65
Twitter: @FastGeert
Twitter: @rogerthat

MOBICAGE NV
Antwerpsesteenweg 19
9080 Lochristi
Belgium

Rogerthat, bringing together people and services.
http://www.rogerthat.net
Introduction: http://www.youtube.com/watch?v=7faWcV7aITo

@aburgel
Copy link
Member

aburgel commented May 30, 2014

What happens when you run this in production? Does it work? The production appengine service always uses the latest version of the SDK.

Also, do you see an error message or exception when the upload fails?

@rogerthat-platform
Copy link
Author

Adding Samaa.

In production it seems to work.

The error we get, is that we did not supply a file, while we clearly did.

Regards,

Geert

On Fri, May 30, 2014 at 9:50 PM, Alex Burgel notifications@github.com
wrote:

What happens when you run this in production? Does it work? The production
appengine service always uses the latest version of the SDK.

Also, do you see an error message or exception when the upload fails?


Reply to this email directly or view it on GitHub
#81 (comment)
.

Geert Audenaert

Email: geert@mobicage.com
Mobile: +32 474 20 15 41
Phone: +32 9 324 25 64
Fax: +32 9 324 25 65
Twitter: @FastGeert
Twitter: @rogerthat

MOBICAGE NV
Antwerpsesteenweg 19
9080 Lochristi
Belgium

Rogerthat, bringing together people and services.
http://www.rogerthat.net
Introduction: http://www.youtube.com/watch?v=7faWcV7aITo

@aburgel
Copy link
Member

aburgel commented May 31, 2014

I'm not sure I can provide much help based on those details. If you could provide an exception or trace through the code in some way to find where you think the error is, then I might be able to give you more help.

Also, is this an issue with webob or with djangoappengine?

@tkmunzwa
Copy link

I might be running into the same issue: request.FILES is an empty dict after POST'ing a form that includes a file upload (SDK 1.9.17). My investigations are ongoing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants