You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using django-pipeline 1.1.25 to generate compressed css and js to STATIC_ROOT along with python manage. py collectstatic --link (django 1.3.1) will cause an infinite loop with no errors when rendering a template with {% compressed_js %} or {% compressed_css %} if new css or js needs to be generated. This issue will be fixed with the addition of the --clear option to collectstatic in django 1.4 ( https://code.djangoproject.com/changeset/16509)
In the meantime the solution is to use PIPELINE_AUTO = False, delete your generated css and js files before running
python manage.py collectstatic --link and then run python manage.py synccompress to regenerate your compressed css and js.
I'm just reporting this form information purposes really, because it took me a while to debug so could possibly help others who are scratching their heads in a similar situation.
The text was updated successfully, but these errors were encountered:
Using django-pipeline 1.1.25 to generate compressed css and js to STATIC_ROOT along with python manage. py collectstatic --link (django 1.3.1) will cause an infinite loop with no errors when rendering a template with {% compressed_js %} or {% compressed_css %} if new css or js needs to be generated. This issue will be fixed with the addition of the --clear option to collectstatic in django 1.4 ( https://code.djangoproject.com/changeset/16509)
In the meantime the solution is to use PIPELINE_AUTO = False, delete your generated css and js files before running
python manage.py collectstatic --link and then run python manage.py synccompress to regenerate your compressed css and js.
I'm just reporting this form information purposes really, because it took me a while to debug so could possibly help others who are scratching their heads in a similar situation.
The text was updated successfully, but these errors were encountered: