• Hallo,

    since I moved my wordpress-blog to a new server, because it was to slow on the old shared-hosting-space, I have a problem with my WP-Super-Cache Plugin.

    I want the Plugin to deliver cached files to EVERY user, that means also to Authors and Admins. But even though I have deactivated “Don’t cache pages for known users.” it still gives fresh pages to all registered users. How can that be?

    Unknown User:
    <!– Dynamic page generated in 9.301 seconds. –>
    <!– Cached page generated by WP-Super-Cache on 2011-06-16 21:37:49 –>
    <!– Compression = gzip –>

    Login as Admin
    <!– Dynamic page generated in 8.242 seconds. –>
    <!– Cached page generated by WP-Super-Cache on 2011-06-17 09:25:27 –>
    <!– Compression = gzip –>

    After Logout Unknown User again:
    <!– Dynamic page generated in 9.301 seconds. –>
    <!– Cached page generated by WP-Super-Cache on 2011-06-16 21:37:49 –>
    <!– Compression = gzip –>

    Login as User:
    <!– Dynamic page generated in 8.644 seconds. –>
    <!– Cached page generated by WP-Super-Cache on 2011-06-17 09:26:30 –>
    <!– Compression = gzip –>

    I also wonder, why it takes our really powerfull server nearly 10 seconds to load the page…. You can find the blog here: https://blog.bergzeit.de

Viewing 2 replies - 1 through 2 (of 2 total)
  • You should probably use the debug system in the plugin. It’ll give you a good idea as to what’ happening.

    Thread Starter ValeSauer

    (@valesauer)

    Okay thanks, a already activated the debug system yesterday on level 5, so I can give you exactly the debugging-info of the requests above:

    Login as Admin:
    07:25:19 / Cookie detected: wordpress_logged_in_07c0f1ba5b8f3cefca9baf2c9c972020
    07:25:19 / supercache dir: /berbeoov/www.bergzeitblog.de/blog/wp-content/cache/supercache/blog.bergzeit.de/
    07:25:19 / Cookie detected: wordpress_logged_in_07c0f1ba5b8f3cefca9baf2c9c972020
    07:25:19 / No wp-cache file exists. Must generate a new one.
    07:25:19 / Cookie detected: wordpress_logged_in_07c0f1ba5b8f3cefca9baf2c9c972020
    07:25:19 / In WP Cache Phase 2
    07:25:19 / Setting up WordPress actions
    07:25:19 / Created output buffer
    07:25:19 / Cookie detected: wordpress_logged_in_07c0f1ba5b8f3cefca9baf2c9c972020
    07:25:27 / Output buffer callback
    07:25:27 / Cookie detected: wordpress_logged_in_07c0f1ba5b8f3cefca9baf2c9c972020
    07:25:27 / Gzipping buffer.
    07:25:27 / Writing gzipped buffer to wp-cache cache file.
    07:25:27 / Renamed temp wp-cache file to /berbeoov/www.bergzeitblog.de/blog/wp-content/cache/wp-cache-4774001cfc26fb74ef45d13ce1603c66.html
    07:25:27 / Writing gzip content headers. Sending buffer to browser
    07:25:27 / wp_cache_shutdown_callback: collecting meta data.
    07:25:27 / Writing meta file: /berbeoov/www.bergzeitblog.de/blog/wp-content/cache/meta/wp-cache-4774001cfc26fb74ef45d13ce1603c66.meta

    After Logout Unknown User again:
    07:25:49 / supercache dir: /berbeoov/www.bergzeitblog.de/blog/wp-content/cache/supercache/blog.bergzeit.de/
    07:25:49 / Served page from supercache file using PHP.

    For me it looks like the plugin simply doesn’t accept, that I don’t want it to reload the page for users with cookies. Am I right?

    The 10 seconds loading time obviously occur during generating the content in the output_buffer.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Don’t cache pages for known users – doesnt work’ is closed to new replies.