[wp-trac] [WordPress Trac] #25714: Notices with translation upgrade

[WordPress Trac]

#25714: Notices with translation upgrade
------------------------------+--------------------
 Reporter:  GregLone          |       Owner:
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  3.7.1
Component:  Warnings/Notices  |     Version:  3.7
 Severity:  normal            |  Resolution:
 Keywords:                    |
------------------------------+--------------------

Comment (by GregLone):

 Replying to [comment:5 dd32]:
 > `755` should be high enough to allow writing to the directory when using
 the `direct` transport, since it specifically checks the ownership.
 Agree.

 > `775` would be needed when using Group Writable, and `777` would be
 needed when relying on the "everyone can write to this" check, These last
 two should only be hit in the event that someone has forced WordPress to
 use the `direct` transport even though it rightly detected it couldn't
 write to the files.
 I wasn't aware of the `775`/`777` + `direct` transport, that explains a
 lot. There's this "myth" where "if you can't upload your photos, chmod
 your content folder with `777` and put `define('FS_METHOD', 'direct');` in
 your wp-config.php, and it'll work". Lots of people do that, and I think
 some of them even chmod `777` all files/folders.

 > Our Language is_writable() checks only check `wp-content/languages`
 (well, actually wp-content since the language directory might not exist)
 is writable, it doesn't check `wp-content/languages/themes` is also
 writable.
 > How those directories were created with `755` if your other directories
 were `777` I'm not sure though, as `FS_CHMOD_DIR` should've been set to
 whatever `ABSPATH`'s permissions were.
 OK, noted, thanks.

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