On Fri, Dec 11, 2009 at 10:13 AM, Abel Deuring
<email address hidden>wrote:
> Right, that's the same error. But I'd like to know _why_ lfa.content is
> None. If this is to be expected, i.e., if the affected records had
> lfa.content.deleted == True before the schema change, then the affected
> code must be fixed; otherwise, I'd like to know at first, what else
> caused lfa.content to become None.
>
>
Right. It is certainly old content - according to:
the release in question is over 3 years old (from dapper). I've grepped
('\.content = None') and like you can't see any other points where the
content is explicitly set to None, so I'll chase up the deleted being set to
True - thanks for the tip Abel!
On Fri, Dec 11, 2009 at 10:13 AM, Abel Deuring
<email address hidden>wrote:
> Right, that's the same error. But I'd like to know _why_ lfa.content is
> None. If this is to be expected, i.e., if the affected records had
> lfa.content.deleted == True before the schema change, then the affected
> code must be fixed; otherwise, I'd like to know at first, what else
> caused lfa.content to become None.
>
>
Right. It is certainly old content - according to:
https:/ /edge.launchpad .net/ubuntu/ +source/ sysvinit
the release in question is over 3 years old (from dapper). I've grepped
('\.content = None') and like you can't see any other points where the
content is explicitly set to None, so I'll chase up the deleted being set to
True - thanks for the tip Abel!