[Plugin: WP Super Cache] 0.9.4.2 Not Caching; Should Cache Be Owned by ‘www’?

  • Who should be the owner/group of the Cache directory?

    I’ve been trying to install a new site today Twice, actually, so far. On both installs, Super Cache was added first thing and was apparently not caching. I.e., its little signature wasn’t appended to the bottom of files, and no cache files were created. Nothing in setup or configuration seemed to be unusual.

    However, the owner and group of the cache directory, on both installs, was “www”.
    Is that correct?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter wagerrard

    (@wagerrard)

    OK, I saw this again on a third, and brand new, WP install.

    All plugins were deactivated except Supercache. I was warned to set permission on wp-content to 777. I was warned to add th wp-cache line to wp-config.

    in setting, I used full on and compression. All other options remained at default. Both .htaccess files were either amended or created correctly.

    Advanced-cache.php and wp-cache-config. php were created in wp-content, as was the “Cache” directory. Inside the Cache directory is an emtpty “Blog” directory. (What’s it for?)

    Everything created by supercache is owned by www and in the www group.

    I logged out and repeated brought up index.php and the two pages I created. Cached files were not created.

    Cache files are created by the webserver so they’re owned by the user that runs them. Your webserver runs as the www user.

    Not sure why cache files aren’t being created. Do you have any visitors? Do you have “do no cache for logged in users” enabled?

    Thread Starter wagerrard

    (@wagerrard)

    Re: www — Thought as much, but hadn’t noticed that on previous versions.

    No visitors yet, presumably. Nothing here so far.

    I haven’t checked “no cache for logged in users”, and I checked for caching after logging out.

    Odd. It’s not producing any error messages, just not any cached files, either.

    I just tried yesterday’s release, 0.9.4.3, as well as 0.9.4.1 and 0.9.3. Same behavior.

    This is on a VPS that runs OpenSolaris. Does the code make any assumptions about the platform it’s on? I’d successfully used 0.9.3 on a shared server, also on OpenSolaris, which points, unhappily, in the direction of something in the configuration of the VPS. (E.g.: I had to ssh in as root to delete the cache directory, on each version. My FTP tool was happy to remove the two PHP files. Also, the installed permissions on Cache and the two php files were 644 on some versions, and 755 on others.)

    Anyway, thanks again for the effort you put into filling an obvious void in WP’s capabilities. Caching ought to be an opt-in alternative.

    I’m having the same problem, everything seemed to set up fine. I also have just an empty blog directory and no cached pages.

    I however am running on nginx, so it may not be related, but any help would be appreciated.

    Thread Starter wagerrard

    (@wagerrard)

    Got it working.

    I’m on a VPS.

    Buried in the vendor’s httpd.conf file for my Apache is a directive that, to paraphrase, says “ignore .htaccess files.”

    I commented that out. re-installed the latest version, and we’re all happy.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Plugin: WP Super Cache] 0.9.4.2 Not Caching; Should Cache Be Owned by ‘www’?’ is closed to new replies.