Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter dparkmit

    (@dparkmit)

    Hi Donncha,

    I was wondering if the additional info I gave you is helpful in figuring out what is causing the homepage to not cache? Thanks again for your awesome help!

    David

    Thread Starter dparkmit

    (@dparkmit)

    Hi Donncha,

    Here is the directory structure for our app:


    /vol
        /www
            /HOSTNAME
            /blog
                /caches - this directory stores the files created by several different caches
                    /wp-cache - this directory stores all files created by the WP cache
                /source - this directory contains the WP source code
                    /wp-content
                        /cache - this is a symbolic link to /vol/www/HOSTNAME/blog/caches/wp-cache

    We use a symbolic link for the WP cache directory because we don’t want to commit/export cache files from our subversion source code repository.

    Please let me know if you need any more info. Thanks!

    Thread Starter dparkmit

    (@dparkmit)

    Hi Donncha,

    Sorry about the confusing directory structure. Here’s how our site works.

    1. The WP source code for the blog is in the directory /vol/www/HOSTNAME/blog/source/ (we have several different hosts – one for production, a couple for development and one for staging).

    2. The source code for our main website is in the directory /vol/www/HOSTNAME/forum/source. Apache has a virtual host that routes all requests for the site HOSTNAME into the /vol/www/HOSTNAME/forum/source directory.

    3. The code for our main website (/vol/www/HOSTNAME/forum/source) has a symbolic link called “mba” that points to the blog source code directory (/vol/www/HOSTNAME/blog/source)

    We separated the blog source code from our other source code so that we could maintain them separately.

    Please let me know if you need any more info. Thanks so much for your help!

    Thread Starter dparkmit

    (@dparkmit)

    Hi Donncha,

    I enabled debugging on our dev box and here’s the output:

    01:17:56 /mba/ supercache dir: /vol/www/dp.www.beatthegmat.com/blog/source/wp-content/cache/supercache/dp.www.beatthegmat.com/mba/
    01:17:56 /mba/ No wp-cache file exists. Must generate a new one.
    01:17:56 /mba/ In WP Cache Phase 2
    01:17:56 /mba/ Setting up WordPress actions
    01:17:56 /mba/ Created output buffer
    01:17:56 /mba/ supercache dir: /vol/www/dp.www.beatthegmat.com/blog/source/wp-content/cache/supercache/dp.www.beatthegmat.com/mba/
    01:17:57 /mba/ Output buffer callback
    01:17:57 /mba/ supercache dir: /vol/www/dp.www.beatthegmat.com/blog/source/wp-content/cache/supercache/dp.www.beatthegmat.com/mba/
    01:17:57 /mba/ Anonymous user detected. Only creating Supercache file.
    01:17:57 /mba/ supercache dir: /vol/www/dp.www.beatthegmat.com/blog/source/wp-content/cache/supercache/dp.www.beatthegmat.com/mba/
    01:17:57 /mba/ Gzipping buffer.
    01:17:57 /mba/ Writing non-gzipped buffer to supercache file.
    01:17:57 /mba/ Writing gzipped buffer to supercache file.
    01:17:57 /mba/ Warning! Not writing another page to front page cache.

    It looks like the error message is “Warning! Not writing another page to front page cache.” Can you please let me know what I can do to fix that? FYI, this is happening every time that our home page is loaded.

    Thread Starter dparkmit

    (@dparkmit)

    Hi Scott,

    Thanks for the quick reply! I love PODS even more now. Here’s one quick question. Can I upgrade PODS to the latest version if I still use WP 2.8.4?

    I tried to upgrade our WPMU 2.8.4 to WP 3.0.1 recently but ran into some crazy performance problems – the site slowed to a complete crawl after the upgrade and our server started totally crashing. The unix top command showed that CPU utilization was going through the roof.

    So we’ll probably upgrade to WP3 at some point in the future, after we can figure out what’s causing this problem. But for now, we’re going to stay on 2.8.4.

    Thread Starter dparkmit

    (@dparkmit)

    Thanks for the quick reply. I understand the fact that I need to use Disk Enhanced mode to get the result that I was seeking – specifically the mode of having WP generate a pure HTML file that Apache can use.

    The problem that I found, however, is that W3 Total Cache w/ Disk Enhanced on my system isn’t writing the files to the right location. As I wrote in the prior post, the files in wp-content/w3tc/pgcache are the same regardless of whether I use Disk Enhanced or just Disk. And neither are writing files according to the rules that are in the .htaccess file.

    I’m sorry if I’m not doing things correctly. And I totally appreciate your support for this plugin. Any insight into what I should check/do to correct this issue would be greatly appreciated! Thanks again!

    Thread Starter dparkmit

    (@dparkmit)

    Hi Frederick,

    Here’s one other question based on your reply:

    Seems so, try the exact same approach except the file path is: wp-content/w3tc/pgcache/www.beatthegmat.com/index.html.gzip

    When I select either enhanced disk or disk for page caching, this is the directory structure of pgcache after a single page has been served:


    wp-content/w3tc/pgcache
    wp-content/w3tc/pgcache/.htaccess
    wp-content/w3tc/pgcache/4e
    wp-content/w3tc/pgcache/4e/4b
    wp-content/w3tc/pgcache/4e/4b/4e4b1c2fa63f672e0fd461b51a131627
    wp-content/w3tc/pgcache/ba
    wp-content/w3tc/pgcache/ba/56
    wp-content/w3tc/pgcache/ba/56/ba564306ec5b5d581d28768d9f628c03

    Can you please let me know what is happening here? It seems that Apache will always have to call PHP code even with the disk-based cache because a cached output file that matches the pattern in the .htaccess file doesn’t exist. FYI, I’ve copied the pattern below.


    RewriteCond /vol/www/%{HTTP_HOST}/sites/blog/wp-content/w3tc/pgcache/%{HTTP_HOST}/$1/index.html%{ENV:APPEND_EXT} -f
    RewriteRule (.*) wp-content/w3tc/pgcache/%{HTTP_HOST}/$1/index.html%{ENV:APPEND_EXT} [L]

    Thread Starter dparkmit

    (@dparkmit)

    Hi Frederick,

    Now that we’ve gotten APC cache to work on our blog, do you recommend that we still use disk-based caches for everything rather than APC? If so, can you please explain why you think disk is better than APC? Thanks again for the great help!

    David

    Thread Starter dparkmit

    (@dparkmit)

    Hi Frederick,

    I wanted to write back to let you know that I figured out the problem with my site. There were two lines at the top of my .htaccess file for the WP directory that I accidentally deleted:


    RewriteEngine On
    RewriteBase /mba

    Without these lines, Apache didn’t know how to route the request correctly because it expected the blog to not be in a sub-directory. Once I put those lines back, it worked.

    dp

    Thread Starter dparkmit

    (@dparkmit)

    Hi Frederick,

    Thanks for the guidance and the info on enhanced disk vs. APC. I assumed that enhanced disk would be faster because it would fetch the info from memory vs. disk. I’ll run our site with enhanced disk cache. Here are the versions of my software:

    • PHP: 5.2.10-2ubuntu6.3 with Suhosin-Patch 0.9.7 (cli) (built: Nov 26 2009 14:42:49)
    • Apache: Apache/2.2.12 (Ubuntu)
    • APC: 3.0.19
    • WordPress: 2.8.4
    Thread Starter dparkmit

    (@dparkmit)

    Thanks for the great suggestion. Is there any specific plugin that you’d recommend? Thanks!

Viewing 11 replies - 1 through 11 (of 11 total)