A few errors here when doing updates. The update fails, and yet the message at the bottom says 'your modules have been downloaded and updated' (false).
The file in questions is set to 777 file permissions, and has group set to _www which is correct for Mac I think.
A better error message would help a lot. How about:
"Unable to remove to file /Library/WebServer/Documents/drupal/modules/webform/composer.json, as it belongs to the wrong group. Should be _www, see article XYZ"
OR
"Unable to remove to file /Library/WebServer/Documents/drupal/modules/webform/composer.json, due to a file permissions issue. Currently set to 600, should he 755, see article XYZ2"
I'm getting the following error. I don't know what to do. I've given 777 for file permissions and set the group correctly (AFAIK).
webform
Error installing / updating
File Transfer failed, reason: Unable to remove to file /Library/WebServer/Documents/drupal/modules/webform/composer.json
Next steps
Your modules have been downloaded and updated.
Comments
Comment #2
CatsFromStonehenge CreditAttribution: CatsFromStonehenge commentedSecurity fail! The only way around this was to set the file permissions and all the folder permissions to 777 (i.e. full access). Full read / write access by _www is not enough. Surely Drupal runs as _www on OSX? I might need to recursively make ALL files 777! Dreadful!
Comment #3
CatsFromStonehenge CreditAttribution: CatsFromStonehenge commentedOK, so I was forced to do this. We don't seem to be using the write user on OSX to access files via drupal. It's forcing me to annihilate good security measures. Not cool.
sudo chmod -R 777 drupal/
Comment #4
cilefen CreditAttribution: cilefen commentedComment #5
cilefen CreditAttribution: cilefen commentedDocumentation is at https://www.drupal.org/docs/8/core/modules/update/overview
Comment #9
quietone CreditAttribution: quietone at PreviousNext commented@CatsFromStonehenge, Thank you for reporting this problem. We rely on issue reports like this one to resolve bugs and improve Drupal core.
There has been no activity here for 5 years, perhaps this is no longer a problem?
Is anyone experiencing this problem on a supported version of Drupal? if so, reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue (starting from "Install Drupal core").
Since we need more information to move forward with this issue, I am keeping the status at Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
Comment #11
quietone CreditAttribution: quietone at PreviousNext commentedThere hasn't been a reply here to confirm that this is still a problem. Time to close.