Context Navigation

Changes between Initial Version and Version 1 of Ticket #11154, comment 37

initial	v1
9	9	i.e. ([https://github.com/alex/django-taggit django-taggit]) If you defined a `TaggableManager()` (uses `GenericForeignKey` internally) on a proxy model then all tags will be associated with the concrete model `ContentType` in the db. If we release `follow_proxy=False` as default then the generic relation between the proxy model and the tags will be broken since they were never associated with the proxy's ct.
10	10
11		We can either break the API to unite them or offer the user to ''opt-in'' in order to maintain backward compatibility. But this whole ~~issue is~~ bigger then the ticket itself. We should maybe open another issue to fix the `ContentType` proxy issue that blocks this one and then, once it's fixed, use the new hooks to fix this one with:
	11	We can either break the API to unite them or offer the user to ''opt-in'' in order to maintain backward compatibility. But this whole discussion is getting bigger then the ticket itself. We should maybe open another issue to fix the `ContentType` proxy issue that blocks this one and then, once it's fixed, use the new hooks to fix this one with:
12	12
13	13	{{{