> Though the default 500 view has since gone back to a standard Context.
> As Adrian explained in the commit message, this is to avoid having
> context processors in the 500 view raise something that'd result in a
> 500 ;)
Maybe they should use RequestContext and fallback to plain Context on error
> I have created a Field called 'CTField' which will acts like a regular
> foreign key,
> but only fetches things which match the content_type as well.
Is it working with r0.95? I'm getting "OperationalError
table app_model has no column named object_id"
--~--~-~--~~~---
> I have created a Field called 'CTField' which will acts like a regular
> foreign key, but only fetches things which match the content_type as
> well.
>comments = CTField( Comment )
Very nice.
Very +1 on putting this into core.
--~--~-~--~~~---~--~~
You recei
> Does anybody have ideas for examples that would be worthwhile and
> helpful to add to the examples directory?
Using content-type/object fields.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" gro
> http://files.lukeplant.fastmail.fm/public/admin_with_description.png
oops... 500: infernal server error
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
