Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
make new release based on -dev?
deprecate and suggest users to switch to advagg?
Comment | File | Size | Author |
---|---|---|---|
#6 | css_gzip.info | 192 bytes | helltae |
#6 | css_gzip.zip | 11.69 KB | helltae |
Comments
Comment #1
mikeytown2 CreditAttribution: mikeytown2 commentedThe diff between 1.3 and dev is very minor
http://drupalcode.org/project/css_gzip.git/shortlog/refs/heads/6.x-1.x
I should deprecate and suggest users to switch to advagg.
Comment #2
mikeytown2 CreditAttribution: mikeytown2 commentedComment #3
Anonymous (not verified) CreditAttribution: Anonymous commentedMikeytown2,
Considering 5,300+ people use this module, wouldn't it be better to use another option to "deprecate" than than flagging it as unsupported and then having all 5,300+ of those sites push off security update emails to their owners?
Comment #4
mikeytown2 CreditAttribution: mikeytown2 commentedWhats a better way to do it?
Comment #5
Anonymous (not verified) CreditAttribution: Anonymous commentedHmm, I'm not sure exactly. I saw this happen with the HTML Mail module a little while ago when they flagged it as unsupported and then it shot out a security notice (and some people were upset). The maintainer then did something else that took off the red security flag and just put up a notice about it not being actively supported/maintained anymore.
I personally use the update_advanced module to turn off notices for anything that happens to do this now...
Comment #6
helltae CreditAttribution: helltae commented+1
I just had to delete advagg because some modules don't work (as ckeditor) and damages some code (for drupal6 i didn't test on 7)
so i delete code on css_gzip.info when it says:
then it don't check if there is a new version.
I attach the info file and css_gzip folder (zipped) v.6.x-1.3
If any knows a better way tell us!!
Comment #7
mikeytown2 CreditAttribution: mikeytown2 commentedI've marked this back as supported even though it is not... Hopefully people can migrate over eventually.
@helltae
Can you provide me with more details as to why advagg didn't work in your case?
What do you mean by damages code?
Can you provide more details about ckeditor? Using WYSIWYG module with ckeditor plugin or the ckeditor module.
Are you using a async JS loader (like LABjs, HeadJS)?
Comment #8
helltae CreditAttribution: helltae commentedIt broke some css code of my theme (little but some)
The CKEditor module doesn't load at all for me. I tried all combinations, disabling all except advagg and only comes alive when advagg was disabled. Let me check about LABjs...
wow i just test on localhost, yes i have LABjs (no HeadJS). i just enabled advagg disabled LABjs and ckeditor comes alive.
As advagg claims:
i didn't check it before :S sorry! I will test more about css code this week, but it seems to work well without LABjs. why it's show as fully compatible if didn't!!! :S
Comment #9
mikeytown2 CreditAttribution: mikeytown2 commented