The developer will be something to fix in the “broken” plug-in?
anonymized-14087207
(@anonymized-14087207)
And I still have problems fixing it so for me it is broken, without “. The directories had 777 permissions (for testing) and I still receive this error. How is that possible?
We also tried entering the directory in open_basedir without any effect. Do you have any other solutions until it’s really fixed?
The error message is misleading.
A function was added in a recent release that checks if a file can be created in the /tmp directory and if it can’t it assumes that no file (e.g. wp-config-cache.php) also can’t be modified. On a host with restrictive permissions (i.e. shared hosting) access to /tmp is probably blocked and so this function will always return false, giving the impression that no file is writable by super cache. I would definitely consider this a bug in Super Cache as it is unnecessarily breaking the plugin on many hosts.
And while that may be a problem, it is not the specific problem I have (it may be related, though).
The reason I made this thread is that file permissions on wp-config-cache.php are apparently so restrictive since updating to 1.6.1 that I can’t easily backup my site with the tar program anymore without first resetting permissions on that file so as to be readable by the regular user (user me), and not *only* by WordPress (user web). This is slightly annoying because my host does not allow that to be dealt with by simply issuing sudo chown me; chmod 664 in an SSH session.
I should add that I have the FS_CHMOD_FILE directive set to 0664 in my wp-config.php to actually avoid this problem.
For now, you need to either revert to 1.6.0 or set PHP config/environmental variables so that http://php.net/manual/de/function.sys-get-temp-dir.php returns a path that is writable by your PHP user.
The problem has been fixed. Can you try the development version at http://ocaoimh.ie/y/2o
I’ll be releasing a new version next week.
