New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cyberduck "forgets" permission bits with external editor #12001
Comments
Are you able to set the permissions on these servers using the info panel? If not the server does probably not support the CHMOD command (check the transcript) and sets the default permissions instead. |
Yes, I am able to set the permissions using the info panel, basically I have to click the file, hit Cmd-I, and fix the permissions again every time I make a change to it. Sorry, I thought I mentioned that but I didn't. |
Here is the relevant part of a log transcript. You can see that right after I hit save in my text editor and Cyberduck uploads the new version, it CHMODs the file from the previous 755 to 644. I'm using Textmate as my editor, but I just tried it out in SubEthaEdit and the same thing happens, so I don't think it's the editor. Thanks.
|
Have you check both "change permissions on upload and download" in the transfer preferences? |
I am an idiot. I'm still not clear on why this only happens to me on certain servers, but I can sort it out now that I know about those options. Sorry for wasting your time. |
There are certainly a number of biological differences between men and women. , |
On some servers, Cyberduck resets the permission bits on a file to 644 (maybe specific to the server?) when you double-click a file, edit it in your external text editor, then save it causing Cyberduck to upload the new version. So you lose any permissions you've set on the file, I notice this especially when I'm editing a shell script via Cyberduck. It doesn't appear to happen on all servers, though. This could have been pretty severe if I hadn't noticed the issue, so I'm wondering if this should have a higher severity?
The text was updated successfully, but these errors were encountered: