{"comment":{"created_at":"2011-10-11T02:24:12Z","body":"The south-related changes regarding the south_field_triple are still relevant, but seem to be broken against the latest version of south; and I'm not convinced about \"generates slugs '', '-2', '-3'\" being fixed, even with my patches.  Aside from those, the patches no longer apply to master.  I'll close this pull request, regenerate the south-related patches against master, and submit a new pull request with those changes (not sure if there's a way to edit the \"attached commits\"...).","updated_at":"2011-10-11T02:24:12Z","url":"https://api.github.com/repos/django-extensions/django-extensions/issues/comments/2354718","id":2354718,"user":{"avatar_url":"https://secure.gravatar.com/avatar/d0d81c25265918acc35d089c7098276f?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/eternicode","id":324189,"login":"eternicode"}},"action":"created","issue":{"number":40,"created_at":"2010-10-14T15:48:56Z","pull_request":{"diff_url":"https://github.com/django-extensions/django-extensions/pull/40.diff","patch_url":"https://github.com/django-extensions/django-extensions/pull/40.patch","html_url":"https://github.com/django-extensions/django-extensions/pull/40"},"body":"When adding an AutoSlugField through a South migration, the easiest way to get the slugs automatically generated for existing objects seems to be to manually save all instances post-migration (this can be done through South's ran_migration and post_migration signals, or in the migration file itself).\r\n\r\nWhen the field-adding migration is run and the models saved, though, the current form of ASF doesn't take an empty string into account, and generates slugs '', '-2', '-3', etc.  I believe the same would happen with null values ('None', 'None-2', 'None-3', etc).\r\n\r\nI've fixed the south triplet to add all the extra `__init__` options to the migration, and I've added two more conditions for force-overwriting the value: field is not-null and value is None, and field cannot be an empty string (a new \"empty\" option was also added to control this), but is.\r\n\r\nThese changes cause the desired behavior in the migration.","comments":2,"title":"AutoSlugField enhancenments","updated_at":"2011-10-11T02:24:12Z","url":"https://api.github.com/repos/django-extensions/django-extensions/issues/40","id":362553,"assignee":null,"milestone":null,"closed_at":"2011-10-11T02:24:12Z","user":{"avatar_url":"https://secure.gravatar.com/avatar/d0d81c25265918acc35d089c7098276f?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/eternicode","id":324189,"login":"eternicode"},"html_url":"https://github.com/django-extensions/django-extensions/issues/40","labels":[],"state":"closed"},"legacy":{"issue_id":362553,"comment_id":2354718}}