• I already mentioned this problem here, but the topic is marked as solved when the underlying problem is not, at least to me.

    When go to the config dialog for WP Super Cache, the permissions of the file wp-config-cache.php are reset to 400 web web, which means that only the webserver can read this file. This is not problematic for running the plugin, but creates a problem for backing up my site manually. TAR always chokes on this file because it’s not readable by the me user that programs on the server run under, and this has only been a problem since the update to WP Super Cache 1.6.1. I assume that something about the permissions to this config file was changed?

Viewing 8 replies - 1 through 8 (of 8 total)
  • The developer will be something to fix in the “broken” plug-in?

    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 messages are not useful, see

    https://www.ads-software.com/support/topic/error-in-v1-6-1-in-shared-hosting-environments-open_basedir-restriction/

    • This reply was modified 6 years, 6 months ago by testtomat.

    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.

    Thread Starter carbeck

    (@carbeck)

    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.

    I need to fix the errors

    For now, you need to either revert to 1.6.0 or set PHP config/environmental variables so that https://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 https://ocaoimh.ie/y/2o

    I’ll be releasing a new version next week.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Permissions of wp-config-cache.php’ is closed to new replies.