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
Issues after upgrading #120
Comments
I think I may have just ran into the same (or a related) problem. For me, it seems the problem stems from the name change of the Changing Out of curiosity, why was the name of this setting changed? |
Unfortunately this does not change anything for me. Setting COMPRESS_ENABLED/COMPRESS or removing it from settings doesn't change a thing. Only removing (commenting) COMPRESS_PRECOMPILERS works. |
I can confirm this. I just migrated from django-mediagenerator. As @23doors points out, commenting COMPRESS_PRECOMPILERS is needed to show all css links. If COMPRESS_PRECOMPILERS is present, it just shows the first defined css in the block. |
Here's a patch: https://gist.github.com/1218346 CompressorNode.debug_mode just checks for COMPRESS_DEBUG_TOGGLE, and my guess is that it should first check for settings.DEBUG, based on the method name :) I'm not sure if that's what you intended to do with debug_mode. |
@23doors, we had the exact same thing happen. The issue results from a great new feature in 1.0 -- precompilers being applied to Fixed in our fork here: https://github.com/threepress/django_compressor/commit/f94c05e8930d793a9383d8f0170e50960fcc4570 |
I think this is related to #119, which I just pushed a fix for, please try it out. |
That seems to fix it for me. |
I take that back -- I still had COMPRESS_PRECOMPILERS commented out. The patch for #119 does not fix this for me; my patch linked above does. I'll try to get a regression test written this evening. |
Okay, thanks, that'd be appreciated. |
Any progress on tests? |
Sorry, have been quite sidetracked. Hoping to push something this weekend. |
This looks like it's related to the issue I posted before about the CSS. #103 |
I can confirm that the patch https://github.com/threepress/django_compressor/commit/f94c05e8930d793a9383d8f0170e50960fcc4570 fixes the issue of missing css links for COMPRESS_ENABLED=False and non-empty COMPRESS_PRECOMPILERS. Precompilers are still executed when necessary and the rest of css links goes through as expected. Also please note that this issue is specific only to CssCompressor. JsCompressor is unaffected. |
Did you test it with DEBUG = True? |
I'm sorry but I can't reproduce this, closing as long there isn't an actual test case proofing this issue. |
@jezdez This issue occurs when DEBUG = True (so COMPRESS_ENABLED=False) and COMPRESS_PRECOMPILERS are not empty (I guess it does some processing that should only be done when COMPRESS_ENABLED is True). https://github.com/threepress/django_compressor/commit/f94c05e8930d793a9383d8f0170e50960fcc4570 fixes this. |
Scratch that. I did some tests with memcached and s3. Eventually memcached was storing some wrong cache values for me. Commit above seems to be working. |
I can confirm that the issue described by 23doors is still exists in 1.1. I have created a pullrequest #194 that fixes this (tested in a mixed css/less project) based on thresspress original fix. |
…as a blocker bug when using less: django-compressor/django-compressor#120)
After upgrading django_compressor==0.9.2 to newest django_compressor==1.0.1 via pip I am experiencing issues with css compression.
This block previously worked normally, right now with both DEBUG True and DEBUG False only first css is displayed.
I can remove first css (reset) from the block and then only second one (text) is used.
I found that when I disable COMPRESS_PRECOMPILERS it all works.
My COMPRESS_PRECOMPILERS is pretty straightforward and works with previous version:
COMPRESS_PRECOMPILERS = (
('text/coffeescript', 'coffee --compile --stdio'),
('text/less', 'lessc {infile} {outfile}'),
)
The text was updated successfully, but these errors were encountered: