[wp-trac] [WordPress Trac] #14049: Upgrade takes an hour to complete due to repeated 30-second FTP timeout

[WordPress Trac]

#14049: Upgrade takes an hour to complete due to repeated 30-second FTP timeout
--------------------------+-----------------------
 Reporter:  mmorearty     |       Owner:  dd32
     Type:  defect (bug)  |      Status:  accepted
 Priority:  normal        |   Milestone:  3.7
Component:  Filesystem    |     Version:  3.1
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |
--------------------------+-----------------------
Changes (by dd32):

 * milestone:  Future Release => 3.7


Comment:

 Went on a bit of a hunt, the latest version of ncFTPd is still affected by
 this.

 After a lot of trial and error, and looking up the sources for other FTP
 Client software, I couldn't work out how others handle this scenario. So
 much so, that I could not find a FTP server that sends 226 after a 426.
 All servers seem to send 226 for a success, 426 for a failure, couldn't
 find one that sends both (although, they DO exist).

 I've come up with an alternative though, switch from using the FTP class
 is_exists / file_exists() method, and instead, use nlist() instead (the
 same as we do for the PHP Ftp Extension), effectively bypassing the buggy
 code in question.

 This seems to work flawlessly for me.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/14049#comment:9>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software