HyperCache 2.7.1 and WordPress Multisite

July 28, 2010 6 Comments

WordPress 3.0 introduced the multisite concept… and something went wrong with Hyper Cache but only when multisite is active. Standard WordPress blogs which updated to version 3.0 without activating the multisite feature should not have noticed bad Hyper Cache behaviours.

The main problem are the WordPress uploads: with multisite feature active, WordPress serves such files directly instead of leaving Apache (or generally the web server) to do the job. But the service which loads and streams back the file fully initialize WordPress… and the caching systems too.

Now Hyper Cache tries to detect if multisite is active and stop it self when an uploaded file is requested (when the URI contains “/files/”).

I hope that will solve the issue.

My excuses for my bad english but it's the only way I have to communicate with you. Would you suggest a correction? Leave a comment, thank you!
Serious

6 Responses to “HyperCache 2.7.1 and WordPress Multisite”

  1. shabooty Reply July 28, 2010 at 6:20 pm

    thank you for the continued updates/support. cheers.

  2. migf1 Reply July 29, 2010 at 10:07 am

    Thank you for this wonderful plugin and for keep supporting it!

  3. migf1 Reply July 29, 2010 at 10:11 am

    Oh I forgot to ask, in the Settings screen it says: URGENT!!! PLEASE DISABLE THE HTML OPTIMIZATION OR Hyper Cache 2.5+ DOES NOT WORK PROPERLY.

    Could you please explain how I disable the HTML OPTIMIZATION? Is this is a HyperCache setting or a general thing?

  4. Piratoo Reply July 29, 2010 at 6:07 pm

    Hyper-cache 2.7.1. is broken to me.
    It does not create any cache files.

    Files in cache (valid and expired) shows 1, everytime.

    Reverted to 2.6.6 and everything is ok.
    I saw the anomaly once I upgraded to 2.7.1, not sure about 2.7.0.

    Running WordPress 3.0.1 alpha.
    I have define(‘WP_ALLOW_MULTISITE’, false);
    in my config.php [FALSE, not TRUE!]

    Does it matter?

  5. Nick+Niebling Reply August 15, 2011 at 3:32 pm

    Hi there,

    Sorry for maybe spamming you.. I jsut saw this post and would like to post my question here as well, as I think it might be related?

    ——–

    I’ve got the latest and greatest version of WP and Hyper Cache on my brand new WP blog.

    I did visit and browse the site with IE private browsing and Chrome Inkognito. No signature (browsed the same 10 pages a lot of times) – but it doesn’t make any cahcing :-(

    So the Cleaning process seems to be working just fine (updating the “next clean stamp”).

    I’ve changed the chmod of the cache (and hyper cache subdir) to 777. I only get 1 file in my cache folder: “_archives.dat”. The file is empty and I don’t know when the file is generated, but it seems to change the file last modified date on a regular basis.

    I’ve tried to deactive the plugin and reactivate. Tried to deactive, delete, install and activate. Tried to deactive, delete manually, manually delete cache folder, install and activate. All with standard settings.

    I did try to disable the “Disk space usage” setting at first use – but it seemed to be buggy to just save that setting (it kept checked/active). Else I havn’t been touching the settings..

    WordPress version: 3.2.1
    Hyper Cache: 2.8.5

    I’ve got a custom theme – so maybe I need to include some WP-stuff I don’t know about? Do you require more than wp header and wp footer? (not using multisite and did enable caching)

    I’ve been using other cache plugins before, but I read a good benchmark of your plugin putting Hyper Cache in front of all the others competitors, so I would really like to try it out and maybe use it for all my blogs in the future. (Donations are of course given to my favorite plugins)

    Cheers,
    Nick Niebling

  6. Nick Niebling Reply September 23, 2011 at 5:26 pm

    My solution was to remove this from my functions.php:

    if(extension_loaded(“zlib”) && (ini_get(“output_handler”) != “ob_gzhandler”)) {
    add_action(‘wp’, create_function(”, ‘@ob_end_clean();@ini_set(“zlib.output_compression”, 1);’));
    }

    My old approach to get a little performance (gzip with lzip) seems to break the Hyper Cache plugin.. Glad I found the bug :-) Hope I might save others for some time..

Leave a Reply