-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
conflicting template tag with django-debug-toolbar #331
Comments
Ran into this issue too and had to disable debug-toolbar. |
I've determined that if I put debug-toolbar before django-imagekit in INSTALLED_APPS, the error goes away. I think this should be ok since imagekit's compat doesn't actually seem to include any template tags - it's just being included by the imagekit templatetag file. If you want to add debug-toolbar to INSTALLED_APPS in a local.py like I'm doing, you'll need to make sure it's added first instead of last, so something like this will work: Or if you need to add it somewhere that is prior to imagekit, but not first, you could cast INSTALLED_APPS to a list, insert it where you wish, and cast it back to a tuple. |
That makes total sense. If we move that file outside of the templatetags package, it should take care of it. |
Thank you, krisfields! That fixed the issue for me too (after upgrading to Django 1.8). |
same issue in django debug toolbar repo django-commons/django-debug-toolbar#734 |
In As @matthewwithanm suggested we can move our Because I'm not sure where will be the right place to move the What you think about this guys? |
I've made a Pull request with moving the |
I get this error if I have both django-imagekit and django-debug-toolbar installed:
'compat' is not a valid tag library: Template library imagekit.templatetags.compat does not have a variable named 'register'
It looks like both django-imagekit and django-debug-toolbar have a templatetag file named compat.py.
Sorry about posting twice. I was logged in under someone else's account and didn't realize it.
The text was updated successfully, but these errors were encountered: