Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter pearljones

    (@pearljones)

    Does anybody else have this problem? This seems to happen when I refresh a page or revisit. It seems to me that the permalink should be displayed all the time. Will this affect me in google or feeds or anyone who bookmarks my site? Does anyone know what I should check?
    Thanks for your help

    Thread Starter pearljones

    (@pearljones)

    In case anyone would like to check it out to see if there is indeed a problem, the address is http://pearljones.com/blog. I got supercache appended to the URL in one computer but not in another so I don’t know what to make of that. This is my first blog I set up so I just want to make sure it is working OK. Thanks.

    pearljones – have you changed the mod_rewrite rules in the .htaccess? I presume it’s doing an external redirect instead of internal..

    You could also switch to “half on” mode to avoid this problem.

    Thread Starter pearljones

    (@pearljones)

    Thank you for getting back to me donncha. When I installed Supercache I made /blog and the .htaccess file writable and supercache added to it. Here is my .htaccess in /blog.

    # BEGIN WPSuperCache
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /blog/
    AddDefaultCharset UTF-8
    RewriteCond %{REQUEST_URI} !^.*[^/]$
    RewriteCond %{REQUEST_URI} !^.*//.*$
    RewriteCond %{REQUEST_METHOD} !=POST
    RewriteCond %{QUERY_STRING} !.*=.*
    RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$
    RewriteCond %{HTTP:Accept-Encoding} gzip
    RewriteCond %{DOCUMENT_ROOT}/blog/wp-content/cache/supercache/%{HTTP_HOST}/blog/$1/index.html.gz -f
    RewriteRule ^(.*) /blog/wp-content/cache/supercache/%{HTTP_HOST}/blog/$1/index.html.gz [L]

    RewriteCond %{REQUEST_URI} !^.*[^/]$
    RewriteCond %{REQUEST_URI} !^.*//.*$
    RewriteCond %{REQUEST_METHOD} !=POST
    RewriteCond %{QUERY_STRING} !.*=.*
    RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$
    RewriteCond %{DOCUMENT_ROOT}/blog/wp-content/cache/supercache/%{HTTP_HOST}/blog/$1/index.html -f
    RewriteRule ^(.*) /blog/wp-content/cache/supercache/%{HTTP_HOST}/blog/$1/index.html [L]
    </IfModule>

    # END WPSuperCache

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /blog/
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /blog/index.php [L]
    </IfModule>

    # END WordPress

    And here is my .htaccess in /blog/wp-content/cache/:

    # BEGIN supercache
    <IfModule mod_mime.c>
    AddEncoding gzip .gz
    AddType text/html .gz
    </IfModule>
    <IfModule mod_deflate.c>
    SetEnvIfNoCase Request_URI \.gz$ no-gzip
    </IfModule>
    <IfModule mod_headers.c>
    Header set Cache-Control ‘max-age=300, must-revalidate’
    </IfModule>
    <IfModule mod_expires.c>
    ExpiresActive On
    ExpiresByType text/html A300
    </IfModule>

    # END supercache

    I just let supercach create this. Can you see something wrong with it?

    Thanks for your help!

    Thread Starter pearljones

    (@pearljones)

    I think I forgot to mention that I don’t know that much about .htaccess (probably just enough to screw it up) so if you could take a look at my current .htaccess that was generated by supercache and point me in the right direction that would be great. I know you mentioned

    I presume it’s doing an external redirect instead of internal

    but you lost me there. Sorry.

    Thread Starter pearljones

    (@pearljones)

    Also, I did have this working correctly when I first setup WordPress with Supercache and permalinks. Just recently I noticed this. I did get a notification in my Dashboard the other day to upgrade to WordPress 2.7.1, which I did. I don’t know if that had anything to do with it.

    Thread Starter pearljones

    (@pearljones)

    OK, this morning I set Supercache to Half-On and the links are appearing as they should in the address bar. But why can’t I use the full Supercache? Is this a bug or something? If not, what can I do to enable the full Supercache and have it work properly?
    Thanks.

    pearljones – I have no idea why you’re seeing what you’re seeing. It might be a plugin, or a configuration issue in your blog but the rules above look ok.

    Try disabling your plugins one-by-one and testing in full mode.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘[Plugin: WP Super Cache] Supercache appended to URL’ is closed to new replies.