Binarynights
Quick fix release – Restores FTP passive mode support
We have just released ForkLift 4.3.2 to quickly address a bug introduced in version 4.3.1 that made it impossible to connect to FTP servers using passive mode. We know this is an essential feature for many of you, so we worked hard to fix it as fast as possible.
Fixes
- Fixes an issue introduced in version 4.3.1 that prevented connections over FTP passive mode
- Adds the missing Edit option to the context menu of saved multi-rename favorites in the sidebar (introduced in version 4.3.1)
- Fixes an issue that prevented hiding tags from the sidebar through the tag’s context menu
Developer, may I ask where is the file location of the device configuration saved by the favorites? Due to work needs, the reading position of the ssh key needs to be changed, but the number of saved devices is too large, and it takes a lot of time to modify them one by one.
I’m posting this again because I have just realized that I didn’t post my original comment as an answer to your comment:
You can’t edit that file manually. If you have manually added the ssh keys to all of your favorites, then you have to change that manually. You can remove the shh key when you edit the favorite. I would suggest you to use the config file to tell ForkLift where the ssh keys are located. That way, you will only need to update the config file in the future when you need to change the location and not every favorite separately. The config file is located at: ~/.ssh/config
If you don’t have a config file, then create one inside the .ssh folder.
You can’t edit that file manually. If you have manually added the ssh keys to all of your favorites, then you have to change that manually. You can remove the shh key when you edit the favorite. I would suggest you to use the config file to tell ForkLift where the ssh keys are located. That way, you will only need to update the config file in the future when you need to change the location and not every favorite separately. The config file is located at: ~/.ssh/config
If you don’t have a config file, then create one inside the .ssh folder.
Hey agnesbinary,
I have still an issue with copy/paste from a RDP session through latest version of Windows App (Version 11.1.5 (2585)).
Copying a file from the RDP session and pasting it in Forklift on my local iMac makes it unreadable.
Doing the same operation but pasting it in finder works flawlessly.
May you dig this one ?
Thanks for the excellent work by the way :))
Kind regards
Richard
Thank you for bringing this up again. We are going to investigate this issue.
Hi,
On the servers I connect to, I have a limitation of only one connection at a time per user with SFTP protocol.
I have noticed that when I disconnect, the session is not actually closed and if I try to connect again the system reports that I am already currently connected.
Thank you for reporting this. We will look into it. Could you please test the same thing in ForkLift 3? https://download.binarynights.com/ForkLift3.zip and let me know if you see the same issue?
I confirm that with Forklift 3, it works perfectly. When do you plan to correct in Forklift 4?
I want to say that I am a registered user and I really like Forklift4, but I noticed another error in copying and pasting files from one panel to another:
If I select one or more files and through the right-click context menu and choose “Copy xx elements” and then right-click on a folder in the other panel and choose “Paste xx elements” the files are not saved in that specific folder.
Thank you for checking that. We will look into the issue in ForkLift 4.
We are not aware of any issues with copy-pasting items in ForkLift. Please send us a screen recording of this at support [at] binarynights [dot] com
We were able to fix the issue with the sessions. Please check the connection in the next update and let us know.
Just to get you right: I have to pay to get a fix for a problem YOU introduced yourself? I love your business-model!
I completely understand where you are coming from.
You are right: all the features in ForkLift come from us, and unfortunately, so do all the bugs. We do our best to deliver stable updates, but sometimes, an unintended issue can slip through and only get fixed in a later version.
Our licensing model is designed to let you keep using ForkLift permanently – even after your license expires – with access to all updates released during your active license period. To get future updates (which include both new features and fixes), a new license is required.
We know it is frustrating to encounter a bug in the last version your license covers, especially if the fix comes shortly after. We are aware of this edge case and are discussing how we might handle such situations more fairly going forward.
If you are stuck with version 4.3.1 and can’t update to 4.3.2, then feel free to reach out to us at support [at] binarynights [dot] com and well do our best to help you find a solution.
Unicode normalisation is still an issue, macOS uses NFD and most other operating systems are using NFC. When I upload files with non-ASCII characters and they are stored as two unicode characters (NFD) and access them via a system which expect them to be one (NFC) those files are not found.
Thank you for reminding us. This is added to our bug tracker, we will look into it.
Would a layout change beneficial ? What about inserting the preview below each left and right pane instead of displaying it on the right-hand side… (similar to the pathfinder layout)
That feature is already on our request list, but we haven’t decided yet whether we will implement it. We are still considering it and weighing the pros and cons.