johncoswell

What version of WordPress are you running?

I changed my GitHub name, so new link: MockPress

OK, can you do a little diagnostic for me? Right after:

$output_buffer_handlers = ob_list_handlers();

can you add:

error_log("buffers: " . implode(", ", $output_buffer_handlers));

And then post the result from your error log? I want to see what the status of the buffers on your machine looks like when you hit that point in the code.

I believe I have a solution to this problem. PHP Speedy’s output buffering gets stacked below WP Super Cache’s, and the way that WP Super Cache handles working with its own output buffer doesn’t take this into account. The buffers below WP Super Cache’s need to be resolved before WP Super Cache can continue with its page processing. I’ve come up with the following code which seems to allow PHP Speedy and WP Super Cache to play nicely together. This replaces the standalone @ob_end_flush() in wp-cache-phase2.php:

//back up through any output buffers until we get to us
$output_buffer_handlers = ob_list_handlers();
while (count($output_buffer_handlers) > 0) {
  @ob_end_flush();
  if (array_pop($output_buffer_handlers) == "wp_cache_ob_callback") { break; }
}