Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert "Removed useless code, two GFK to one model don't work anyways…"
This reverts commit 188182b.
- Loading branch information
20a8063
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the reason for reverting commit 188182b? After reverting, deletion of tagged item in admin causes
AttributeError: 'MyCustomTaggedItem' object has no attribute '+1'.
I tested this on Django Version: 1.5.5
With version 0.11 it works fine.
20a8063
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vici: Can you please open a issue with full traceback? The reason was that it would fail on 1.4 and 1.5 if you had more than one relation https://travis-ci.org/alex/django-taggit/builds/14516600
20a8063
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although, technically I just should forbid two generic taggable relations -- but this seemed like the easier way out; patches + test welcome
20a8063
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@viciu: Can you confirm that acbbba8 fixes this for you?
20a8063
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@apollo13: Thanks! I confirm, after your last commit this works for me. As suggested, I've created #172 for the reference.
20a8063
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm getting this same problem for Django 1.6. Can anyone confirm whether or not this is a problem for them as well?
20a8063
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@konrad1234: have you tried just released Django 1.6.1?
20a8063
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just updated but it didn't fix the problem.
20a8063
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You have to use the develop branch till I got a new release…
20a8063
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, thanks! That commit works for Django 1.6.1.