Open GoogleCodeExporter opened 8 years ago
Is this issue maybe related to this:
http://code.djangoproject.com/ticket/12397
The essence of which is that the media path begins with "/".
Original comment by ele....@gmail.com
on 6 Jan 2010 at 9:41
I don't think these issues are related because it works well with latin
symbols. So
the problem is connected with decoding.
Original comment by pakhomov...@yandex.ru
on 8 Jan 2010 at 8:02
I just want to store file somewhere in my root path. I guess I should customer
the
save function myself.
Original comment by wooodyhu...@gmail.com
on 11 Apr 2010 at 3:30
I can confirm that having files with non-latin characters filenames in a zip
file throws the error. Test case is to upload the attached "umlauteinside.zip"
file as a gallery. Working case is the same image file in a zip named with only
latin characters ("no-umlaute.zip"). Both zips were generated with 7-zip under
Win7 64bit.
Although I can't reproduce it now on a Win7-64bit development host, I have seen
this even worse behavior on a Linux host: You can't browse the photos in the
admin afterwards, it throws
Caught an exception while rendering: ('ascii', 'grunwei\xc3\x9f', 7, 8,
'ordinal not in range(128)')
when visiting /admin/photologue/photo/. Real bad. This kills the site and needs
manual DB intervention to clear out (just delete the offending image entry in
table photologue_photo).
Original comment by philipp....@googlemail.com
on 19 Jul 2010 at 9:54
Attachments:
[deleted comment]
[deleted comment]
I coded a test that tries to create a GalleryUpload-object for each of the two
ZIP-Files above (encoded inside the code) and fails with the umlauteinside.zip
one.
Also included is a solution that sanitized filenames inside the ZIP-file before
writing them to disk.
This patch should apply cleanly using patch -p2 to django-photologue-2.2.
Original comment by philipp....@googlemail.com
on 19 Jul 2010 at 4:50
Attachments:
Here's the proper way to sanitize paths ...
http://code.google.com/p/django-photologue/issues/detail?id=119#c6
Original comment by hainea...@gmail.com
on 8 Feb 2011 at 7:04
Original issue reported on code.google.com by
pakhomov...@yandex.ru
on 2 Dec 2009 at 10:25