What may be the case is your template is trying to access ``{{
result.object }}`` on the search result of a deleted database record.
Haystack does not automatically handle deletions from the DB
propagating to the index. The quick fix is to run either ``./manage.py
update_index --remove`` (if you need the index to stay in place & can
spare the RAM) or ``./manage.py rebuild_index`` (which will wipe out
the whole index first & rebuild it over time).
A longer term solution is to either move to ``RealTimeSearchIndex``
or a queued solution.
Daniel
> --
> You received this message because you are subscribed to the Google Groups "django-haystack" group.
> To post to this group, send email to django-...@googlegroups.com.
> To unsubscribe from this group, send email to django-haysta...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/django-haystack?hl=en.
>
>