radvanyi

Or even a patch here: http://lutt.se/blog/2009/01/04/patch-wordpress-automatically-upgrade-does-not-choose-direct-method.html

I even tried to hack the class-wp-filesystem-base.php file modifying the wp_content_dir() and wp_plugins_dir() to return with the hardwired absolute paths of the respective directories.
The result was – I was trying to delete a plugin through the dashboard – that I received a message: plugin(s) could not be fully deleted.
I’m getting too deep now, but still no resolution.

Otto,

Thanks a lot for your reply. Unfortunately it did not work for me.

I think I know what my absolute path and I even tried with the ABSPATH constant value.

Any more ideas?

Could you confirm that the WP auto upgrade is not working the same way as the plugin updater?

Best regards,
Tibor

Unfortunately even with the “localhost:21” I get the error message: “Plugin could not be deleted due to an error: Unable to locate WordPress Plugin directory.”

The only difference between my erroneous WP instance and an other one where this features works is that the problematic one is installed into a /blog/ directory. This might be the reason why WP is not able to find the proper plugin directory.

Do you have any suggestions?

Hi All,

I tried all the suggestions:

• Use server name as the ftp host
• Use localhost
• Use the IP Address
• Use a different browser

and I’m still not able to delete or install plugins. “Unable to locate WordPress Plugin directory.”

Do you have any other idea?

I’m afraid the WP auto upgrade might result similar issue when it’s time to upgrade WP from 2.7.