#1296 closed defect (fixed)
[patch] Allow SlugFields longer than 50
| Reported by: | anonymous | Owned by: | Adrian Holovaty |
|---|---|---|---|
| Component: | Metasystem | Version: | magic-removal |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I ran in to the hard 50 character SlugField limit while importing my wordpress blog entries to Django. While slugs longer than 50 are probably not desirable, there may be some cases (such as this) where they are required. I've patched trunk as of [2185] to default to a maxlength of 50 but allow that value to be overridden.
It works perfectly for me on Postgres, but it should behave just fine on the other backends too.
I haven't checked out magic-removal yet but can apply these changes there too if that will help.
Attachments (1)
Change History (5)
by , 18 years ago
| Attachment: | slugfield.patch added |
|---|
comment:2 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:3 by , 18 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
| Version: | SVN → magic-removal |
The changes to fields.py were never merged into magic-removal; it still has a mandatory maxlength=50. Trivial one-line fix:
kwargs['maxlength'] = kwargs.get('maxlength', 50)
comment:4 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Note:
See TracTickets
for help on using tickets.
Patch to allow SlugFields with maxlength greater than 50