Skip to content

Workaround for https://github.com/SmileyChris/easy-thumbnails/issues/388#414

Open
zsoobhan wants to merge 1 commit intoSmileyChris:masterfrom
pancentric:fix__long_filenames_388
Open

Workaround for https://github.com/SmileyChris/easy-thumbnails/issues/388#414
zsoobhan wants to merge 1 commit intoSmileyChris:masterfrom
pancentric:fix__long_filenames_388

Conversation

@zsoobhan
Copy link

@zsoobhan zsoobhan commented Jul 6, 2016

This is a workaround for my use case given the processors being used in my project were increasing the filename lengths to beyond 255 characters.

I separately added a small bit of .js to check for the length of file names when they are originally uploaded since the files being thumbnailed were uploaded by end users.

Changes the max_length on the models.File.name from 255 to 1023
Adds:

  • django migration
  • south migration

Changes the max_length on the File.name from 255 to 1023
Adds:
  - django migration
  - south migration
@aurimukas
Copy link

Hey!
I have exactly same problem.. and I've done exactly same thing (in my local/dev machine).. still I was thinking that using hashed names should be a cleaner solution (for me). the problem is that I've tried to define a different namer function still Thumbnails are being generated with a default namer function.. does anyone had this problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants