• Can anyone verify that WP Super Cache works on GD Linux Deluxe Shared Hosting as it is supposed to? And, if necessary, what modifications need to be made?

    On the surface, it appears to work. I see this on the first page load:

    <!-- Dynamic page generated in 0.779 seconds. -->
    <!-- Cached page generated by WP-Super-Cache on 2009-04-16 09:55:51 -->

    and this on the second:

    <!-- Dynamic page generated in 0.779 seconds. -->
    <!-- Cached page generated by WP-Super-Cache on 2009-04-16 09:55:51 -->
    <!-- Compression = gzip -->

    I have checked the headers using the plugin for firefox, in which WP-Super-Cache: WP-Cache is there.

    However, YSlow reports that it is not gzipped. I tried using a couple online, which also report the same.
    https://www.whatsmyip.org/mod_gzip_test/
    https://nontroppo.org/tools/gziptest/
    https://www.seositecheckup.com/html_compression_status.php

    I will also add that I am having this problem on 3 sites, each hosted within a separate hosting account. I have WP-Cache running on one site on one of those accounts that reports being served as gzipped. So, WP-Cache is working and WP-Super-Cache is not. The sites with Super Cache never had WP Cache installed.

    I also tried using the ismyblogworking.com link and got this:
    The important stuff:

    * Your web server [IP] is working fine.
    * Your RSS feed is available.
    * Your blog is not indexed by Google. (it is)
    * Your blog seems slow. It took 4.91 seconds to generate the page.
    * Your blog application doesn’t support gzip compression.
    * Your blog doesn’t support client caching (no 304 response).
    * WP Super Cache is active.
    * Your feed doesn’t support caching (no 304 response).

    So, even though it appears to report that it is working, it doesn’t appear to actually be serving cached files or gzipped files.

    I tried it with the WP-Cache enabled blog and:
    * Your web server [IP] is working fine.
    * Your RSS feed is available.
    * Your blog is indexed by Google.
    * Your blog supports client caching (304 response).
    * Your feed supports caching (304 response).

Viewing 3 replies - 16 through 18 (of 18 total)
  • merid – wp-super-cache doesn’t use either of mod_gzip or mod_deflate. It does it’s own gzipping and stores the gzipped cache page.

    Hey, I spent a couple of hours hacking away at this, and finally got it working.

    OKAY! SO!

    I used the instructions here to enable compression. I have PHP5 running on my client’s account, so I went to their root directory, created a php5.ini file, and pasted in

    output_buffering = On
    output_handler = ob_gzhandler
    zlib.output_compression = Off

    I believe if you’re using PHP4, then you need to name it php.ini, but don’t quote me on that!

    Anyway, after that, it seemed to work perfectly. I tested it at https://ismyblogworking.com, whatsmyip and YSlow.

    This still doesn’t help for gzipping the CSS and JS, but it’s a definite start.

    I hope that helps!

    I also have ismyblogworking.com telling me that my site is not enabled for Gzip compression, even though I have WP Super Cache operating in Full mode. I found this site that tells how to turn gzipping on (it’s a very simple solution):
    https://wpbloghost.com/blog/gzip-compression/

    He recommends that you check your site at https://www.port80software.com/support/p80tools.asp

    When I run my site – without any change – on port80software, it tells me that gzip compression is working, in direct contradiction of ismyblogworking.com.

    It occurs to me that ismyblogworking is checking the wrong thing when a blog is using WP Super Cache. Donncha says above that his plugin uses its own gzipping, which perhaps turns off the standard WP or PHP gzipping process. It is possible that, when you “fix” this problem identified by ismyblogworking, you are actually duplicating Donncha’s process.

    Any thoughts?

    Steve

Viewing 3 replies - 16 through 18 (of 18 total)
  • The topic ‘Bizarre Behavior – Not Working- GoDaddy Hosting’ is closed to new replies.