Page Cache not working with php 5.4

I have no idea what godaddy uses these days, but you can try disabling the plugin, and if you have ftp or a file manager, delete the .htaccess file.

Then you can re-enable the plugin, and let it generate a new .htaccess.

Not sure if thats your problem, but I haven’t used apache server in years so thats all I can think of.

Chris

Yeah it has something to do with GoDaddy. I downgraded PHP to 5.3 and it worked fine.

Anyone find a solution to this since PHP 5.3 is EOL?

The .htaccess files are not being edited when changing settings in w3tc with php 5.4 where they are being edited in php 5.3. I changed the .htaccess files from 604 to 644 and there was no difference. Could it be a permissions problem with GoDaddy and php 5.4?

Disk: Basic still serves a 500 error

Permissions on the cache and w3tc-config folders permissions are 705 where the rest are 755

.htaccess files in both the root and page_enhanced are 604 where the rest of the files are 644

The compatibility check is as follows the only thing that changes is the PHP Version to 5.4.19

Server Modules & Resources:
Plugin Version: 0.9.4.1
PHP Version: 5.3.24;
Web Server: Apache
FTP functions: Installed (required for Self-hosted (FTP) CDN support)
Multibyte String support: Installed (required for Rackspace Cloud Files support)
cURL extension: Installed (required for Amazon S3, Amazon CloudFront, Rackspace CloudFiles support)
zlib extension: Installed (required for compression support)
Opcode cache: Installed (APC)
Memcache extension: Not installed
HTML Tidy extension: Not installed (required for HTML Tidy minifier suppport)
Mime type detection: Installed (Fileinfo) (required for CDN support)
Hash function: Installed (hash) (required for NetDNA / MaxCDN CDN purge support)
Safe mode: Off
Open basedir: Off
zlib output compression: Off
set_time_limit: Available
mod_deflate: Not detected (required for disk enhanced Page Cache and Browser Cache)
mod_env: Not detected (required for disk enhanced Page Cache and Browser Cache)
mod_expires: Not detected (required for disk enhanced Page Cache and Browser Cache)
mod_headers: Not detected (required for disk enhanced Page Cache and Browser Cache)
mod_mime: Not detected (required for disk enhanced Page Cache and Browser Cache)
mod_rewrite: Not detected (required for disk enhanced Page Cache and Browser Cache)
mod_setenvif: Not detected (required for disk enhanced Page Cache and Browser Cache)
Additional Server Modules

New Relic
PHP version: Supported
Operating System: Supported
Web Server: Not Supported. (Apache See NewRelic Requirements page.)
WordPress Resources

/..somestuff../.htaccess: OK
/..somestuff../wp-content: OK
/..somestuff../wp-content/uploads/2015/01: OK
Fancy permalinks: /..somestuff../
WP_CACHE define: Defined (true)
URL rewrite: Enabled
Network mode: No

Apache errors:

[Sat Jan 31 10:32:41 2015] [7381100] [fcgid:warn] (104)Connection reset by peer: [client x.x.x.x:63334] mod_fcgid: error reading data from FastCGI server
[Sat Jan 31 10:32:41 2015] [7381100] [core:error] [client x.x.x.x:63334] End of script output before headers: index.php

Another interesting point is I found a folder in the page_enhanced cache that was named as follows:

www.somedomain.comhttp:

It had two paths to post files. So is there a problem with the path causing the issue?

On a test site I removed W3TC (that was giving a 500 error to non-logged in users on php 5.4) and installed WP Super Cache using mod_rewrite to serve cache files. WP Super Cache worked without issue but I would still like to solve this so I can use W3TC for my larger sites.

NOTE: I just tried uninstalling (removed all files, htacess and cache folders) and reinstalling on php 5.4 on GoDaddy. Same 500 error.

I do notice that WP Super Cache defines WPCACHEHOME in the wp-config file where W3TC does not

Tried stopping processes each change, compatibility mode, NFS file system on/off, rearranging htaccess, etc.

I am wondering if it has something to do with the server configuration even though WP Super Cache works?

Here is why:
I am running a few sites and using “AddHandler x-httpd-php5-4 .php” in .htaccess to change to PHP Version 5.4.19 for testing purposes.

Everything is normal in the php info file until Environment
GD_PHP_HANDLER x-httpd-php5-3

And PHP Variables pointing to php 5.3
_SERVER[“GD_PHP_HANDLER”] x-httpd-php5-3

So I found something interesting. W3 Total Cache Page Cache will work with php 5.4 on GoDaddy if Debug Mode is enabled. If Debug Mode for Page Cache is disabled it will return a 500 error to non logged in users (cached serving).

I know we are supposed to start new threads but I have the exact same issue. I had used W3 cache in the past but started having that internal server error issue and nothing worked to resolve it. I switched to Super Cache several months ago.

I figured I would give W3 a chance again after four months in the hopes an update had solved the issue by now. It hasn’t.

Last night I also discovered independently that one workaround is to enable debugging for Page cache. I figured that out before I found this thread.

Like the person above my post I am on Godaddy and have PHP 5.4 installed. Enabling debugging for Page cache is the only workaround I have found but I don’t think that is a good solution since debugging slows things down according to the warning.

I hope the developer will see this thread and realize there is a problem that needs to be addressed. On another note, Opcode APC is an option that can be selected in settings. Is there any advantage to choosing that on Godaddy over Disk or Disk enhanced?

I installed W3 last night and ran Gtmetrix, Pingdom Tools, and Google Page speed and all three are giving me the identical scores I last ran on WP Super Cache. That is strange as you would expect some change for the better or worse, but something different.

Besides downgrading to PHP 5.3 is there any fix for this 500 internal server error?

I’m having the same problem, just upgraded to PHP5.4 on godaddy and getting the 500 internal server error. I love this plugin and don’t want to switch if possible.

Help please.

marky10000, the only way it will work on GoDaddy php 5.4 is with debug enabled for page cache otherwise you need to downgrade to php 5.3

Woocommerce demands 5.4 since the latest upgrade, so downgrading is now out for me.

Also having this problem. It only works with debug mode turned on. I am also on godaddy with PHP 5.4.

Could you guys also let Frederick Townes know on twitter about this issue
https://twitter.com/w3edge
Tweets by fredericktownes