[wp-trac] [WordPress Trac] #29610: FTPext Filesystem class can't detect isWritable, isReadable correctly

WordPress Trac noreply at wordpress.org
Tue Nov 11 02:35:36 UTC 2014


#29610: FTPext Filesystem class can't detect isWritable, isReadable correctly
----------------------------+------------------------------
 Reporter:  programmin      |       Owner:
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Filesystem API  |     Version:  2.5
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+------------------------------

Comment (by programmin):

 Replying to [comment:5 dd32]:
 > > Why not, can you please clarify?
 >
 > Quite simply because we assume that FTP access has the ability to modify
 the files. Short of attempting to write to each file, there isn't an easy
 way to cover every system.
 > If a file is chmod to 400, we'll alter it to 644 and attempt again, if
 it's 777 and a linux/windows ACL prevents write, we can't "see" that ACL
 or write to the file.

 This is not done automatically unfortunately - edit a plugin's main file's
 version line to be an old version, and give it some wrong folder
 permissions, and update breaks it.

 The wp update ''is'' doing file by file check, but ideally it could try
 chmod-ing each file to correct mode, an operation both FTP and Direct do.
 I think upgrading plugin should do the same if there isn't a way to have
 is_writable() function.

 I tried a couple filters to see where I could check for existence of
 incomplete folder while installing, but it seems there isn't a filter for
 that.

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


More information about the wp-trac mailing list