• Resolved reviewmylife

    (@reviewmylife)


    Hi Frederick,

    I’ve spotted that W3 Total Cache suffers from the same problem with mod rewrite rules that WP Super Cache suffered from until very recently (Donncha fixed the WP Super Cache problem in 0.9.9.8). Any chance you could fix the problem too?

    Here’s a bit of background:

    On most host the PHP paths and Apache paths start from the same root. This means that when you create the rewrite line for the .htaccess using the PHP paths it works on most hosts as the Apache path is the same. For example using the PHP extracted path you get a line like this:

    RewriteCond "/homepages/xx/dxxxxxx/htdocs/blog/wp-content/w3tc/pgcache/$1/_index%{ENV:W3TC_UA}%{ENV:W3TC_SSL}.html%{ENV:W3TC_ENC}" -f

    The problem on 1and1 is that their Apache path has an extra ‘/kunden’ directory at the start (which the PHP path doesn’t) so the RewriteCond is incorrect. The line should in fact be:

    RewriteCond "/kunden/homepages/xx/dxxxxxx/htdocs/blog/wp-content/w3tc/pgcache/$1/_index%{ENV:W3TC_UA}%{ENV:W3TC_SSL}.html%{ENV:W3TC_ENC}" -f

    There is more details of how the problem was fixed in WP Super Cache on this thread: https://www.ads-software.com/support/topic/plugin-wp-super-cache-how-to-get-mod_rewrite-working-on-1and1-shared-hosting

    This problem is obviously affecting the disk enhanced mode.
    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[Plugin: W3 Total Cache] 1and1 mod rewrite rules incorrect’ is closed to new replies.