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.
I can see some aggregated css files that are empty.
Is this intentional?
Comments
Comment #1
mikeytown2 CreditAttribution: mikeytown2 commentedGenerally no, it is not intentional. Can you look up in your database what files are included in that bundle?
Modify this query to see what files are included.
Another thing that might be helpful is adding
?advagg-debug=1
to the end of the URL and attaching the watchdog debug output as a file in this issue. You need the "bypass advanced aggregation" permission for this to work.Also see #1181928: Optimize output from css_emimage
Comment #2
mikeytown2 CreditAttribution: mikeytown2 commentedClosing this issue as I've gotten no feed back on it.
Comment #3
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedI've now been able to investigate this. This happens if the CSS file is itself empty. Maybe include a check for this?
I agree that the file should not be empty in the first place.
Comment #4
loopduplicateDrupal 7 query:
Comment #5
Diane Bryan CreditAttribution: Diane Bryan commentedA use-case for an empty css file: AdaptiveTheme includes media breakpoint css files, and requires that they always be left active, even if completely empty. Thus, the site builder can decide whether to have overlapping media queries or stacked queries. So, you don't want to have your advanced aggregation removing them, or you'll probably break the theme.
Comment #6
mikeytown2 CreditAttribution: mikeytown2 commentedNo good fix for this.
Marking as closed (not fixed, reopen with patch).