Droplets and their behavior

[Krzysztof M.]

Hello,
I have been using ForkLift a while, and I discovered Droplets. Really nice feature, but not working for me. Here is some my questions and thoughts to extend the program:

1. Droplets are nice feature, but why they cannot connect from itself to the server or even better remember the password and when I drop something to the droplet transer it to the destination? More I wasn't able to use the sFTP droplet even when I was connected to the server - I got UI window "Disconnected from server"?!

2. When I mount SMB share from Finder and it's visible in the ForkLift there is no "Save as Droplet..." option available. Why? For what kind of shares droplets are working than?

3. Samba is little bit shaky. Some slow downs and it is not possible to connect to SMB share using ForkLift. Also no possibility to save the destination as a Droplet.

4 OFF TOPIC: sFTP shares always asking me for password, even I have checked "Remember password in keychain". It is really annoying. Why it happens?

Thanks in advance for your information.

--
Krzysztof Maj :mad:

[Krzysztof M.]

Anybody can help me?

[csaba]

1. I don't really understand your problem here. I've tested the droplet but it does work for me, regardless whether ForkLift is running or not. In fact, the Droplet runs as an independent program once it has been created. Let me explain how it should work for you:
Once you have connected to a server (any remote server, except for local SMB and AFP shares) you can save any of the folders on that server as a droplet (using right-click + 'Save as Droplet' command). Once the Droplet is created, it will upload any file or folder you drop on it, and should do this without any intervention. It should connect to the given server and upload the file quietly in the background. If this is not what happens, than you are not doing something right. So please give me some more information on what is it that your droplets fail to do, and how you created them, because I don't fully understand the problem here.

2. Droplets are available only for volumes that are mounted as remote connections (FTP, SFTP, Amazon S3, WebDAV). Local network shares (SMB, AFP, etc) are considered local volumes in OSX, so Droplets will not work on these (since you can have a simple local shortcuts to these folders and use these for the same purpose as the droplets).

3. I thought we had settled all issues with SMB and other local shares with the 1.5.3 release. Please describe how it is shaky, and what kind of shares ForkLift fails to detect (local shares are handled by OSX, so ForkLift should see everything that OSX sees. There has been an issue in 1.5.2, but it has been corrected in the last release). You do run 1.5.3, right?

4. This seems odd. Could you please do this: delete the favorite that points to this problem SFTP, and create it again. To be honest, I think this has to do with the Keychain, not ForkLift.


And sorry for not getting back to you right away, but please understand that we're not 24/7 and sometimes we do take a day or so to get to the Forums.

[Krzysztof M.]

1. I don't really understand your problem here. I've tested the droplet but it does work for me, regardless whether ForkLift is running or not. In fact, the Droplet runs as an independent program once it has been created. Let me explain how it should work for you:
Once you have connected to a server (any remote server, except for local SMB and AFP shares) you can save any of the folders on that server as a droplet (using right-click + 'Save as Droplet' command). Once the Droplet is created, it will upload any file or folder you drop on it, and should do this without any intervention. It should connect to the given server and upload the file quietly in the background. If this is not what happens, than you are not doing something right. So please give me some more information on what is it that your droplets fail to do, and how you created them, because I don't fully understand the problem here.

2. Droplets are available only for volumes that are mounted as remote connections (FTP, SFTP, Amazon S3, WebDAV). Local network shares (SMB, AFP, etc) are considered local volumes in OSX, so Droplets will not work on these (since you can have a simple local shortcuts to these folders and use these for the same purpose as the droplets).

3. I thought we had settled all issues with SMB and other local shares with the 1.5.3 release. Please describe how it is shaky, and what kind of shares ForkLift fails to detect (local shares are handled by OSX, so ForkLift should see everything that OSX sees. There has been an issue in 1.5.2, but it has been corrected in the last release). You do run 1.5.3, right?

4. This seems odd. Could you please do this: delete the favorite that points to this problem SFTP, and create it again. To be honest, I think this has to do with the Keychain, not ForkLift.


And sorry for not getting back to you right away, but please understand that we're not 24/7 and sometimes we do take a day or so to get to the Forums.

Hello,
thank you very, very much for all your explanation and your time. It is a pleasure to have that level of information!

I have saved some droplets for sFTP connections in my work and everything was working fine, but suddenly stopped in the middle of the day. So I though that's a problem with ForkLift. So I did what you suggested to me. I deleted all my sFTP favorites starting off from the scratch. Also I have deleted all the occurrences of that accounts in my keychain. Than I set up the connection once again one by one, checking the box on remember my password. Than BOOM, when I saved some catalogue on my desktop once again everything starts working fine! I don't know what it was but now it's been working a while without any problems. Would be great to have the same for SMB shares mounted from my Vista home machine?!

Regarding Samba I have noticed that when I connect to the SMB share using Finder that SMB volume is not visible in the ForkLift. But I have noticed that only few times. Maybe I did something wrong, let me play with that little bit more and than we'll see.

Since than, all staff is working pretty well. Thank you very much once again for your information and help and even if don't work 24/7 your are awesome guys ;-) Love the app and waiting for a new version!

Keep up the good work,
Krzysztof Maj :D