要执行请求的操作，wordpress需要访问您的Web服务器。请输入您的ftp

将以下内容添加到wp-config.php:

 define( 'FS_METHOD', 'direct' );
 

让我知道它如何为您工作.

Add the following to wp-config.php:

define( 'FS_METHOD', 'direct' );

Let me know how it works for you.

这表示WordPress在安装文件夹中进行更改的权限有限.

为了解决此问题,您所需要做的就是为其提供必要的权限.

通过SSH连接到服务器后,在终端/腻子/命令行提示符中运行以下命令:

 sudo chown -R apache:apache /var/www/html
 

结帐这篇文章以获取详细信息.

This means that WordPress is having limited permission for making changes in the folder that it was installed.

In-order to fix this, all that you need to do is provide necessary permissions for the same.

Run the following Command in your Terminal / Putty / Commandline Prompt after connecting to your Server via SSH:

sudo chown -R apache:apache /var/www/html

Checkout this article for full details.

即使所有权为具有权限775的root:apache和httpd以apache的身份运行是完全正确的,但Wordpress并不喜欢这样.根据apache,它希望所有者是apache:

     // Attempt to determine the file owner of the WordPress files, and that of newly created files
   $wp_file_owner = $temp_file_owner = false;
   if ( function_exists('fileowner') ) {
      $wp_file_owner = @fileowner( __FILE__ );
      $temp_file_owner = @fileowner( $temp_file_name );
  }
 

您将是:
wp_file_owner=根
temp_file_owner=阿帕奇

 if ( $wp_file_owner !== false && $wp_file_owner === $temp_file_owner ) {
    // WordPress is creating files as the same owner as the WordPress files,
    // this means it's safe to modify & create new files via PHP.
    $method = 'direct';
    $GLOBALS['_wp_filesystem_direct_method'] = 'file_owner';
} elseif ( $allow_relaxed_file_ownership ) {
    // The $context directory is writable, and $allow_relaxed_file_ownership is set, this means we can modify files
    // safely in this directory. This mode doesn't create new files, only alter existing ones.
    $method = 'direct';
    $GLOBALS['_wp_filesystem_direct_method'] = 'relaxed_ownership';
}
 

如果$ wp_file_owner与$temp_file_owner相同,则继续.您的将陷入elseif中,根据注释,该elseif不允许删除/创建,而只能进行更新(我通过在Wordpress中更新插件的代码来验证了这一点,并且有效).

请注意,我没有广泛浏览代码,这只是我的快速解释.我遇到了同样的问题,当我切换user:group以便httpd用户也是文件所有者时,它不再提示输入FTP凭据.

Even though it is totally correct to have the ownership as root:apache with permissions 775, and httpd to run as apache, Wordpress does not like this. It wants the owner to be apache, as per wp-admin/includes/file.php:

    // Attempt to determine the file owner of the WordPress files, and that of newly created files
   $wp_file_owner = $temp_file_owner = false;
   if ( function_exists('fileowner') ) {
      $wp_file_owner = @fileowner( __FILE__ );
      $temp_file_owner = @fileowner( $temp_file_name );
  }

Yours would be:
wp_file_owner = root
temp_file_owner = apache

if ( $wp_file_owner !== false && $wp_file_owner === $temp_file_owner ) {
    // WordPress is creating files as the same owner as the WordPress files,
    // this means it's safe to modify & create new files via PHP.
    $method = 'direct';
    $GLOBALS['_wp_filesystem_direct_method'] = 'file_owner';
} elseif ( $allow_relaxed_file_ownership ) {
    // The $context directory is writable, and $allow_relaxed_file_ownership is set, this means we can modify files
    // safely in this directory. This mode doesn't create new files, only alter existing ones.
    $method = 'direct';
    $GLOBALS['_wp_filesystem_direct_method'] = 'relaxed_ownership';
}

If $wp_file_owner is same as $temp_file_owner then proceed. Yours would be caught in the elseif, which according to the comment does not allow delete/create, but only updates (I verified this by updating the code of a plugin from within Wordpress, and it worked).

Note I did not extensively look through the code, this is just my quick interpretation. I had the same problem and once I switched user:group so that the httpd user is also the file owner, it did not prompt for FTP credentials anymore.

这不是直接的答案,但是可能不得不说-这是您应该避免解决的一个问题,除非您正在谈论本地开发,在这种情况下,您可以将权限设置为777.

原因是,如果Web服务器可以覆盖您的代码,则在它上面运行的任何恶意代码也将能够做到这一点.风险要比不必键入ftp凭据节省几秒钟的便利大得多.

Not a direct answer, but probably has to be said - this is one problem you should avoid solving unless you are talking about a local development in which case you can just set permissions to 777.

The reason is that if the webserver can overwrite your code, then any malicious code running on it will be able to do that as well. The risk is just so much bigger than the convenience of saving few seconds by not having to type the ftp credentials.

尽管问题不再是新问题了,我还是想在这个问题上再加上两美分.

很多ppl的VPS服务器上都有Centos(7),下面的代码行可以解决他们的问题.

Imho与SELinux息息相关,SELinux阻止WordPress按要求工作.到目前为止,将解释 SELinux 是什么以及它的作用.仅供参考,介绍始于:

安全性增强Linux(SELinux)是在内核中实现的强制性访问控制(MAC)安全性机制.

只需执行以下3个步骤:

• 1打开一个终端(或通过SSH访问服务器)
• 2添加以下代码行 chcon -R -t httpd_sys_content_t/var/www/html/wordpress
• 3添加第二行代码 chcon -R -t httpd_sys_rw_content_t/var/www/html/wordpress

无需从服务器重新启动,也无需从任何守护程序重新启动.

我不会说它对所有人都有帮助,但是对于那些没有禁用SELinux的人来说,这应该是一种缓解.

欢呼

注意:请根据自己的需要进行调整(即WordPress的路径)

edit:在 wp-config.php define(" FS_METHOD"," direct"); >,因为当上述代码行按需进行时,这绝对是不可行的.

Although the question is not that new anymore I want to add my two cents on this issue also.

A lot of ppl have Centos(7) on their VPS server and following code lines could solve their problem.

Imho has all to do with SELinux which withholds WordPress from doing it's job as wished. It goes to far to explain what SELinux is and what it does. FYI the introduction starts with:

Security-Enhanced Linux (SELinux) is a mandatory access control (MAC) security mechanism implemented in the kernel.

Only 3 steps to folow:

• 1 Open a terminal (or access the server through SSH)
• 2 Add following code line chcon -R -t httpd_sys_content_t /var/www/html/wordpress
• 3 Add second code line chcon -R -t httpd_sys_rw_content_t /var/www/html/wordpress

No reboot from the server or restart from any daemon needed.

I won't say it helps everybody but for those who didn't disable SELinux it should be a relieve.

Cheers

Note: Please adjust to your own needs (meaning path to WordPress)

edit: be sure to remove the line define("FS_METHOD", "direct"); when it is/was used in wp-config.php because that's absolutely a no go when above code lines do as wanted.

对于我来说,我是通过从GIT切换回FTP模式解决的.

不再警告.

也许对其他人也有帮助.

In my case, I solved this by switching from GIT back to FTP mode.

No more warning.

Perhaps that'll help somebody else too.