Postponed (maintainer needs more info)
Project:
Aggregate cache
Version:
7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
31 Jan 2013 at 10:49 UTC
Updated:
22 Aug 2017 at 08:43 UTC
Jump to comment: Most recent
Comments
Comment #1
IWasBornToWin commentedAny way you could answer this "critcial" issue? Makes me want to uninstall this module immediately.
Comment #2
warmth commentedI disabled it!
Comment #3
catchThis needs more information:
- are clean URLs enabled?
- are you seeing filenames rendered in the HTML document?
- what happens with the request for the aggregate files if so - 404? 403? 500?
Comment #4
Ivan_Dagreat commentedI had this same issue. But its not just css, its js also. Every aggregated file returns a 404.
- Clean URLs are on
- Filenames Look Normal (js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js)
Comment #5
nwom commentedI'm getting the same issue, but I'm wondering if it's a Radix Bootstrap/Bootswatch theme incompatibility.
Comment #6
aaron.ferris commentedSeeing the same issue:
- are clean URLs enabled? Yes
- are you seeing filenames rendered in the HTML document? Yes
- what happens with the request for the aggregate files if so - 404? 403? 500? - 404
Digging into this a little, it appears, at least in my implementation that agrcache_generate_aggregate() is never actually being called, so the files aren't created, hence the 404.
In my case it was a fast_404 setting causing this (even with '404_fast_paths_exclude' configured as per the module instructions):
$conf['fast_404_exts'] = '/\.(png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i';For anyone else noticing the same issue, it would be worth checking these settings in settings.php or wherever they're set.