Ok cool, we might leave it for now since the new release is almost here -
but thanks so much for documenting all your findings, no doubt it'll be
useful.
On Wed, Jul 1, 2015 at 1:01 PM, Lee H. popov.gh...@gmail.com wrote:
Regarding a fix. I guess there a few points:
1) This was all in Django
After killing myself to try and work out what throws this bad request (400)
error when filebrowser-safe is installed and when MEDIA_ROOT is set to non
''. I finally (through blood sweat and tears), worked out that it comes
from the safe_join function of the django-storages s3boto.py. Because I
Just another note: if filebrowser-safe is uninstalled this bad request 400
does not occur, regardless if MEDIA_ROOT is set to some local fs, or empty,
so I guess it must be a problem with filebrowser when MEDIA_ROOT is
something other than ' ', and s3 storages being used.
--
You received this
Any thoughts on a fix?
On Wed, Jul 1, 2015 at 3:45 AM, Lee H. popov.gh...@gmail.com wrote:
After killing myself to try and work out what throws this bad request
(400) error when filebrowser-safe is installed and when MEDIA_ROOT is set
to non ''. I finally (through blood sweat and tears),
###
### STORAGE ##
###
# The custom storage just allows definition of different 'locations'
so media goes in media/ static goes in /static
# within the bucket. Otherwise same as S3 boto
There is one other simpler way to get this working
MEDIA_ROOT = ''# stops django throwing bad request 400 in admin
when looking at blogpost detail
then thumbnails will attempt to temporarily write to the local filesystem
in the dir 'uploads' relative the point of execuation, so if
