Raphael Gaschignard
Raphael Gaschignard
OK so I narrowed this down to the fact that `TaggableManager` is using a totally custom `contribute_to_class`. In Django's `RelatedField.contribute_to_class` method we have ``` if related_name: related_name = related_name %...
Labelling a bug since we _are_ a `RelatedField` sublcass, so should behave as such when possible.
@thenewguy if you want to take this on, I think the straightforward way would be to just edit one of the existing test models with a related name like what...
I've reached out to Paul on this topic, waiting for a reply
I got no reply from Paul on this one. I just compared the licenses, and everything seems in order for vendoring this in. The licenses are identical except for copyright...
Alright this is vendored in and part of the 1.5.0 release
@glemmaPaul thank you for the initial work! I do hope that the vendoring is to your liking
In your case you might need to set up a custom form field. The easiest way would be to redefine `formfield` on your `TaggableManager` subclass to use some sublcass of...
Yep that definitely makes sense (I tend to add created/updated timestamps on all of my models as a general principle). For now it's easy to create a custom tag class...
Hmm I'm seeing a similar issue on a custom tag thing.... feels like a legit bug here