Opened 12 years ago
Closed 11 years ago
#601 closed enhancement (fixed)
Increase the max tag length limit
Reported by: | warp | Owned by: | NattilyPidgin |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | programming | Keywords: | sprint, bitesized, review |
Cc: | Parent Tickets: |
Description
When importing data from flickr some months ago I hit the length limit for tags in MediaGoblin, I assume this limit is still in place.
The limit should be (at least) 255 characters, as this is the limit flickr uses. It doesn't seem to be documented anywhere, but submitting a 4096 length to flickr resulted in that tag being truncated to 255 characters.
Change History (7)
follow-up: 2 comment:1 by , 12 years ago
Keywords: | sprint biresized added |
---|
comment:2 by , 12 years ago
Keywords: | bitesized added; biresized removed |
---|
Replying to cwebber:
This would be a fairly easy task for a newcomer. Marking it bitesized and for the sprint!
That says biresized. :P I'll fix it.
comment:3 by , 11 years ago
I would love to take this on!
My first question is, is this possibly only one line? I just changed line 35 in mediagoblin/config_spec.ini and it works on my lazyserver
...seems too simple? I guess that's what sprint means?
comment:4 by , 11 years ago
Heya... wow you're right, it's just that one line! I thought it would be much more complex, needing a migration.
comment:5 by , 11 years ago
Here's my 'solution'
https://gitorious.org/~npigeon/mediagoblin/npigeons-mediagoblin/commits/ticket-601
I believe that's all!
comment:6 by , 11 years ago
Keywords: | review added |
---|---|
Owner: | set to |
Status: | new → assigned |
comment:7 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Great! Merged! Thanks :)
Yeah, the only complaint I have about this: in the future, please wrap your commit messages at column 80... it makes it a lot easier to read! :)
Good work!
This would be a fairly easy task for a newcomer. Marking it bitesized and for the sprint!