I understand the principle of SuperCache, in that it generates static files that are served to users who aren’t logged in or have not left a comment, but when I connect to the site while logged in as the WordPress admin, why does this generate files in wp-content/cache directory in the format wp-cache-xxxxx? They too contain ‘Cached page generated by WP-Super-Cache on’ in the footer.
SuperCache seems to be doing it’s thing just fine on my site (http://iosdevgoodies.joostschuur.com). Non logged in users trigger the creation of static files under the usual hostname and URL slug based filenaming convention in the supercache folder and are then used for subsequent visits. I’m running nginx, and have the appropriate rewrite rules enabled for that web server (from http://wiki.dreamhost.com/Nginx). I just assumed that logged in users wouldn’t generate any files and wanted to make sure all is going as designed here.
Side note: The header on the settings page reads ‘Mod rewrite may not be installed!’. That’s true of course, since I’m using nginx, but I have the appropriate rewrite settings for my ngix.conf applied, so everything should be alright, correct? The plugin simply can’t detect the nginx config and that’s why the warning?
Everything seems to be working. I even modified one of the static files from the supercache folder manually and the change correctly appeared when I refreshed the page.
- The topic ‘[Plugin: WP Super Cache] Why do admin visits generate wp-cache-xxxx files?’ is closed to new replies.