I've successfully gotten AdvAgg working on 3 Drupal 6.22 sites, but, keep getting 'Adv CSS/JS Agg - Asynchronous Mode Set to FALSE' on one site.
I've tried the suggested fixes for Fast 404, Cache clear, IP Address to send all asynchronous requests to: -1, Maintenance mode off, etc. No cigar.
Here's the Asynchronous debug info:
stdClass Object (
[request] => GET /files/advagg_css/css_missing14510339121306523897_0.css HTTP/1.0
Host: example.com
User-Agent: Drupal (+http://drupal.org/)
[data] => 239d
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Page not found - 404</title>
<link type="text/css" rel="stylesheet" media="all" href="/modules/node/node.css?k" />
<link type="text/css" rel="stylesheet" media="all" href="/modules/system/defaults.css?k" />
<link type="text/css" rel="stylesheet" media="all" href="/modules/system/system.css?k" />
<link type="text/css" rel="stylesheet" media="all" href="/modules/system/system-menus.css?k" />
<link type="text/css" rel="stylesheet" media="all" href="/modules/user/user.css?k" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/cck/theme/content-module.css?k" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/ctools/css/ctools.css?k" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/date/date.css?k" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/dhtml_menu/dhtml_menu.css?k" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/filefield/filefield.css?k" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/jquerymenu/jquerymenu.css?k" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/logintoboggan/logintoboggan.css?k" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/cck/modules/fieldgroup/fieldgroup.css?k" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/views/css/views.css?k" />
<link type="text/css" rel="stylesheet" media="all" href="/files/color/garland-c634f946/style.css?k" />
<link type="text/css" rel="stylesheet" media="print" href="/themes/garland/print.css?k" />
<script type="text/javascript" src="/sites/all/modules/jquery_update/replace/jquery.js?k"></script>
<script type="text/javascript" src="/misc/drupal.js?k"></script>
<script type="text/javascript" src="/sites/all/modules/adsense/contrib/adsense_click/adsense_click.js?k"></script>
<script type="text/javascript" src="/sites/all/modules/dhtml_menu/dhtml_menu.js?k"></script>
<script type="text/javascript" src="/sites/all/modules/google_analytics/googleanalytics.js?k"></script>
<script type="text/javascript" src="/sites/all/modules/jquerymenu/jquerymenu.js?k"></script>
<script type="text/javascript">
<!--//--><![CDATA[//><!--
jQuery.extend(Drupal.settings, { "basePath": "/", "dhtmlMenu": [ "doubleclick", "clone" ], "googleanalytics": { "trackOutgoing": 1, "trackMailto": 1, "trackDownload": 1, "trackDownloadExtensions": "7z|aac|arc|arj|asf|asx|avi|bin|csv|doc|exe|flv|gif|gz|gzip|hqx|jar|jpe?g|js|mp(2|3|4|e?g)|mov(ie)?|msi|msp|pdf|phps|png|ppt|qtm?|ra(m|r)?|sea|sit|tar|tgz|torrent|txt|wav|wma|wmv|wpd|xls|xml|z|zip" } });
//--><!]]>
</script>
<script type="text/javascript">
<!--//--><![CDATA[//><!--
window.google_analytics_uacct = "UA-409846-31";
//--><!]]>
</script>
<!--[if lt IE 7]>
<link type="text/css" rel="stylesheet" media="all" href="/themes/garland/fix-ie.css" /> <![endif]-->
</head>
<body>
<!-- Layout -->
<div id="header-region" class="clear-block"></div>
<div id="wrapper">
<div id="container" class="clear-block">
<div id="header">
<div id="logo-floater">
<h1><a href="/" title=".::."><img src="/images/logo.png" alt=".::." id="logo" /><span>xxx</span> .::. </a></h1> </div>
<ul class="links primary-links"><li class="menu-136 first"><a href="/about.html">About</a></li>
<li class="menu-135 last"><a href="/services.html">Services</a></li>
</ul>
</div> <!-- /header -->
<div id="center"><div id="squeeze"><div class="right-corner"><div class="left-corner">
<div class="breadcrumb"><a href="/">Home</a></div> <h2>Page not found - 404</h2> <div class="clear-block">
<div id="node-8" class="node">
<div class="content clear-block">
<!-- google_ad_section_start --><h2 id="pageName">Oops, we couldn't find that page...</h2>
<div class="feature">
<p>... it may have moved, or may be listed under a new name or if you typed in the name, perhaps there was a typo.<br />
<br />
Please try searching for the page using the Google search form at the bottom of the page. If you still can't find what you are looking for, send an email to the webmaster. Let us know and we'll work hard to get you the information you want!</p>
</div>
<br />
<!-- input type modified from "q" to "as_q" as per article at: http://www.techmag.biz/google_onsite_search_on_drupal -->
<!-- SiteSearch Google -->
<form method="get" action="http://texas-video.com/sitesearchresults.html" target="_top">
<table border="0" bgcolor="#ffffff">
<tr><td nowrap="nowrap" valign="top" align="left" height="32">
<a href="http://www.google.com/">
<img src="http://www.google.com/logos/Logo_25wht.gif" border="0" alt="Google" align="middle"></img></a>
</td>
<td nowrap="nowrap">
<input type="hidden" name="domains" value="example.com"></input>
<label for="sbi" style="display: none">Enter your search terms</label>
<input type="text" name="as_q" size="60" maxlength="255" value="" id="sbi"></input>
<label for="sbb" style="display: none">Submit search form</label>
<input type="submit" name="sa" value="Search" id="sbb"></input>
</td></tr>
<tr>
<td> </td>
<td nowrap="nowrap">
<table>
<tr>
<td>
<input type="radio" name="sitesearch" value="" id="ss0"></input>
<label for="ss0" title="Search the Web"><font size="-1" color="#000000">Web</font></label></td>
<td>
<input type="radio" name="sitesearch" value="texas-video.com" checked id="ss1"></input>
<label for="ss1" title="Search the example website"><font size="+1" color="#000000">example.com</font></label></td>
</tr>
</table>
<input type="hidden" name="client" value="pub-6051175549824070"></input>
<input type="hidden" name="forid" value="1"></input>
<input type="hidden" name="ie" value="ISO-8859-1"></input>
<input type="hidden" name="oe" value="ISO-8859-1"></input>
<input type="hidden" name="safe" value="active"></input>
<input type="hidden" name="cof" value="GALT:#008000;GL:1;DIV:#336699;VLC:663399;AH:center;BGC:FFFFFF;LBGC:336699;ALC:0000FF;LC:0000FF;T:000000;GFNT:0000FF;GIMP:0000FF;FORID:11"></input>
<input type="hidden" name="hl" value="en"></input>
</td></tr></table>
</form>
<!-- SiteSearch Google -->
<!-- break -->
<!-- google_ad_section_end --> </div>
<div class="clear-block">
<div class="meta">
</div>
</div>
</div>
</div>
<div id="footer">example</div>
</div></div></div></div> <!-- /.left-corner, /.right-corner, /#squeeze, /#center -->
</div> <!-- /container -->
</div>
<!-- /layout -->
<div style="height: 0px; width: 0px;"><a href="http://www.lisapace.com/backstage.php?m=70">telesync</a></div>
<!--[if IE 6]>
<script type="text/javascript">
var IE6UPDATE_OPTIONS = {
icons_path: "http://example.com/sites/all/modules/ie6update/images/",
message: "Internet Explorer is missing updates required to view this site. Click here to update... ",
url: "http://www.microsoft.com/windows/internet-explorer/default.aspx"
}
</script>
<script type="text/javascript" src="http://example.com/sites/all/modules/ie6update/ie6update.js"></script>
<![endif]-->
<script type="text/javascript">
<!--//--><![CDATA[//><!--
var _gaq = _gaq || [];_gaq.push(["_setAccount", "UA-409846-31"]);_gaq.push(["_trackPageview", "/404.html?page=" + document.location.pathname + document.location.search + "&from=" + document.referrer]);(function() {var ga = document.createElement("script");ga.type = "text/javascript";ga.async = true;ga.src = "/files/googleanalytics/ga.js?k";var s = document.getElementsByTagName("script")[0];s.parentNode.insertBefore(ga, s);})();
//--><!]]>
</script>
</body>
</html>
0
[protocol] => HTTP/1.1
[status_message] => Not Found
[headers] => Array (
[Date] => Fri, 27 May 2011 19:18:17 GMT
[Server] => Apache/2.2.15 (Unix) mod_ssl/2.2.15 OpenSSL/0.9.8e-fips-rhel5 DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.13
[X-Powered-By] => PHP/5.2.13
[Set-Cookie] => SESS01dcf23648a9c4e7f4b38aa0a1b143f5=388ef0089313098c0a426500bd5a8a2a; expires=Sun, 19-Jun-2011 22:51:37 GMT; path=/; domain=.videotexan.com
[Expires] => Sun, 19 Nov 1978 05:00:00 GMT
[Last-Modified] => Fri, 27 May 2011 19:18:17 GMT
[Cache-Control] => post-check=0, pre-check=0
[Vary] => Accept-Encoding,User-Agent
[Transfer-Encoding] => chunked
[Content-Type] => text/html; charset=utf-8
)
[error] => Not Found
[code] => 404
[timer] => Array (
[count] => 1
[time] => 2554.49
)
)
Next step?
Note to self: vt.c
| Comment | File | Size | Author |
|---|---|---|---|
| #66 | advagg-1171244-66.patch | 2.26 KB | mikeytown2 |
| #35 | advagg-1171244-33.patch | 1.23 KB | mikeytown2 |
| #33 | advagg-1171244-33.patch | 1.23 KB | mikeytown2 |
| #16 | advagg-1171244-16.patch | 2.82 KB | mikeytown2 |
| #4 | 5-27-2011 11-58-00 PM.png | 25.99 KB | TallDavid |
Comments
Comment #1
mikeytown2 commentedhmmm; this looks like a menu issue. Can you try clearing the menu cache one more time?
If still no go, you will have to hack core and add this to includes/common.inc at the top of the drupal_not_found() function. OR in your case, you can change node/8 (your 404 page) to have the PHP input filter and add this code to the top of it. The debug_backtrace() function will let us know who called drupal_not_found().
Then go to admin/settings/advagg/info, then go to watchdog, get the "advagg-404" entry for
/files/advagg_css/css_missing...and paste it here.Comment #2
TallDavid commentedHere it is! ---->
Comment #3
mikeytown2 commentedTop of the stack is [file] => index.php; means menu_execute_active_handler() was ran. Means your menu cache doesn't have advagg in it yet.
With phpmyadmin what does this give you?
If nothing does this give you anything?
In either case try running this function if your standard drupal cache clear is not working (admin/settings/performance at the bottom press the "Clear cached data" button )
Long story short this appears to be a menu issue.
Comment #4
TallDavid commentedgives the results in the attached file: 5-27-2011 11-58-00 PM.png
gives the results in the attached file: 5-28-2011 12-06-20 AM.png
Clearing the cache via the
function doesn't seem to make any difference.
Comment #5
mikeytown2 commentedSorry but I don't know what to tell you. The correct entry is in the menu_router table. path matches the test url.
files/advagg_css/%
files/advagg_css/css_missing14510339121306523897_0.css
My last recommendation, which is a bad idea to do on a live site is to disable all caching
http://www.garfieldtech.com/blog/drupal-cache-disable
Place this in your settings.php file at the bottom and hit the status page.
This should let me know to a fairly high level of confidence that the cache is not the issue. includes/cache-install.inc for the curious.
Comment #6
TallDavid commentedThis is a head-scratcher. Disabling of all caching (as per garfieldtech.com) makes no difference.
I also tried uninstalling/re-installing AdvAgg as well as updating to this morning's 6.x-1.x-dev code, trying a new theme and a few other things. Nothing makes a difference.
Comment #7
Peter Bowey commentedrefer #8
Are you using Pressflow?
If so, see http://drupal.org/node/1172012 and http://drupal.org/node/1169702 for how I dealt with the problem...
The 'clue' is if you see the following in the async advagg debug status
Comment #8
TallDavid commentedPeter, thanks for the suggestion. No, I am not using Pressflow. So far, 3 Drupal 6.22 sites work fine with AdvAgg and on 2 I can't get past the 'Asynchronous Mode Set to FALSE' problem.
Comment #9
Peter Bowey commentedRefer #8
'Tall David', I cannot see all of your advagg's debug info (above)!
Note: It has 2 parts...
Mine looks like this (in 2 parts):
Part1:
Part 2: (CDN Debug typically)
Hope I am not confusing you.
The 'critical' part is (advagg) seeing both: [1]
<!-- advagg_missing_fast404 -->and [2][X-AdvAgg] => Failed Validation. Wrong PatternHowever, at least you have 'template' for how advagg info 'should' look with a valid async.
I note that your (above) 404 response looks 'strange', as though something else is handling 404's.
Comment #10
Peter Bowey commented'TallDavid', have you compared the advagg debug info data between the working and non-working sites (systems)?
I am sure there is good 'clue' in doing that comparison.
Comment #11
TallDavid commentedPeter, the AdvAgg debug info only has 1 part on my site and that is what was provided in the initial writeup above. I'm not running a CDN, could this be the reason that I'm not seeing a Part 2 like the one you presented? If I misunderstood your suggestion, please let me know. I'm inexperienced in the CSS/JS Aggregation area, but I learn fast.
I attempted to take your suggestion and to compare the AdvAgg async debug info between one of the working and a non-working site, but, the 'Asynchronous debug info' does not exist on the working site (there's nothing to debug since it's working ;-).
I've now encountered a total of 3 sites that work and 3 sites that have the same 'Adv CSS/JS Agg - Asynchronous Mode Set to FALSE' issue. (All on the same server.)
Comment #12
mikeytown2 commentedIn regards to the idea in #1. You checked the location of the watchdog report to make sure it came from the advagg path, correct? If not run #1 again, but with this code; it will only output to watchdog if
/advagg_is in the path.I do plan on using menu_get_item() to help on the status page; will let me know if a menu cache flush is needed; but I haven't written that patch yet.
Comment #13
TallDavid commentedMickeyTown2, thanks for your persistence in troubleshooting this issue.
Yes, when I originally performed the steps in #1, there was an "advagg-404" entry in the watchdog from which I cut-n-pasted. (The entry is still there... this is a very low volume site).
After placing the revised code from #12 in my 404 page (node 8), visiting admin/settings/advagg/info and then going to watchdog, there is no new "advagg-404" entry. There is, however, this entry:
What's next?
[FYI, I've updated a few more sites to Drupal 6.22 and installed AdvAgg after the upgrade. Currently 6 sites are working fine and 3 have problems with 'Adv CSS/JS Agg - Asynchronous Mode Set to FALSE'.]
Comment #14
Peter Bowey commentedRefer #11
TallDavid, the latest advagg *.dev version now has a async. info/debug status window built in. It will always show 'results'. The sample 'result' I sent you is of a correctly working advagg. This may help you!
Looking at #1 state, I see 'possible' issues with 404 handling. Your 404 is 'bypassing' from being processed thru advagg. So no async. check pass - what Mike refers to as the advagg 'menu callback' that should result. Hence Mike's suggestion to 'clear the menu cache'...
It also looks to me as though you have a type of 'search404' process added to your 404 chain?
eg: http://drupal.org/project/search404
and I see this "
<!-- SiteSearch Google -->"I would use the KISS concept to debug :)
Comment #15
mikeytown2 commentedyour not using the CDN module so I doubt my latest fixes for this issue will do anything... but it's worth trying.
#1172012: cdn_file_url_alter's path blacklist by default has admin*. AdvAgg CDN tests on status page not working as a result.
For the sites that do work in comparison to the sites that don't, could you list out what modules are different or if any code is different?
Comment #16
mikeytown2 commented@TallDavid
This patch below has been committed; let me know if you get the 'Flush your caches' warning on the status page.
Comment #17
TallDavid commentedFinal count on 15 sites updated to Dupal 6.22: 12 sites have no problems with AdvAgg. But, I haven't been able to resolve the 'Adv CSS/JS Agg - Asynchronous Mode Set to FALSE' issue on the remaining 3 sites. I've downloaded the latest dev version, but, it's way too late to do any testing tonight. I'll follow-up on the 'morrow.
Comment #18
TallDavid commented@mikeytown2, I've updated the site to the May 31, 2011 version of AdvAgg 6.x-1.x-dev. I'm still getting 'Adv CSS/JS Agg - Asynchronous Mode Set to FALSE' and do not see a 'Flush your caches' warning on the status page.
The 'Asynchronous debug info' now shows:
Comment #19
mikeytown2 commentedDo you mind searching your code base for "The requested URL was not found on this server." That looks like a fast404.
Comment #20
TallDavid commentedThe string "The requested URL was not found on this server." is found on this site in the advagg.module and settings.php files.
Comment #21
Peter Bowey commentedTo #20 (via settings.php grep); that's a fast404
See http://2bits.com/drupal-planet/reducing-server-resource-utilization-busy...
Comment #22
TallDavid commentedPeter, yes, I am aware of this. I've followed the documentation and modified the Fast 404 to accommodate AdvAgg and still get 'Adv CSS/JS Agg - Asynchronous Mode Set to FALSE'. I've completely removed the Fast 404 code from my settings.php and still get 'Adv CSS/JS Agg - Asynchronous Mode Set to FALSE'. I've disabled modules and still get 'Adv CSS/JS Agg - Asynchronous Mode Set to FALSE'. None of the changes that I have tried get past that one issue. I think we may be chasing the wrong rabbit.
Comment #23
mikeytown2 commentedRemove the fast404 code from settings.php and hit the info & status pages again. We keep digging till we find it; right now fast404 appears to be the issue, but with that gone we'll hopefully find the next roadblock fairly easily.
Comment #24
TallDavid commentedDone. The 'Asynchronous debug info' now shows:
Comment #25
mikeytown2 commentedhmmm I'm running out of ideas for solving this issue. Can you compare what modules are installed on a site that works VS one of your problem sites? Run this code on each of the sites, it will output a sorted module list; from there get the differences and we'll go through the list.
Comment #26
Peter Bowey commentedRefer #24
@TallDavid clearly you have a 'third-party' direct interception for 404's - or an issue with Apache! As it is appears that you are using Apache, this problem could [also] happen in the .htaccess handling - or in several Drupal Modules.
Notes: advagg will normally handle the missing (js|css) asset if Drupal is handed the 404 directly and correctly. If Apache is diverting the 404 to it's own process - then advagg will not pass the async. verification - (though it will still perform it's work OK).
Judging by the 'large length / size' of your problem sites 404's (above samples), I am reasonably confident that you have a custom 404 process in place!
If you suspect that this 'could' be a PHP code problem, then I suggest that you enable PHP 5.x E Notices! I have discovered many problems this way (often 'sloppy PHP code practices' - Drupal and other).
Notes: Standard Drupal disables PHP E' Notices, Pressflow does not (a great debug tool - I think)!
Comment #27
TallDavid commented@mikeytown2, below is a table with the differences in modules between two sites that exhibit the problem (first 2 columns) and one site that does not exhibit the problem (last column).
There are several modules that are on both problem sites, but, not on the 'good' site (date_api, date_timezone, jquery_ui, logintoboggan). These seemed to be good candidates for further testing. On each of the two problem sites, I disabled these modules, cleared the cache and ran a site status to see if the problem was resolved. The problem persists on these sites.
@peter, these sites all run on the same server, so I'm assuming that Apache is not the problem. Please let me know if this is not a good assumption.
I've compared the /.htaccess file on the problem sites to a 'good' site and found no problems. I've removed custom 404 pages from the problem site. I'm not familiar with 'PHP 5.x E Notices', I'll do some research.
Module differences between two problem sites and 1 good site:
Comment #28
Peter Bowey commentedRefer #27
@TallDavid
Perhaps you could use Firefox with the "Live HTTP headers extension" to check the HTTP Header 404 states (live capture).
https://addons.mozilla.org/en-US/firefox/addon/live-http-headers/
After you have installed that extension and restarted Firefox, go to Tools —> Live HTTP headers. That will open up the Live header-viewer window.
In my own 'basic debugging' with advagg 'missing-404' HTTP header responses - you do get an idea what is actually occurring.
Comment #29
mikeytown2 commentedGoing back to #12, if you do not have fast 404's running can you run this code at the bottom of your 404 node page.
If the end of the trace looks just like
and the status report for advagg doesn't throw a
Flush your cacheswarning then I'm out of ideas; if you don't get a advagg-404 entry in watchdog than something is intercepting the request. When checking the advagg-404 entries make sure the location is set to something likefiles/advagg_css/css_missing14510339121306523897_0.css. The last option would be to setup xdebug and get a full stack trace to try and figure out what function is calling drupal_not_found.Comment #30
TallDavid commentedNote: I've updated to the latest AdvAgg 6.x-1.x-dev before running these tests.
When I follow the procedure in #1 with the code in #29, I get the following output in the watchdog:
Interestingly, when I simply attempt to access a non-existent url, I get:
To-date, I have never seen the status report for advagg throw a "Flush your caches" warning. Shouldn't drupal_not_found be called in both cases?
Comment #31
mikeytown2 commentedcan you run this code and paste in the output?
It's a modified version of menu_get_item. And to answer your question advagg has a missing file handler, that should be called; but it is not. That is the issue we are dealing with.
Comment #32
TallDavid commentedAdvAgg debug #31 output
Comment #33
mikeytown2 commentedThat's weird. I'll make a special mode for you that you can set in your settings.php file to have it call the missing handler while in hook_init. This should take care of the issue your having. In your settings.php file add in
Let me know if it works.
Comment #34
mikeytown2 commentedThat's weird. I'll make a special mode for you that you can set in your settings.php file to have it call the missing handler while in hook_init. This should take care of the issue your having. In your settings.php file add in
Let me know if it works.
Comment #35
mikeytown2 commentedComment #36
TallDavid commentedI applied the patch to advagg.module and inserted the $conf line into my settings.php. No joy.
I then navigated to admin/settings/advagg/info, then to watchdog, to retrieve the new "advagg-404" entry, but, there was no new entry.
Mickey, I don't want to monopolize your time. I can live without AdvAgg on these 3 sites. However, I'm willing to keep testing/working on this issue if you think there is value.
[I'm off to ride some trails at Brazos Bend State Park. I'll check back in - in a few hours.]
Comment #37
mikeytown2 commentedWell, I'm going to mark this as postponed until we can better track this one down... I'm out of ideas at this point.
Comment #38
TallDavid commentedOne of the commonalities of the three problem sites is that they were all upgraded from Drupal 5 sites. One started it's life at Drupal 4.6. I'm not sure if it's relevant to this issue, but, it's better to over communicate!
I'm going to roll-back the AdvAgg installations on these 3 problem sites and focus on Drupal 7 upgrades.
@mikeytown2 / @peter bowey, thank you for your efforts and suggestions. Happy Trails.
Comment #39
Peter Bowey commented@TallDavid
That is a great idea (CLEAN Drupal Base). More work for you, but a very positive outcome (D7)!
I know I had several (like) issues just upgrading D6.17 to D6.20
(most of these issues occurred with the (older) Drupal Database hanging onto old (retired) schema's).
Looks like we will not see you at 'advagg' for awhile, Mike is planning the D7 version.
http://drupal.org/node/1171546
Comment #40
cdracars commentedI seem to be having a simailar issue...
Comment #41
mikeytown2 commented@cdracars
Do you have special rules in your setup for imagecache?
Comment #42
cdracars commentedYes here it is.
Comment #43
mikeytown2 commentedIf you notice, the HTML returned in #40 is not a fast404 so the code above (#42) isn't causing the issue. The way the error looks, it appears to be generated from apache. I would check your htaccess and httpd.conf files to see if you have a special configuration for imagecache.
Comment #44
cdracars commentedI've looked at both the .htaccess and .http-conf... and can't find a call for imagecache any where... Also removed imagecache to see if that had any effect.
Comment #45
mikeytown2 commentedDoes imagecache work on your setup? Try looking in your code base for some of the phrases in the html given in #40; like "
This could be because of a broken or outdated hyperlink, a typing error, or the page might not exist anymore." or "The requested page or file was not found:"Comment #46
cdracars commentedcss_missing8299648721308239207_0.css this file does not exist on my system... exactly what the debug info (#40) says. As far as imagecache it works fine. I have yet to locate where those strings are generated from but am still looking. Thank you for your help... and creating the holy grail of aggregation modules.
Comment #47
Peter Bowey commentedRefer #46
Note: css_missing8299648721308239207_0.css is not meant to exist!
It is simply part of the advagg debug check process for correct 404 handling being sent back to Drupal + Advagg!
Here is a snapshot of a correct 'Asynchronous debug info' response (from my own D6 Server):
The very important [advagg] key element is this:
[X-AdvAgg] => Failed Validation. Wrong Pattern@cdracars: I note that your response has this:
[code] => 302This is a HTTP redirect ["Moved Temporarily"] on your Apache 404! So check your .htaccess || http.conf processing.
Comment #48
mikeytown2 commentedThat is correct, the file is missing. AdvAgg has a missing file handler and for some reason it's not being called; thats what the debug output is saying from the test. Imagecache also has a missing file handler and it's located in the files directory; thus they are very similar. Imagecache has been around for a long time thus support for it is usually hard coded in.
Comment #49
cdracars commented@peter bowey: I am unfortunately using a stock .htaccess from drupal 6.22.
Comment #50
Peter Bowey commented@cdracars
Notes 1: Advagg additionally writes this supplement to the stock .htaccess:
This occurs both in the /files/advagg_css directory -and- the /files/advagg_js directory (so the above .css references change to .js)
Notes 2: It could be helpful to set Apache to send 404's to /index.php?q=$uri (= Drupal PHP). This would be a proof test/check of D6 404 handling. I use similar in my Nginx 2nd domain CDN setup to keep advagg 'happy'.
*Your 'HTTP 302' response does not look like Drupal is handling 404's*
Comment #51
cdracars commentedThere are no edits to my .htaccess as their should be.. and on the Apache edit.. I am still pretty new to working with Apache so I'm not sure how to go about doing that.
Comment #52
Peter Bowey commented@cdracars
In your Apache .htaccess -or- http.conf file, add this:
Currently, I am far more conversant with Nginx code than with Apache 2.x, but I did utilize Apache a lot - once :)
*Notes: Target the .htaccess file in your Drupal root folder for the edit!
If you cannot see / find that file, then you are probably on a hosted / rented site that by default 'hides' such files.
You have several ways to deal with that, but that is to be your homework :)
Comment #53
cdracars commentedI have altered my .htaccess to have the
.
No changes however... thanks for pointing me in the right direction as to where to add the change.
Comment #54
Peter Bowey commented@cdracars
Thanks for doing the test.
1) It is important the order that you place the above .htaccess change.
Ideally, you need to place it such that it over-rides other Apache 'diverts'.
2) Have you located the 'reason' on the 302 redirect? That is a real problem!
Comment #55
cdracars commentedI am looking into the 302 redirect now... I have the module working without a hitch on my local dev box but on two servers I am getting the 302 error...
Comment #56
Peter Bowey commentedRefer #55
@cdracars: Good idea, for Drupal does not normally produce a 'HTTP 302 redirect' unless you install some special Drupal Modules. And that could be a 'pass catch' for Advagg 404 handling.
Comment #57
cdracars commentedStarted working on all but a shared host site... Could the hosting be part of the problem? Also still unable to find what is causing the 302 because it just started working on my other sever.
Comment #58
alladdin commentedI have enabled fast 404 module and now on status page I get error for Advagg.
1. Settings.php has been modified to
if (!strpos($_SERVER['QUERY_STRING'], 'imagecache') && !strpos($_SERVER['QUERY_STRING'], '/advagg_')) {2. IP Address to send all asynchronous requests set to '-1'
3. All caches cleared, menu cache cleared twice.
No success.
My Asynchronous debug info:
And:
Thank you for your help
Comment #59
mikeytown2 commentedThe fast 404 module is different from the settings.php script.
The directions I have are for the settings.php script. Here is the issue for the module #1166622: AdvAgg, Fast 404: Support for AdvAgg
Comment #60
mikeytown2 commented#1207178-19: Flush your caches
Comment #61
tjharman commentedI've found the problem!!!! (I think?)
My /files/ directory has this .htaccess in it!
As soon as I removed that - everything worked.
I hope that helps people fix this issue.
Now my question is - can I remove that now??
Tim
Comment #62
mikeytown2 commentedThe default files dir .htaccess should be
Gets created by file_check_directory
Comment #63
tjharman commentedRight, but this is my Drupal install from 4.x that I've slowly upgraded over the years.
Is it possible this is a hangover from a long time ago? I wonder if the people having problems are in a similar situation?
Comment #64
mikeytown2 commentedSounds like the status page needs a test to see if
RewriteEngine offis set in the .htaccess file.Comment #65
TallDavid commentedThe 3 sites that have the same 'Adv CSS/JS Agg - Asynchronous Mode Set to FALSE' issue were all older sites (#38) that began life in Drupal 4 or 5 and had the old-style .htaccess in the \files directory as reported in #61.
For each of the 3 problematic sites, I changed the .htaccess files to the current code (as noted in #62), installed the latest 6.x-1.4 version of the AdvAgg module and the problem is resolved on all sites. Yeah!
Thanks to mikeytown2 for his hard work on this project, to peter bowey for his troubleshooting suggestions and to tjharman for the spark that provided the solution.
Comment #66
mikeytown2 commentedcommitted code that will check files/htaccess to see if "RewriteEngine off" exists if async doesn't work.