• i am trying to speed up https://www.trailheads.com and the super-cache plugin was working well yesterday, got me up to 98% in google site speed, but now when i review the content page, there is NO wp-super-cache content stored, and my site speed is down to 76%

    i am using the advanced rules, and the plugin seems to be working correctly, but i think i am missing something stupidly obvious

    wp super cache

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter seanskilling

    (@seanskilling)

    to add to the above-
    the advanced rules are in the htaccess file,but the advanced settings page keeps saying the rules need to be added, but it is in green as if there was no error

    the headers say the page is from super-cache – i don’t know…

    There’s a chance the plugin can’t see your .htaccess. I’m not sure why but the path to where it lives has no ending “/”. It only happens to some servers, and it didn’t happen on any of mine. Try the mod at https://github.com/Automattic/wp-super-cache/pull/306/files which should fix the problem and allow you to update the .htaccess file properly.
    You could also copy the .htaccess rules from the settings page and paste them into your .htaccess file too.

    Thread Starter seanskilling

    (@seanskilling)

    thanks! that did fix the advanced module installing correctly, but i am still not seeing super-cache files served, only wp-cache

    i have the compression option turned off, but i do have compression running in the htaccess – also, i have ExpiresActive On, but google page speed is still complaining i am not leveraging browser caching

    any thoughts to what i am doing wrong?

    Do you have HTTP header caching enabled?
    Also, enable the debug log and load a few pages as a logged out, anonymous user. That should tell you a lot about what’s happening behind the scenes!

    Thread Starter seanskilling

    (@seanskilling)

    headers are caching, but i can’t view the log, it keeps asking me to authenticate and doesn’t log in

    Thread Starter seanskilling

    (@seanskilling)

    i see 18:29:24 70086 /wp-content/plugins/jetpack/css/%22https://fonts.googleapis.com/css?family=Open+Sans%22 https://www.trailheads.com/wp-content/plugins/jetpack/css/%22https://fonts.googleapis.com/css?family=Open+Sans%22 – Page not cached by WP Super Cache. No closing HTML tag. Check your theme.

    this is coming from google fonts, is there a work-around? or is this not actually the issue?

    Thread Starter seanskilling

    (@seanskilling)

    i hate to be a pain about this, but i cannot figure out two things:
    1. i have http header caching turned off, but the cache commands are showing an expiry in 1984, and the cache control is
    Cache-Control: no-cache, must-revalidate, max-age=0

    i have caching enabled in htaccess, but it is being ignored in the wp-cache files that are being served

    2. a completely fresh browser visit gives this data in the log

    16:03:10 34027 / wp_cache_get_cookies_values: return:

    16:03:10 34027 / supercache dir: /usr/home/trailheads/public_html/wp-content/cache/supercache/www.trailheads.com/

    16:03:10 34027 / wp-cache file exists: /usr/home/trailheads/public_html/wp-content/cache/supercache/www.trailheads.com/wp-cache-0501496c6f8517ab08de3c5a0741cc27.php

    16:03:10 34027 / Serving wp-cache static file

    16:03:10 34027 / exit request

    why isn’t the supercache file going out instead?

    if you can take the minute to see what i have missed i would really appreciate it

    one thing i should note, i know you say that this is a rare bug, but when i first loaded wpsc last week, i got google page speed up to 98%, and then the page came through as unknown content type, and the zip was being zipped – i removed the plugin and reinstalled and haven’t been able to get the speed up to snuff again

    again, any help will be great!

    Thread Starter seanskilling

    (@seanskilling)

    when i look in the cache directory, there ae NO supercache files being created – the content tab shows the same info, and when i try to set up preloading, the same result – could this be the missing slash again? and the program can’t see the directory?

    From your logs, it looks like simple mode is working here but the line that sends the Cache-Control is slightly different.
    header( "Cache-Control: max-age=3, must-revalidate" );

    I don’t know where “no-cache, must-revalidate, max-age=0” is coming from.

    Thread Starter seanskilling

    (@seanskilling)

    it is coming from the htaccess in the cache directory
    should i disable this?

    # BEGIN supercache
    <IfModule mod_mime.c>
      <FilesMatch "\.html\.gz$">
        ForceType text/html
        FileETag None
      </FilesMatch>
      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 Vary "Accept-Encoding, Cookie"
      Header set Cache-Control 'max-age=3, must-revalidate'
    </IfModule>
    <IfModule mod_expires.c>
      ExpiresActive On
      ExpiresByType text/html A3
    </IfModule>
    Options -Indexes
    
    # END supercache
Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘wp-super-cache files inactive’ is closed to new replies.