charleslf

You are using an outdated version of PHP that has already reached its end-of-life (almost 6 years ago).

You should update the PHP version that your server is running.

Now, going back to your problem.

What is the value of “Expires header lifetime” in Performance => Browser Cache.

The TTL of page cache files is set via the “Expires header lifetime” field in the “HTML” section on Browser Cache Settings tab.

Hey @timmen22,

Perhaps not directly related to the problem you’re facing, but worth mentioning: The filter function you mention above only works on the community edition of W3TC.

Also, the parameters are reversed, it should be:

add_filter('w3tc_pgcache_lifetime', function($time, $request_uri) {
    if( $request_uri == '/' ){
        $time = 604800;
    }
    return $time;
},10,2);

• This reply was modified 8 years, 6 months ago by charleslf.

Hey @lindholmfotografie,

Out of curiosity, are you using something other than enhanced disk-cache (example: memcached) as your page cache engine?

There’s a bug with the sitemap flush that I’ve identified and fixed here: https://github.com/szepeviktor/fix-w3tc/issues/75

Hey @bryan202,

It seems you did not deactivate the w3-total-cache plugin and replaced its files.

Here are the instructions to follow:

Installation

1. Deactivate official w3tc plugin from WP.org
2. Delete plugin directory w3-total-cache by hand, DO NOT click “Delete” on Plugins page
3. Unpack master in /wp-content/plugins/
4. Rename the extracted directory from fix-w3tc-master to w3-total-cache
5. Activate w3tc

Hey @bhamrick,

This is indeed the same old bug that is mentioned in the thread that you found.
You can try the fix that @whiteshadow recommended by changing (in /w3-total-cache/lib/W3/Plugin/NewRelic.php and /w3-total-cache/lib/W3/Plugin/Cdn.php) the line that says:

$role = array_shift( $current_user->roles );

to

$role = reset( $current_user->roles );

I have opened a new issue on the community-driven version of W3TC and will patch it up there in the coming couple of days.

You can follow the progress over here.

• This reply was modified 8 years, 6 months ago by charleslf.

@abdorefky, I’m not the owner of the github repository, but I have recently started contributing there.

The repo is community-driven and fixes a lot of bugs in w3tc (some of these bugs have been identified and reported at least 2 years ago and yet went on without a fix!).

As Fist Full of Crisco said, it’s up to you to decide on whether to use it or not.

@detoner,
Have you tried changing your theme to a default one? Does the error persist when you do so?
I’m inclined to think this is not strictly w3tc-related, seems like some faulty gzip configuration to me. Could you post the content of your .htaccess file too?

@kimberly, this is off-topic, but I’d love to hear your thoughts on these two issues #31 and #32

I don’t know about the original author’s plans and if he’s still willing to update the plugin.

However, there’s a community-driven version of w3tc that is compatible with php 7 and also fixes several long-standing bugs in the original plugin.

You might want to check it out.

I would create different master.php files (from wp-content/w3tc-config/master.php) for the different configurations, and copy them over to their corresponding installation.

It’s not exactly the “defined constant” approach you were looking for, but it might help you in separating the local development environment settings from production ones.

Can you please post here your line 82 from wp-content/plugins/w3-total-cache/inc/functions/file.php?

The error you’re seeing is when w3_rmdir function is called.
Line 82 should look something like this:
$dir = @opendir($path);
notice the “@” just before opendir. This is there to suppress those warning messages in case the folder does not exist.

Otherwise, you can also try adding the following just before line 82 (above $dir = @opendir($path);):

if(!is_dir($path)) { return false; }