django-cloudinary-storage does not anticipate Windows paths

[klis87]

django-cloudinary-storage does not anticipate Windows paths

[tundebabzy]

Here are snapshots of the error.

By default, zinnia uploads to a directory named 'uploads' concatenated with the year, month and day the image was saved hence in this particular case - 'uploads\zinnia\2017\01\11'.

Let me know if you need any more information.

[klis87]

I will check it on my windows system soon, it should work right now as I intended this package to work on Windows as well, thanks for letting me know, I will try to fix this in the following days.

[klis87]

By the way, I would like to make sure, by path\to\some\image\image.jpg you mean that this is not actual path to image.jpg, but it is the file name, right?

[tundebabzy]

Yes. This is just the file name.

[klis87]

Thank you for your commits' references.

I am just wondering about one thing, which I am missing. Why a file with a filename like path\to\some\image\image.jpg is created in the first place? Could you please provide me a sample of your Django model/view code, when this situation could arise, so I could understand this issue better? Unless path\to\some\image\image.jpg is just the hardcoded file name?

[tundebabzy]

I'm using django-zinnia for the project. With all default settings, uploading a picture from the zinnia app fails when I'm working on a windows machine. After investigating, I discovered that the name of the image django-cloudinary-storage was receiving is in the 'file path form'. I'm presently on ubuntu but I'll reproduce the issue on my windows machine shortly and show the full stack trace

[klis87]

Thank you for the explanation, now everything is clear, I will test it myself in the evening on Windows machine, accept the merge request and upload new version to pypi.

[tundebabzy]

That will be nice. Thanks.

[klis87]

Thank you for your pull request. I added 1 comment to it, please review it, thanks in advance.