Forum Replies Created

Viewing 4 replies - 151 through 154 (of 154 total)
  • I believe I had the same problem. I traced it back to the fact that the automatic upgrade did not upgrade the advanced-cache.php, db.php, and object-cache.php files in the wp-content directory. When I manually upgraded these, the plugin began escaping characters correctly in the .htaccess file.

    I had 500 Internal Server Errors when I upgraded to the latest version and copied the new suggested rules into my .htaccess file. I figured out that the RewriteCond %{HTTP_USER_AGENT} line was not properly escaped.

    In my case, this happened because the automatic upgrade/install had not automatically replaced the old db.php, advanced-cache.php, and object-cache.php files in the wp-content directory.

    After replacing these files with the new versions, the suggested code to paste into my .htaccess file suddenly had the proper escape characters. I copied this code into my .htaccess file and it solved my 500 Internal Server Errors.

    Thread Starter robertstaddon

    (@robertstaddon)

    fredericktownes, would you recommend that I post this question on the WordPressMU forums instead of here? It is true that it only applies to a WordPressMU installation.

    Thread Starter robertstaddon

    (@robertstaddon)

    It’s not really a 404 error. If I FTP into my server and remove the file completely, I get the “file not found” message.

    When W3TC is active, a web browser will find large files but can only download 0kb of them. Try to download the two top example files above and you’ll see what I mean. If the W3TC plugin is deactivated, you would be able to download them entirely.

    Here’s how to consistently replicate the problem:
    – Install WordPressMU
    – Install and activate W3TC
    – FTP upload a large file (>20MB) into wp-content/blogs.dir/1/files/ or any subdirectory
    – Try to access that file via a web browser

Viewing 4 replies - 151 through 154 (of 154 total)