Setting file upload permissions

I would also expect the permissions to be 644. This is usually what Finder does. I'm very surprised that the x bit is set. What kind of file is it? Is there anything special about your server setup, like strange permissions or setgid bit on $HOME?

I have the same question. Is it possible to set and enforce default permisions for mounted drives?

I have set the server side umask to 002 (as described on http://jeff.robbins.ws/articles/setti...), and it seems to work if I create files on the mounted disk within terminal (e.g. touch test.txt), however files saved to the mounted drives by Mac OS X applications (e.g. TextEdit or TextMate) still have permissions set to 644.

Sorry about the delayed response. I do not manage our webserver so I am unaware of any strange setup. I do not know how to verify whether the setgid bit is set on something. I just upload the files and know enough about linux to get around in it.

Repi,
This is Finder's fault and unfortunately, we don't have a solution yet. Finder explicitly calls chmod 644 whenever a new file is created, so even if the initial permissions were correctly set to 664, they will be changed automatically. A fix is on our to-do list, but for now, you'll have to manually change file permissions in terminal if you need the file to be group-writable.

Astromac,
Does this happen for every file, or just a specific file or kind of file?

Matt,

I suspected as much due to the difference between files manipulated through terminal vs. by "regular" applications. I guess there should be a preference someplace that would change the default Finder behavior, but it would affect the whole system and not only the a behavior on one drive. A "fix" for enabling per drive defaults when using Finder (or Mac applications in general) would be greatly appreciated.

Thanks!

Did you see the first reply in this thread, about BatChmod? I haven't tried it myself, but it's probably worth a spin to see if does what you suggest.

Hey Matt,

I did see BatChmod. It does seem like a handy program but if this permissions issue becomes cumbersome (using 2 separate programs to upload a file) I may likely revert back to Transmit - at least for new file uploads. For the moment it is workable as most of the time I use it to edit existing files rather than upload new ones - in which case ExpanDrive performs great. I can sit in Textmate, and save all day long without getting an email alert from our server that somebody logged in as I do with Transmit. That is wonderful.

As much as I love ExpanDrive and prefer using it to Transmit, Transmit allows me to upload files, have it set permissions and even rename them once uploaded. Right now I can't do these things as effortlessly with ExpanDrive. Although, to be fair, sometimes renaming a remote file works sometimes it doesn't.

I did have a look at BatChmod. It does its job, but it is only useful after the fact, to batch change permissions. I find it easier to type in a command in terminal for that.

I have experienced this as well. I didn't have this problem before I updated a few days ago. It is frustrating, because before it was perfect.

I am getting complaints from my dev group about this as well. Would be really nice if using the Get Info command worked for changing permissions. For that matter, Get Info's ability to change the Open With property seems to not work for me either.

So far, I've been using expandrive for about a week, and I love the capability it gives me to just copy and paste from one server to another, without having to download it to my desktop and then re-upload it, like I always had to do with cyberduck. The real problem comes from the fact that I work with other people, and if everything I upload to the server gets set to 644, then I have a lot of angry co-workers telling me to give them permissions to the files. I switched over from Cyberduck, which allowed me to set a default permission on every file that was uploaded, so I never had to worry about it. Now I have to go in and change the permissions every time I do something. I switched because I thought that it might speed up my workflow, but if I have to go in through terminal every time... I'm thinking of going back to cyberduck

I would really like to get to the bottom of this, as I use ExpanDrive in a server environment where I need to be able to share with other developers. Having permissions problems is kind of a big deal.

It seems like there's a variety of sources for the problems: server-side umask, Finder behavior, ExpanDrive behavior, etc. I think it's important to get to the bottom of the interactions, and really understand why things happen the way they do.

Frankly, I don't even need ExpanDrive to completely solve the problem, if I simply could understand the behavior across multiple servers, etc., where it seems like things are different. If I knew how to work around the issues (without having to resort to a second tool), that would be good enough.

Finally, having the Permissions panel in the Finder's Get Info dialog work as one would expect is _critical_.

Would love the ability for Expandrive to be able to change file/folder permissions. Without this, it can't really replace a dedicated FTP/SFTP client (like I had wanted)

Bump.

ExpanDrive is basically useless for me if I can't control the permissions of the files. Uploaded a ton of images all ended up 700 despite parent folder set at 777. Now manually chmod ing the files, but that seems stupid.

I still use it to transfer mockups and light editing, but for anything dynamic I generally just do my heavy transferring with cyberduck to preserve permissions. While I realize this is as much (or more) of a finder issue than a Expandrive one, with how I use the app now I think I'll keep it at 1.3.4.

I noticed that the latest 2.0 upgrade has some "Finder plug-in" feature for permissions, does this apply to non-S3 accounts? How do we get this plugin?