• W3TC seems to be working well for me on the front end, but one thing I notice on the back end is that every time I make an update, e.g., empty the page cache, change a setting, or even edit and update a post, the admin page fails to reload correctly and instead just gives me a blank white screen. Reloading doesn’t work. But if I click back and reload, the pages will load correctly with any changes accommodated.

    I’ve tried enabling and disabling individual items like page caching, DB caching, etc., but nothing seems to work. Cache settings are currently set so that pages are not cached for logged in users.

    Any help here would be greatly appreciated. Thanks!

    http://wordpress.org/extend/plugins/w3-total-cache/

Viewing 10 replies - 1 through 10 (of 10 total)
  • Are you running a reverse proxy on your server? It’s best to submit a bug submission form from the support tab of the plugin if you can get it to load.

    Thread Starter rabbitpoets

    (@rabbitpoets)

    Reverse proxy? No I don’t think so, at least I don’t believe I have any unusual settings enabled. I’ll go ahead and submit a bug submission. Thanks.

    Thread Starter rabbitpoets

    (@rabbitpoets)

    Hmm, I got the white page error when I clicked submit, but hopefully the message got to you. Can you let me know if you didn’t receive it? My email is rp@rabbitpoets.com. Thanks.

    Thread Starter rabbitpoets

    (@rabbitpoets)

    Ah! Sorry for the barrage of messages. A couple bug reports may have come through as well, but I think I’ve figured out the issue.

    I’d previously configured Apache to set the Expires header in the .htaccess file (following direction here: http://www.askapache.com/htaccess/apache-speed-compression.html), but it seems like that created some conflict with the W3 plugin.

    But after deleting the above info from the htaccess file, it looks like everything is functioning ok. Admin actions aren’t resulting in blank pages, redirects are functioning ok, etc.

    Update
    —————
    Hmm… I may have spoken too soon. For whatever reason everything works fine as long as I have the database cache option and the database debug mode checked. If I uncheck one or both, the admin actions > blank pages errors still seems to occur… so it might be worth a further look.

    I’d previously configured Apache to set the Expires header in the .htaccess file (following direction here: http://www.askapache.com/htaccess/apache-speed-compression.html), but it seems like that created some conflict with the W3 plugin.

    As it says in the description, W3TC takes care of this for pages / posts / feeds, so you need to update your directives to only deal with static files like images.

    Thread Starter rabbitpoets

    (@rabbitpoets)

    As it says in the description, W3TC takes care of this for pages / posts / feeds, so you need to update your directives to only deal with static files like images.

    Right, I had forgotten I’d changed that setting in the past. So now I actually don’t have apache handling any of the compression and run everything through W3TC.

    But do you have any idea why I’d still be getting blank page errors if I don’t have both database cache option and database debug mode enabled? It seems like it’s interfering with the way some of the admin pages redirect. Thanks.

    Thread Starter rabbitpoets

    (@rabbitpoets)

    Well, I think I may have found and resolved the issue (*knock on wood*). I had some poorly written PHP in the functions file of my theme that looked like it was conflicting with the way the caching was functioning. Nothing inherently wrong with W3TC, but bad code on my part that must have triggered all this.

    W3TC has it’s own namespace for it’s functions. Can you provide more detail on the conflict in case I missed something?

    Thread Starter rabbitpoets

    (@rabbitpoets)

    Sure, I use a custom version of the Street Child theme for Thematic.

    I decided to switch my theme to the base thematic theme to see if the admin blank page/redirection issues still occurred, and surprisingly, once I switched the them, everything worked fine.

    So I then uploaded a stock version of the Street Child theme to see if that had any issues, and actually that & W3TC had no conflicts.

    So at that point I figured there must be a conflict with some of the modifications I’d made. Through the process of elimination, I was able to whittle the problem area down to my version of the functions file.

    In my functions file, I had the following code (in addition to others):

    <?php
    function childtheme_create_stylesheet() {
    $templatedir = get_bloginfo('template_directory');
    $stylesheetdir = get_bloginfo('stylesheet_directory');
    /* <link rel="stylesheet" type="text/css" href="<?php echo $templatedir ?>/library/styles/reset.css" /> */
    ?>
    <link rel="stylesheet" type="text/css" href="<?php echo $stylesheetdir ?>/thematic.css" />
    <link rel="stylesheet" type="text/css" href="<?php echo $stylesheetdir ?>/style.css" />
    <?php
    }
    add_filter('thematic_create_stylesheet', 'childtheme_create_stylesheet');
    ?>
    
    <?php
    function goingup() {
    $gu_siteid="bpmzrib";
    $gu_param = "st=".$gu_siteid."&ref=".urlencode($_SERVER['HTTP_REFERER']).
    "&vip=".$_SERVER['REMOTE_ADDR']."&ua=".urlencode($_SERVER['HTTP_USER_AGENT']).
    "&cur=".urlencode("http://".$_SERVER['HTTP_HOST'].$_SERVER['REQUEST_URI'])."&b=5";
    @readfile("http://counter.goingup.com/phptrack.php?".$gu_param);
     ?>
    <?php }
    add_filter( 'thematic_after', 'goingup' );
    ?>

    The upper calls the style sheet into the header, the latter a tracking code into the footer. I found that when I deleted only one of the code chunks, I still ran into the admin blank page/redirect issue. But when I deleted both of the codes from the functions file, everything worked fine. The problem only started occurring after I began running the W3TC plugin – unless I had both the database caching and database caching debug options checked off.

    So I reworked the two chunks of code above and changed it to the following:

    function childtheme_create_stylesheet() { ?>
    <?php
    $templatedir = get_bloginfo('template_directory');
    $stylesheetdir = get_bloginfo('stylesheet_directory');
    ?>
    <link rel="stylesheet" type="text/css" href="<?php echo $stylesheetdir ?>/thematic.css" />
    <link rel="stylesheet" type="text/css" href="<?php echo $stylesheetdir ?>/style.css" />
    <?php }
    add_filter('thematic_create_stylesheet', 'childtheme_create_stylesheet');
    
    // Going up code
    function goingup() { ?>
    <?php
    $gu_siteid="bpmzrib";
    $gu_param = "st=".$gu_siteid."&ref=".urlencode($_SERVER['HTTP_REFERER']).
    "&vip=".$_SERVER['REMOTE_ADDR']."&ua=".urlencode($_SERVER['HTTP_USER_AGENT']).
    "&cur=".urlencode("http://".$_SERVER['HTTP_HOST'].$_SERVER['REQUEST_URI'])."&b=5";
    @readfile("http://counter.goingup.com/phptrack.php?".$gu_param);
     ?>
    <?php }
    add_filter( 'thematic_after', 'goingup' );

    I’m not very familiar with PHP, but making the changes above apparently must be the correct way to write the code. Because once I uploaded the new functions file, everything started working again. I turned off all caching options, turned off debug options, then turned on each caching option (leaving the debug options off), and it worked ok each time – no admin blank page/redirect issues.

    Let me know if you need any more details.

    Thanks, that’s interesting.

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

The topic ‘[Plugin: W3 Total Cache] Blank pages when taking admin actions’ is closed to new replies.