Drupal theming has a trick to exclude CSS file of a base theme in a subtheme. You simply include the filenames of CSS files to exclude it in your info file. Then, if your subtheme doesn't have these files, the files are "overriden" to null state, meaning they are not included on the page.
With AdvAgg these files are still referenced in the page source, probably causing lots of issues (disabled page cache, empty aggregates). But I'm sure this is issue with AdvAgg because when I view the page with ?advagg=0 these files are not included.
Update
I forgot to add this happens not with the base theme CSS files only, but with any overriden CSS files (including core modules').
Comments
Comment #1
crea commentedBasically AdvAgg seems to not completely replicate drupal_get_css() logics.
Comment #2
crea commentedThis is major, if not critical problem. For me it caused page cache to completely stop working, and caused different strange problems - empty aggregate files, broken CSS links.
Comment #3
crea commentedI've managed to fix the problem for myself by clearing all non-existant files from the
$vars['css']in my own page preprocess hook.Comment #4
crea commentedComment #5
crea commentedComment #6
crea commentedLooks like we also have to clean the advagg_files table from the missing files.
Comment #7
nikhilsukul commentedIs this patch works? We are facing problems as when advagg css file is requested we get 404 error sometimes, not always. Is this a related issue as discussed here: http://drupal.org/node/1681712?
Comment #8
mikeytown2 commentedThanks for the patch it has been committed :)
Open to idea on how to clean up the advagg_files table.
Comment #9.0
(not verified) commentedupdate