Closed (outdated)
Project:
Provision
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Apr 2011 at 22:47 UTC
Updated:
26 Feb 2016 at 14:41 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
joestewart commentedgit format-patch style patch for 7.x-2.x attached for review.
Comment #2
omega8cc commentedThe patch works as expected. Thanks!
Comment #3
anarcat commentedOkay wait here. With this patch *no* directory gets recursively chmod'd. Why don't we ditch that completely instead of having a blacklist that blacklists everything?
Comment #4
omega8cc commentedGood catch.
But maybe there was a reason we did it before that way? I can only recall from discussions with Vertice, that it was related to the remote stuff permissions issues, so maybe we should test it with remote servers first?
Comment #5
joestewart commentedIt looked to me that it was just a way of avoiding the recursive chmod on files problem, but didn't address recursive chmod on directories - http://drupal.org/node/874716#comment-3294098
After 1.2 is released I'll try to submit a cleanup without recursion for 1.x and have mostly worked through a method for 2.x with recursion that will go back to "maintaining permissions on existing directories"
That will give more time to test on remotes too.
Comment #6
ergonlogicCross-referencing: #1647830: Incorrect ownership of directories under sites/example.com/private/files/
Comment #7
helmo commentedThe 6.x-2.x branch will go EOL along with Drupal this week. So I'm closing
this issue. If it remains a confirmed issue in 7.x-3.x, feel free to re-open,
or better yet, create a new issue referencing this one.
PS: some more recent discussion: #2616426: Add 'fix permissions' task