-
Notifications
You must be signed in to change notification settings - Fork 28
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
django 1.3 STATIC_URL #28
Comments
I made a pull request regarding the media url issue earlier. You can have a look here #27 |
Works perfect. Thanks! |
i dont know about you guys, but i store site-wide sass files in STATIC_ROOT and now these files are not found by django-css. They are however served perfectly by django static files. django-css needs to considder files in STATIC_ROOT before any files in STATICFILES_DIRS |
Django-css's copy of django-compressor is old in general. Django-compressor took care of this in recent versions |
is anyone merging django-compressor into django-css regularly/semi-regularly? |
You might wanna take a look at https://github.com/jezdez/django_compressor/. It now has a precompiler filter with which you can add support for external commands (sass, coffescript etc). Works well in my first test and have support for Django 1.3 / staticfiles. |
Yes, it works really well in my tests. Except one small problem where I can't get it to find my static files in my app. Other than that there's 0 problems. :) |
I tracked down the bug I spoke of above here, and have the fix. |
Django 1.3 introduces STATIC_URL as a standard approach for app static files.
So from now on there are two paths for not dynamic files:
MEDIA_URL - more like uploaded files
STATIC_URL - statics delivered with app
At this point there are two issues with django-css.
I guess it should be enough jus to remove templatetags/compress.py lines:
if 'MEDIA_URL' in context:
media_url = context['MEDIA_URL']
else:
It might be useful to either document this limitation or get real static file path while in development mode (runserver)
The text was updated successfully, but these errors were encountered: