Comments on: WordPress plugin upgrade explained http://www.ericbrodeur.com/blog/2009/02/15/wordpress-plugin-upgrade-explained/ Perspectives on storytelling and digital cinema technology Wed, 23 Nov 2011 05:55:23 +0000 hourly 1 http://wordpress.org/?v=3.3 By: apeiro http://www.ericbrodeur.com/blog/2009/02/15/wordpress-plugin-upgrade-explained/comment-page-1/#comment-3336 apeiro Mon, 08 Jun 2009 15:06:29 +0000 http://www.ericbrodeur.com/wp/?p=776#comment-3336 <p>This makes zero sense to me. If I have WP installed on the server, why would it ever need to FTP into itself? It already has access to the local filesystem. As long as permissions/ownership are setup correctly, WP should be able to write into it's own plugin directory, just as it can with my themes.</p> <p>Based on this fact and the lack of contextual help on that page, I'm guessing this wasn't thought out much before it was deployed.</p> This makes zero sense to me. If I have WP installed on the server, why would it ever need to FTP into itself? It already has access to the local filesystem. As long as permissions/ownership are setup correctly, WP should be able to write into it’s own plugin directory, just as it can with my themes.

Based on this fact and the lack of contextual help on that page, I’m guessing this wasn’t thought out much before it was deployed.

]]> By: Ian http://www.ericbrodeur.com/blog/2009/02/15/wordpress-plugin-upgrade-explained/comment-page-1/#comment-2955 Ian Wed, 13 May 2009 09:04:50 +0000 http://www.ericbrodeur.com/wp/?p=776#comment-2955 <p>'... and the prize for the least intuitive form goes to..' :)</p> <p>The first time I saw this, I thought it was asking for the details of the download site. </p> <p>Anyway, the other problem is that if you do give it your ftp details, and your webserver isn't running as 'you', it can break your WP setup.</p> <p>It will login as you, and get the upgraded plugin or whatever, but when it (re)creates a directory, it doesn't make it readable to other users... including the webserver. Ooops.</p> <p>Somewhere, it isn't doing a 'chmod 0755 wp-content/upgrade' or 'chmod 0755 wp-content/plugins/plugin-name'...</p> ‘… and the prize for the least intuitive form goes to..’ :)

The first time I saw this, I thought it was asking for the details of the download site.

Anyway, the other problem is that if you do give it your ftp details, and your webserver isn’t running as ‘you’, it can break your WP setup.

It will login as you, and get the upgraded plugin or whatever, but when it (re)creates a directory, it doesn’t make it readable to other users… including the webserver. Ooops.

Somewhere, it isn’t doing a ‘chmod 0755 wp-content/upgrade’ or ‘chmod 0755 wp-content/plugins/plugin-name’…

]]> By: kb http://www.ericbrodeur.com/blog/2009/02/15/wordpress-plugin-upgrade-explained/comment-page-1/#comment-2318 kb Mon, 09 Mar 2009 02:02:48 +0000 http://www.ericbrodeur.com/wp/?p=776#comment-2318 <p>Never had to deal with this bs until today when I went to upgrade a plugin. And you're correct, wp forum was worthless. Really appreciate you posting this information! Take care.</p> Never had to deal with this bs until today when I went to upgrade a plugin. And you’re correct, wp forum was worthless. Really appreciate you posting this information! Take care.

]]>