per eseguire l'azione richiesta, wordpress deve accedere al tuo server web. per favore inserisci il tuo ftp

Aggiungi quanto segue a wp-config.php:

 define( 'FS_METHOD', 'direct' );
 

Fammi sapere comefunzionaperte.

Add the following to wp-config.php:

define( 'FS_METHOD', 'direct' );

Let me know how it works for you.

Ciò significa che WordPress dispone di autorizzazioni limitateper apportaremodifiche alla cartellain cui è statoinstallato.

Per risolvere questoproblema,tutto ciò che devifare èfornire le autorizzazioninecessarieper lo stesso.

Eseguiil seguente comandoneltuoterminale/Putty/prompt della riga di comando dopoesserti connesso altuo servertramite SSH:

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

Checkout questo articolo peri dettagli completi.

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.

Anche se è deltutto corretto avere laproprietà come root:apache coni permessi 775e httpdperessereeseguito come apache,a Wordpressnonpiace questo. Vuole cheilproprietario sia apache,come da 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 );
  }
 

Iltuo sarebbe:
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';
}
 

Se $ wp_file_owner è uguale a $temp_file_owner alloraprocedi. Iltuo verrebbe catturatoin elseif,che secondoil commentonon consente dieliminare/creare,ma solo di aggiornare (l'ho verificato aggiornandoil codice di unplugin da Wordpress,e hafunzionato).

Nota chenon hoesaminato afondoil codice,questa è solo lamia rapidainterpretazione. Ho avuto lo stessoproblemae una volta cambiato user:groupin modo che l'utente httpdfosse ancheilproprietario delfile,nonmi sonopiù richieste le credenziali 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.

Non è una risposta diretta,maprobabilmente va detto: questo è unproblema che dovrestievitare di risolvere ameno chetunon stiaparlando di uno sviluppo locale,nel qual casopuoi semplicementeimpostarei permessi su 777.

Ilmotivo è che seil server webpuò sovrascrivereiltuo codice,anche qualsiasi codice dannosoin esecuzione su diesso saràin grado difarlo.Il rischio èmoltopiùgrande della comodità di risparmiarepochi secondinon dovendo digitare le credenzialiftp.

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.

Anche se la domandanon èpiù cosìnuova,voglio aggiungerei miei due centesimi anche su questoproblema.

Molti utenti hanno Centos (7) sulproprio server VPSe le seguenti righe di codicepotrebbero risolvereil loroproblema.

Imho hatutto a chefare con SELinux cheimpedisce a WordPress di svolgereilproprio lavoro come desiderato. Vatroppo lontanoper spiegare cosa sia SELinux e cosafa. Cordiali saluti,l'introduzioneinizia con:

Security-Enhanced Linux (SELinux) è unmeccanismo di sicurezza MAC (obbligatorioperil controllo dell'accesso)implementatonel kernel.

Solo 3passaggi da seguire:

• 1 Apri unterminale (o accedi al servertramite SSH)
• 2 Aggiungi la seguente riga di codice chcon -R -t httpd_sys_content_t/var/www/html/wordpress
• 3 Aggiungi la seconda riga di codice chcon -R -t httpd_sys_rw_content_t/var/www/html/wordpress

Nessun riavvio dal server o riavvio da qualsiasi demonenecessario.

Non dirò che aiutatutti,maper coloro chenon hanno disabilitato SELinux dovrebbeessere un sollievo.

Saluti

Nota: adattati alletueesigenze (ovveroilpercorso a WordPress)

modifica: assicurati di rimuovere la riga define ("FS_METHOD","direct"); quando è/è stata usatain wp-config.php perché è assolutamente vietato se le righe di codiceprecedentifanno come si vuole.

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.

Nelmio caso,ho risoltoilproblematornando da GIT allamodalità FTP.

Nientepiù avvisi.

Forse questo aiuterà anche qualcun altro.

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

No more warning.

Perhaps that'll help somebody else too.