• I have tried three times to submit a bug report but it always times out. I should add that this also happens when I try and preview or publish pages. I have tried several times already so not sure if you received previous bug submissions. It says “Safari can’t open this page because the server unexpectedly dropped the connection. This sometimes occurs when the server is busy. Wait for a few minutes and try again” That never happened with WP Super cache.

    I had used W3 cache in the past but started having an internal server error issue and nothing worked to resolve it. I tried the .htaccess tips and several more but nothing worked. 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.

    I am on Godaddy and have PHP 5.4 installed. Enabling debugging for Page cache is the only workaround I have found to avoid the 500 Internal Server error but I don’t think that is a good solution since debugging slows things down according to the warning.

    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. I thought that might be relevant.

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

    I know many like to blame Godaddy but I have been pretty happy with their hosting. I got good speeds with Super Cache and also with W3 before I upgraded my PHP to 5.4. Downgrading to PHP 5.3 is not really a good option since some other plugins I use require 5.4 for full functionality. I hope this is a bug you are working on fixing. I like the extra options available in W3 but might have no choice to switch back if this isn’t a bug you are working to fix or a solution isn’t already available.

    my website gwmac.com

    https://www.ads-software.com/plugins/w3-total-cache/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Zee

    (@laserjobs)

    This is a known problem and I have sent information to Frederick Townes via email, twitter and w3edge website but it still has not been resolved. I have come to the same conclusion that you either have to stick with php 5.3 or enable debug for page cache with php 5.4 on GoDaddy shared hosting. The error I get in the apache logs is “End of script output before headers: index.php”

    Zee

    (@laserjobs)

    In the plugin compatibility check the same information is displayed with either php 5.3 or php 5.4. The only thing that changes is the php version from PHP Version: 5.3.24;

    Server Modules & Resources:

    Plugin Version: 0.9.4.1
    PHP Version: 5.4.19;
    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
    “all ok”

    Fancy permalinks: /%year%/%monthnum%/%day%/%postname%/
    WP_CACHE define: Defined (true)
    URL rewrite: Enabled
    Network mode: No

    Thread Starter Alan Wood

    (@gwmacosx)

    Thanks laserjobs. I had been using W3 cache while on the older PHP for several months and then when I upgraded PHP switched to Super Cache. My results actually improved slightly on Gtmetrix, Pingdom Tools, and Google Pagespeed.

    I am wondering if it is worth the trouble to downgrade to PHP 5.3 to use W3 again unless I could really get a speed benefit.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Unable To submit Bug Report with Godaddy PHP 5.4 error’ is closed to new replies.