Error loading template: 'crispy_forms_tags' is not a registered tag library about django-sass-processor

[jrief]

Then presumably in one of your templates you are using a templatetag named crispy_forms_tags.

If its so, please close.

[bxm156]

I had the same problem too, the django rest framework includes templates that perhaps use it, even though my project never used them.

[jrief]

which version of DRF? I currently using 3.1.3 and do not encounter these problems.

We (including @franksmit) use the following:

Django==1.9.2
django-sass-processor==0.3.4
djangorestframework==3.3.2
libsass==0.10.1

[jrief]

ok
In DRF 3.1.3 the templatetag crispy_forms_tags is not used. This seems to haven been added later to the file
rest_framework/templates/rest_framework/filters/django_filter_crispyforms.html

So what can we do?

• you add crispyforms to your project
• we ask Tom Christie to remove that dependency :)
• someone adds an option, say --ignore-template-errors to the command compilescss

the latter approach is presumably the more future-proof

I'd say the latter as well

[jrief]

Just a question, from looking at the code there should only be an error message. The compilation step should not abort. Or is this different in your environment?

It still works indeed. It's just not very pretty 😉

[jrief]

I just added a check on the verbosity. If its 0 no warnings are generated.
Please checkout from GitHub and test, it then will be part of 0.3.5

Yay works great!

[dszmaj]

@jrief exactly this breaks my sass routine, when crispy-forms are added to my project it just works

unfortunately not as intended... 'sass_src' pointing to scss in static folder serves just precompiled css, if that css is deleted it doesn't compile on runtime, SASS_PROCESSOR_ENABLED is set to DEBUG value (True), SASS_PROCESSOR_AUTO_INCLUDE = False, no other settings, manage command works good after crispy forms addition

django 1.9
python 3.5