Support » Plugins » [Plugin: WP Super Cache] problems with plugins

  • Donncha,

    I been experiencing some problems with WP 2.8.4 and the latest version of WP Super Cache.

    I use the Random File plugin, which adds text from a set of text files inside my template, and the Comment Rating plugin, which lets user vote on comments.

    The problem is that when the Random File plugin gets executed, I see the following text added on my html code:

    Page not cached. No closing html tag found

    And then, the page doesn´t get cached, causing a high load on my server. It used to work fine on WP 2.7.1

    As for the Comments Rating plugin, once you vote the vote image is changed to a gray’ed one. So it dynamically changes the source for that image… but on the process it adds “Page not cached. No closing html tag found”/image.jpg, breaking the html code.

    I notified the Comment Rating author and he fixed it on v2.7 of his plugin. I wonder what the issue is, and how to fix it for the Random File plugin if it´s a WP Super Cache issue.

Viewing 4 replies - 1 through 4 (of 4 total)
  • It could be the output buffer. Do they use ob_start? They may not be closing the output buffer correctly.

    Hi there,

    I’m the author of Comment Rating dbasulto got me into investigating the issue.

    I believe this is a problem in WP-super-cache, that you should look into. Comment Rating uses light-weight AJAX to track voting and change the image after voting. I have a php script ck-processKarma.php to accept vots, update DB and return results. It has a simple way to return those data in ‘|’ separated form. Here’s the code.


    Of course the output is not a valid html.

    When WP-Super-cache’s rewriting rule sees this, it inserted additional declarations to the end of the output of ck-processkarma.php.


    This confused the comment rating javascript like hell.

    My solution is to pretend there’s another field:


    And the javascript ignores everything after the ‘|’ before dummy.

    I’m sure many other people use similar light-weight protocol on top of http and WP-super-cache will mess theme up too.

    The purpose of the added content, I guess, is for debugging. But why should wp-super-cache care whether it’s a valid HTML. It’s be faster if you don’t check whether it’s a valid html.

    Having an option to turn off the Wp-super-cache debugging will avoid the potential problem.

    Thanks, I’ve just modified the plugin to only show that message if debugging is enabled.

    Thanks so much for your fast response.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[Plugin: WP Super Cache] problems with plugins’ is closed to new replies.