Workaround for https://github.com/SmileyChris/easy-thumbnails/issues/388 #414
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changes the max_length on the File.name from 255 to 1023 Adds: - django migration - south migration
zsoobhan
force-pushed
the
fix__long_filenames_388
branch
from
39ed16e
to
f0a9b85
Compare
|
Hey! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.namefrom 255 to 1023Adds: