I had my server setup that allowed me to update plugins, themes, and the kernel using nice WordPress buttons. However, after upgrading to 3.8, I was unable to update anything. However, I also added iptables to the server at about the same time, but I don't think this is a problem - I disabled iptables and tried, but had no success.
When I try to download a plugin / update via WordPress FTP, it cannot connect via localhost. Both 127.0.0.1 and the public IP return "inability to find the Wordpress content directory (wp-content)" after a long, long time, suggesting a timeout or several timeouts.
Environment:
- WP 3.8 (multi-position, subdirectory)
- Ubuntu 12.04 Server
- vsftpd (so I can FTP my user)
- Going back (when I did not know what I was doing), I changed all the permissions to / var / www / directory for gabe: gabe. Since then, I have tried changing the wp-content directory to gabe: www-data and www-data: www-data without success. I also tried using chmod 777 on wp-content, again without success.
I have googled, and the vast majority of fixes go as far as permissions. However, as I said above, I tried to change the owner and permissions to 777 for the directory. So, I think permissions are a dead end.
I initially thought iptables was somehow getting in the way. But I turned it off / could not clean the table without success. Therefore, I do not think iptables is the culprit.
googled wp-config.php. . .
Apache . , wp- -, . ftp , 127.0.0.1.
, .
------------- : , wp-config -------------
Per http://wordpress.org/support/topic/unable-to-locate-wordpress-content-directory-wp-content wp-config.php, :
if(is_admin()) {
add_filter('filesystem_method', create_function('$a', 'return "direct";' ));
define( 'FS_CHMOD_DIR', 0751 );
}
, WordPress 2.8 4 . , / , . , , WP.
, wp-config.php, :
putenv('TMPDIR='. ABSPATH .'tmp');
define('WP_TEMP_DIR', ABSPATH . 'tmp');
Per http://wordpress.org/support/topic/unable-to-locate-wordpress-content-directory-wp-content?replies=15. , , .