Raphael Gaschignard

Not sure what we need to do exactly here, I would hope that `models.Manager` would get us this "for free", but seems like it might not. We'll likely need to...

(Sorry for the delay here) I think you need to make sure to have run migrations? Tags rely on the content type table and the like to implement its generic...

We have `Tag`, `TaggedItem` and various models `M`, `N`, `O`, `P`. But we might also have custom tags, and multiple tag managers on `M` or `N`, etc.... it's not very...

Yep, as people have identified this is due to custom tag models using different tables etc. Seems very doable for us to improve this (or at least document some workarounds)

@ggiller-collective no progress has been made on this specific point. Generally if you make a custom tag, you should be able to add that model to the admin like any...

we added `tag_kwargs` at one point in time, but seems like `through_defaults` is the "better" version of that, thank you for pointing this one out!

Reading `through_defaults` more, this is actually a bit more complex, around the through table instead of the tag itself (so both options might still be relevant)

Does this issue only appear when using Django 3 for you? And what version of django taggit are you using? `similar_objects` is some tricky code, so something might be busted...

This change as-is would break backwards compatibility with everyone using this base. After triaging a hundred+ issues, I think a big thing is the custom tag documentation. I'm going to...

this can be solved by using a Custom Tag (or rather, a [custom through model](https://django-taggit.readthedocs.io/en/latest/custom_tagging.html#using-a-custom-tag-or-through-model)). With custom tags you have loads of flexibility on your data store, so you don't...