Linux.com

FTP and the updater

Posted by: Anonymous [ip: 64.223.107.223] on April 09, 2008 06:27 PM
The new auto updater for the plugins requires FTP access in order to update your plugins. The reason it asks you for your FTP info is because the updater can't find it on it's own due to FTP being disabled on your server. I don't know what your good reason for having FTP disabled is but I can't possibly think why that would be. Securing your plugins from outside access is easy enough and has nothing to do with having FTP being enabled. If I didn't have FTP access to my WordPress, upgrading and access to my site's directory structure would be that much more difficult.

"I could go research on Wordpress, as I'm sure there's a FAQ entry or a message board posting, but why didn't they just make this FTP page actually tell me a little more information!?"

There are literally hundreds of thousands of possible server configurations out there. Do you expect them to cover all? If FTP is disabled then how do you expect WP to give you more info? You can't enter a room of there's no door. And yes, you need to do the research. You own a website...that makes you a webmaster...it's your job.

You can enable FTP access to your site through your host's cPanel or the equivalent. It's not the WP dev's fault if your server doesn't meet the minimum requirements. Same with the flash uploader. It was announced that this is what 2.5 now used for uploading media although it should degrade and still properly for those browsers without flash.

My recommendation is that you upgrade to the latest Firefox and install the latest version of the Flash plugin. If you're worried about all those Flash based ads popping up in your face then install the AdBlocker extension. Sorry you have a crappy computer and old software but minimum requirements are minimum requirements. Time to think about upgrading.

Oh, for those that are finding the new admin slow to respond you probably need to check for any outdated plugins that may affect the admin itself or any plugin that might not be compatible with 2.5 (there's a list at WordPress.org). That's often the problem. Deactivate all plugins to start with and reactivate them one at a time until you find the one that's slowing you down. The new admin in all testing and the majority of user feedback is actually faster than the old one.

#

Return to The new WordPress