that simply does not work. you'll have to write custom code to store in
blobstore or cloud storage if you don't want to keep uploaded images in
the DB.
note that images that are static that you deploy with the application
can be stored in a static folder and mapped via app.yaml to be handled
with a static file handler and caching policies set in app.yaml
cfh
On 11/24/13, 2:43 , St. Pirsch wrote:
I am experiencing the same problem right now. I am running an application
with version 2.51 on GAE, where images are uploaded via the standard
Field('file', 'upload'),
and retrieved using the download helper, which continues to work correctly.
Today, I tried to launch an application on ver. 2.7.4 using a static
upload path:
Field('logo', 'upload', uploadfolder=request.folder+'static/images'),
Images are embedded via:
<img src="{{=URL('static', '/images/'+kopf.projekt.logo)}}" border="0">
which does not work.
In the edit menu of the GRID-helper all uploaded images are displayed
correctly in GAE.
If someone knows how to handle this, she/he would be of great help for me.
Thanks,
Stephan
Le samedi 23 novembre 2013 13:36:43 UTC+1, Scott Hunter a écrit :
Are there any issues with using the various upload-related Field options
when runnning under GAE? In particular, I'm wondering about the
uploadfolder & uploadseparate options. How would using these affect using
response.download in a controller?
- Scott
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups "web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
