[wp-trac] [WordPress Trac] #34976: Plug ins fail to update after WP 4.4 installed

[WordPress Trac]

#34976: Plug ins fail to update after WP 4.4 installed
----------------------------+--------------------
 Reporter:  patdundee       |       Owner:
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  4.4.1
Component:  Filesystem API  |     Version:  4.4
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+--------------------

Comment (by dossy):

 It makes me sad that people think it's okay for software to violate the
 RFC.  Every part of my soul screams out with "ProFTPD users should set
 `ListOptions "-a"` and someone should file an upstream bug against ProFTPD
 to fix their buggy `NLST` behavior."  :-(

 I'd much prefer the mainline WP code be implemented towards the RFC, and
 detect the special edge cases where we support things that deviate from
 the RFC (e.g., ProFTPD) and handle then accordingly.

 On `ftp_connect()` we can issue a `FEAT` command and look for `MLST` which
 ProFTPD implements, and an `ACCT` command and look for the `502` error
 response, as [http://www.proftpd.org/docs/rfc.html ProFTPD's
 documentation] says they don't implement it (''"However, the ACCT
 (Account) command is not implemented."'').  If ProFTPD is detected, then
 `WP_Filesystem_FTPext::exists()` could use `NLST -a`.

 I'd be happy to submit a patch that implements this, if everyone agrees.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/34976#comment:62>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform