Admin and API browser fails for views without a filter_class

[mcastle]

The JSON browser does work though. It seems crispy forms breaks because it's expecting a filter form even when there is no filter_class set on a given view.

VariableDoesNotExist at /api/users/

Failed lookup for key [form] in u'None'

Template error:
In template /Users/user/virtualenvs/ddrsite/lib/python2.7/site-packages/rest_framework/templates/rest_framework/filters/django_filter_crispyforms.html, error at line 5
   (Could not get exception message)

   1 : {% load crispy_forms_tags %}
   2 : {% load i18n %}
   3 : 
   4 : <h2>{% trans "Field filters" %}</h2>
   5 :  {% crispy filter.form %}

[jpadilla]

Ugh! Yeah that's definitely what I thought might happen with #3560. @mcastle can you confirm this is happening with the just released 3.3.1?

Update: Specifically talking about this comment on #3560.

[mcastle]

Yep, this happened with 3.3.1.

[spout]

Same for me with 3.3.1, upgraded for #3560

[jpadilla]

Thanks for confirming. So I think what should probably be happening here is that if there's no filter class the filter backend's to_html() returns None. It'd then be skipped here.