Well, you can’t upgrade the wordpress version unless you actually put the new version of WordPress on the server. That’s where FTP comes in — because files have to be transferred at one point or another (either you uploading the new version manually or your wordpress install accessing WordPress.org and getting the new file itself and uploading it onto your server).
The upgrade function was developed specifically to not need to download files locally. If you want to download files locally and upload them manually — I think you’re going to have to handle that yourself.
Thread Starter
tcurdt
(@tcurdt)
So you are saying there is FTP server access to wordpress.org and that’s what should go in there???
I am talking about plugins(!) here – not wordpress itself. Those plugins are 3rd Party. They have a HTTP URL and no FTP access.
Also I don’t really understand the reasoning behind the objective of “specifically to not need to download files locally”. Every HTTP upload (e.g. like the image upload) means creating files locally. Don’t understand what is supposed to be the problem with that.
At least it would be nice to have a “local folder” option instead of just the FTP transport.
Roy
(@gangleri)
There’re several threads about the subject from the time 2.6 was just out. I can’t get the built in updater to work either, but the One Click Plugin Updater plugin works just fine. Of course that requires one plugin uploaded ‘the old way’.
