Re: Content types and interaction with DeferredAttribute models

I have the same problem. It looks like the content types app will return the content type of the original model when asked for one since revision 10523 (see ticket #10738), but that an additional content type is still created. Is the creation of the additional content type necessary? http://code

Content types and interaction with DeferredAttribute models

FYI: Trying to run unittests. Using the .only() method on a queryset causes the content types machinery to find and attempt to use a model with Deferred attributes. This function (with print and verbosity added): def update_contenttypes(app, created_models, verbosity=2, **kwargs): """