erikask
unread,Dec 12, 2012, 11:14:50 AM12/12/12Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to djangofi...@googlegroups.com
Hello
I've got a weird issue that seems close to impossible to track down the source of. I'm using django 1.3.6, filebrowser, 3.4.3, grappelli 2.3.9, everything works except for file uploads of binary files. I can upload any text file, seemingly irregardless of extension, so far I've tried everything from .txt to .cc to no extension. However any file that is binary fails, with the annoying error message "Failed", no other info. From apache logs i found that uploading caused a 500 error, unknown in what step of the process.
This error also only occurs on the production server, however file upload using djangos standard file upload fields works fine, both binary and others, so the apache 2 clearly accepts file-uploads. On my laptop (dev- machine) this problem doesn't exist. I've tried to reproduce it but no success.
Since this seems to be machine specific I of course don't expect anyone to solve it of the bat, but if anyone can provide info on how filebrowser uploads differ from standard file-field uploads, a more step by step on the underlying processess or anything else that could guide my search to track it down I'd be grateful.
All other functionality works, creating directories etc, manually placing iamges and pdfs in the structure I can browse and download. ./manage.py test filebrowser returns "ok" (and a runtime).
p.s.
Updating filebrowser and hence django is unfortunately not an option.
d.s.