Automatic plugin upgrade not working – ftp problems

Hi everyone, I was just having trouble too, but putting the server IP for the hostname solved the problem.

I have my WordPress at Servage.net and found out today that for me Firefox is the problem. When using Safari I have no problems with WPAU at all.

Thanks to johncolumbo’s comment, I was able to log in with localhost.
(I was also using the wrong password, so I’ll never know if the “normal” ftp host name would have worked, since I changed both fields at once.)

Cheers,

Mitch

Yup I agree with johncolumbo, anyone that may still be having this problem entering “localhost” into the ftp host box.

Anyway that is how I corrected the problem at my site.

I had the same problem here and I’ve got to agree with chiahau, at least that’s how I also corrected the problem over at my site.

Just my 0.02.

Cheers,
Christian.

Here’s a summary of the suggestions thus far:

1. Use server name as the ftp host
2. Use localhost
3. Use the IP Address
4. Use a different browser

None of these worked for me (I’m using 000webhost for hosting my blog).

Anyone have other suggestions!?

I solved it!
A friend of mine hadn’t this issue at the same hoster. So we compared our settings and find a difference: He uses PHP5, I used PHP4.

I changed it to PHP5 – et voilá … no error.

Change your PHP to version 5! (works for me…)

Thanks for your help guys, anyway ??

https://www.ads-software.com/support/topic/225836?replies=8#post-927682

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.

Ya know – instead of all this BSing around … why the hell don’t you people just forget the plugin and upload your stuff manually with FTP! You’re using FTP anyway – so just do it right and move on.

You are right, I can manage the plugins and even a whole WP upgrade manually. It’s just much easier with the built in automated functionality.

Surprisingly, using “localhost:21” as a Hostname worked for me. I had to define the port because when I didn’t, it was giving me the error:

Error: There was an error connecting to the server, Please verify the settings are correct.

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?

Try manually defining the correct constants for your FTP:
https://codex.www.ads-software.com/Editing_wp-config.php#FTP_Constants

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

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

No.. they both use the same code to connect to the server and update the files.