remotay

Jonno225,

What sort of results are you seeing as eAccelerator usage for Minify / DB Cache? From what i’ve read on these forums and from numerous tests, the most optimized setup is Disk Enhanced for page cache, and APC / Eaccelerator for Minify / DB cache. I’m sure it varies from server to server though.

Based on what Fredrick said before Disk Enhanced is the fastest for page cache.

I think I found the culprit..

I have <?php flush(); ?> right after my </header>. I read that this is optimal for making a site load faster as per the Yahoo Best Practices guide. This has to be it, because when the pages “screw up”, they load everything in the header and that’s it.

Any way <?php flush(); ?> could interfere with W3 Total cache? The problem doesn’t happen often enough for me to test my hypothesis..

Argh, Just had the issue again, this time it happened on my homepage. It’s not a big deal if it happens on a random inner page, but when its homepage, it sort of screws up the entire site until I clear the cache. Dug through my PHP Error log and apache error log and couldn’t find anything out of the ordinary.

Invalid method in request \x16\x03\x01 is it, but that error has to do with SSL or something, so its unrelated. I’m using PHP Version : 5.2.9 maybe upgrading will help?

I found a few entries in the apache error log regarding W3TC. I sent you them via your contact us page on W3Edge.

There were several more “request failed: error reading the headers” on June 1 but I didn’t include all of them.

On my Cpanel I checked the error log, I’m not even sure how to access the apache log, but I’ll find out and check.

The problem still happens now. Random parts of my website (High traffic) will be blank and only the header will load. It looks like W3 Total cache is caching these pages which only load up to the header, and serving those cached files.

I need to clear the cache to fix the issue, and hope that the cache is rebuilt properly. There are no entries into my error log when this happens.

The issue doesn’t happen THAT often, but I noticed it happening more often today randomly. I did notice since you updated your plugin the issue happened a lot less. Any idea what may be causing this? I’m on the latest release version of WP. Site is MMOHut.com

Just to rule out my own browser screwing up, I have cleared my own cache, and hit CTRL+F5 on the affected page(s) to no avail. Page is still blank with only header loaded all the way up to </head>, usually only ONE page out of my 2000 or so pages get affected.

OMG! AFTER 3+ HOURS OF FIDDELING WITH shutter-reloaded.js I FIXED THE PROBLEM!

1) I know ABSOLUTELY nothing about Javascript. I literally just played around, changed variables, deleted lines to see what happened.

I have NO Idea whether my fix has any other adverse effects or not, so maybe someone can comment?

To fix the problem, remove

document.documentElement.style.overflowX = ”;

that entire line. Delete that bit, save, and upload and problem fixed! Anyone want to tell me what that line does? And will removing it break anything else? So far everything looks peachy on my end.

Yes, I’m excited. I fixed something when I had no idea what I was doing :). Took hours of screwing around!

OMG! AFTER 3+ HOURS OF FIDDELING WITH shutter-reloaded.js I FIXED THE PROBLEM!

1) I know ABSOLUTELY nothing about Javascript. I literally just played around, changed variables, deleted lines to see what happened.

I have NO Idea whether my fix has any other adverse effects or not, so maybe someone can comment?

To fix the problem, remove

document.documentElement.style.overflowX = ”;

that entire line. Delete that bit, save, and upload and problem fixed! Anyone want to tell me what that line does? And will removing it break anything else? So far everything looks peachy on my end.

Yes, I’m excited. I fixed something when I had no idea what I was doing :). Took hours of screwing around!

If anyone found a fix please please post it! The newest nextgen gallery still has this bug =[!

Same problem. The problem is with Firefox 3.6. I’d appreciate it if anyone can develop a workaround for this. The problem even happens on the latest version of nextgen gallery

Move the part of the code that removes or adds the WWW bit your url to the absolute top of your .htaccess.

Weird. I just got a blank page today on my site. I did notice that the issue happens MUCH less frequently on the latest version of W3TC but it still does happen from time to time.

Excellent. Once you told me the issue was with the ordering of directives, the issue was obvious. I didn’t submit the report. Someone else did.

To those having this issue – simply put the remove WWW directive in the .htaccess as the first directive (Rather than the W3 Total Cache directive).

I have this exact same problem. Any solutions? I just noticed it too. I don’t think this happened on the last version of W3 TC.