WordPress.org

Ready to get started?Download WordPress

Forums

WP Super Cache
Not caching pages for logged in users (12 posts)

  1. irishdude
    Member
    Posted 3 years ago #

    Hi,

    My WP super cache is not caching pages for logged in users.
    I have "Don’t cache pages for known users. (Recommended)" unchecked in the plugin admin, same result with it checked as unchecked. Super cache works perfect for anyone not logged in. Any idea why this would be happening? I'm refreshing the page and checking the footer time:

    <!-- Dynamic page generated in 1.058 seconds. -->
    <!-- Cached page generated by WP-Super-Cache on 2010-10-06 17:55:29 -->

    After refresh:

    <!-- Dynamic page generated in 1.078 seconds. -->
    <!-- Cached page generated by WP-Super-Cache on 2010-10-06 17:55:39 -->

    I'm running WP super cache 0.9.9.6 on WordPress 3.01

    Any help will be greatly appreciated.

    Thanks

    http://wordpress.org/extend/plugins/wp-super-cache/

  2. irishdude
    Member
    Posted 3 years ago #

    Still haven't resolved this issue. I've checked to see if editor's as well as admin's are getting cached pages when logged in and they too are getting non cached pages which is causing an extra load on my server.

    The items that I have enabled in advanced mode are:
    - Cache hits to this website for quick access. (Recommended)
    - Use mod_rewrite to serve cache files. (Recommended)
    - Compress pages so they’re served more quickly to visitors. (Recommended)
    -Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated. (Recommended)
    - Mobile device support.

    Cache content at the moment is:
    WP-Cache (23.50KB)
    0 Cached Pages
    3 Expired Pages
    WP-Super-Cache (6.18MB)
    99 Cached Pages
    0 Expired Pages

    Garbage Collection
    Last GC was 09:41 minutes ago
    Next GC in 00:19 minutes

    Is this a bug in WP-super cache?

  3. Donncha O Caoimh
    Member
    Plugin Author

    Posted 3 years ago #

    Try the debug system in the plugin. Does it give you any warnings when you browse your site as a logged in user?

  4. irishdude
    Member
    Posted 3 years ago #

    Hi Donncha,

    Thanks for your reply. I've enabled debug to a file and I get this output:

    12:45:02 / Cookie detected: wordpress_logged_in_cf38bcf430e797b75a72cd096a815346
    12:45:02 / wp-cache file exists: /var/www/vhosts/domain.com/httpdocs/wp-content/cache/wp-cache-887b1775cf4166976236d0e009c1cdec.html
    12:45:02 / couldn't load wp-cache meta file
    12:45:02 / Cookie detected: wordpress_logged_in_cf38bcf430e797b75a72cd096a815346
    12:45:02 / In WP Cache Phase 2
    12:45:02 / Setting up WordPress actions
    12:45:02 / Created output buffer
    12:45:02 / Cookie detected: wordpress_logged_in_cf38bcf430e797b75a72cd096a815346
    12:45:04 / Output buffer callback
    12:45:04 / supercache dir: /var/www/vhosts/domain.com/httpdocs/wp-content/cache/supercache/www.domain.com/
    12:45:04 / Cookie detected: wordpress_logged_in_cf38bcf430e797b75a72cd096a815346
    12:45:04 / Cookie detected: wordpress_logged_in_cf38bcf430e797b75a72cd096a815346
    12:45:04 / supercache dir: /var/www/vhosts/domain.com/httpdocs/wp-content/cache/supercache/www.domain.com/
    12:45:04 / Gzipping buffer.
    12:45:04 / Writing gzipped buffer to wp-cache cache file.
    12:45:04 / Renamed temp wp-cache file to /var/www/vhosts/domain.com/httpdocs/wp-content/cache/wp-cache-887b1775cf4166976236d0e009c1cdec.html
    12:45:04 / Writing gzip content headers. Sending buffer to browser
    12:45:04 / Writing meta file: /var/www/vhosts/domain.com/httpdocs/wp-content/cache/meta/wp-cache-887b1775cf4166976236d0e009c1cdec.meta
    12:45:04 /wp-content/plugins/wp-postviews/wp-postviews.php?_=1286455527910&postviews_id=78 Cookie detected: wordpress_logged_in_cf38bcf430e797b75a72cd096a815346
    12:45:04 /wp-content/plugins/wp-postviews/wp-postviews.php?_=1286455527910&postviews_id=78 supercache dir: /var/www/vhosts/domain.com/httpdocs/wp-content/cache/supercache/www.domain.com/wp-content/plugins/wp-postviews/wp-postviews.php/
    12:45:04 /wp-content/plugins/wp-postviews/wp-postviews.php?_=1286455527910&postviews_id=78 No wp-cache file exists. Must generate a new one.
    12:45:05 /wp-content/plugins/wp-postviews/wp-postviews.php?_=1286455527910&postviews_id=78 Cookie detected: wordpress_logged_in_cf38bcf430e797b75a72cd096a815346
    12:45:05 /wp-content/plugins/wp-postviews/wp-postviews.php?_=1286455527910&postviews_id=78 In WP Cache Phase 2
    12:45:05 /wp-content/plugins/wp-postviews/wp-postviews.php?_=1286455527910&postviews_id=78 Setting up WordPress actions
    12:45:05 /wp-content/plugins/wp-postviews/wp-postviews.php?_=1286455527910&postviews_id=78 Supercache caching disabled. Only using wp-cache. Non empty GET request.
    12:45:05 /wp-content/plugins/wp-postviews/wp-postviews.php?_=1286455527910&postviews_id=78 URI rejected. Not Caching

  5. Donncha O Caoimh
    Member
    Plugin Author

    Posted 3 years ago #

    See the error, "couldn't load wp-cache meta file" ?

    Unfortunately the plugin hides errors on writing cache files, but the meta files usually go in wp-content/cache/meta/ so make sure that directory is writeable.

  6. irishdude
    Member
    Posted 3 years ago #

    Thanks Donncha, I'll give that a go.

  7. irishdude
    Member
    Posted 3 years ago #

    The meta folder didn't have the right permissions on it so I changed that and it seemed to fix the problem.

    But now I've got another related issue. I've noticed that the cache times of the same page differ from browser to browser when logged in (tested in IE,Chrome,FF). The times are consistent when logged out, so the issue is only when logged in.

    If I refresh the page the cache time remains the same when logged in which means it is cached, but if I open another browser and log in with the same user the cache is rebuilt but is cached there after. When logged in or out of another site I've developed the times are consistent across browsers and logins. Any ideas? I've tried reinstalling and reverting to 0.9.9.3

  8. irishdude
    Member
    Posted 3 years ago #

    Just spotted when i reverted back to 0.9.9.3 in the admin settings screen I get this error just below the preload settings

    "Fatal error: Unsupported operand types in /var/www/vhosts/98fm.com/httpdocs/wp-content/plugins/wp-super-cache2/wp-cache.php on line 621"

    This error only appears when the cache is enabled, in half on or off mode the error doesn't appear.

  9. Donncha O Caoimh
    Member
    Plugin Author

    Posted 3 years ago #

    Search the archives here for that fatal error and the fix, but there shouldn't be any need to revert back to that version!

    How many of your users are logged in? Compared to visitors to your site? It's probably tiny.

  10. irishdude
    Member
    Posted 3 years ago #

    I've returned to the latest version :)

    There could be up to 15 people logged in to wp-admin at once and hundreds of visitors. I've tested it on a number of machines now and when your logged in on different browsers it generates a different cache file for each browser (the times are different on each). Logged out users get a different file as logged in users but the file is consistent from browser to browser and machine to machine.

    I'm worried that these admin users are browsing the website logged in which is why its putting an unnecessary load on the server, do you think that would be the case?

    Thanks for your help so far I really appreciate it.

  11. Donncha O Caoimh
    Member
    Plugin Author

    Posted 3 years ago #

    Ah, that's ok. Logged in users all get customized content like the comment form on each post so they need per-user cache files. I wouldn't worry about.
    The vast majority of your visitors will be served the supercache files!

  12. irishdude
    Member
    Posted 3 years ago #

    Cool thanks for your help, I just found it strange how in 0.9.9.3 when your logged in the cache files for users are the same on different browsers. So this is no longer the case on 0.9.9.6?

    Again thanks!

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic