That change did miss the release. It will be present in RC1.
Christian
On Tue, Oct 10, 2017 at 7:27 AM, Nicolas Ferrari
wrote:
> Hi, the issue is still present in the 3.0.x version.
>
> Regards,
>
> On Monday, October 2, 2017 at 11:11:17 PM UTC+2, Christian Hammond
Hmm, this is beyond bizarre. Note these lines:
if not hasattr(current_object, attr):
raise SearchFieldError("The model '%s' ('%s' -- %s) does not have a
model_attr '%s' (%s)." % (repr(obj), repr(current_object),
current_object.__class__.__name__, attr, hasattr(current_object,
Hi, the issue is still present in the 3.0.x version.
Regards,
On Monday, October 2, 2017 at 11:11:17 PM UTC+2, Christian Hammond wrote:
>
> Hi Ali,
>
> We have a fix for this in our tree
> (commit 23fbc2f28742442835c4c275e81c1ad0cb163ed6), which will be part of
> the next 2.5.x release.
>
>
Here you go...
# encoding: utf-8
from __future__ import unicode_literals
import re
from django.template import Context, loader
from django.utils import datetime_safe, six
from haystack.exceptions import SearchFieldError
from haystack.utils import get_model_ct_tuple
class NOT_PROVIDED: