Fixes
- Fixes a possible crash of ForkLift Mini caused by a missing macFUSE installation introduced in version 3.5
- Fixes a possible hang after uploading items to Google Drive with enabled bandwidth limit introduced in version 3.5
Fixes
If you use ForkLift 3.5, then you won't be able to update to version 3.5.1 from within ForkLift. Please download and install ForkLift 3.5.1 from here
Fixes
New
Improvements
Fixes
Fixes
New
Improvements
Fixes
We at Binarynights are planning to change how we develop and price ForkLift, and before you freak out, no, we don’t want to use subscriptions. Find out in this post what we are planning and why.
So far, we have used the one-off purchase model which means that the major releases (ForkLift 1, ForkLift 2 and ForkLift 3) were paid releases and all minor updates in between (for example ForkLift 3.3.9) were free. This is the traditional way of selling software online but it has some drawbacks for both the developers and the users.
While using the one-off purchase model, the development of the major versions has become a bigger and bigger burden for us. This model has a lot of drawbacks: every major release has to be packed full of new features to make it interesting enough for users to upgrade. That also means that big features and great new ideas don’t make it into ForkLift right away because we have to withhold them and bundle them up for the next major release. That holds the development of the current version back, and we can’t react quickly to the changes in the market and the requests of our users.
In our new model, there won’t be major and minor updates the same way as we have them now. As soon as a new feature is ready, we will release it. If we decide to implement a new feature or change something, we will start the development of it immediately. That will clearly benefit our users because they will use an app that evolves continuously. And that will benefit us too because we won’t need to maintain and develop two versions parallelly, which sometimes causes big issues. If we have to maintain only one code, we can deliver changes faster. We won’t speculate what to release and what to withhold either, so we will be able to focus on the continuous development of ForkLift without restrictions.
Changing the way we develop ForkLift means that we also have to change the way we price ForkLift.
The software industry is shifting towards the subscription business model. Subscriptions are great for developers because they secure a predictable and steady cash-flow, and they make the continuous development of the application possible. But we know that a lot of users are getting tired of subscriptions, and we also think that the subscription model is not the best fit for ForkLift.
We want to combine the advantages and minimize the disadvantages of the two extremes: the one-off purchase model and the subscription model. To do this, we want to use a hybrid model that some call the Dutch Model because it was first introduced a few years ago by mainly Dutch companies such as Sketch.
The idea behind this model is that when you buy ForkLift, you get the app and one year of free updates. After the year is over, you can renew your license and get one more year of updates, or you can keep using the same version of ForkLift forever. If you change your mind and want to use a newer version a few weeks or months later, you can renew your license any time and get all updates for another year.
If you constantly use ForkLift to upload files to your servers or you use it as your go-to file manager, then it will be worth renewing your license because you will greatly benefit from the constant enhancements. But if you only upload some files occasionally, then it might be enough to buy ForkLift once because you will be able to use a reliable FTP client for many years.
We want to lower the price of the single-user license (plus one year of free updates) to $14.95, and the renewal would cost $12.95.
We are currently working on the technical and administrative changes which are needed before we can switch over to the new model. We want to make the transition as smooth as possible.
We want to switch to the new model in a few months and release ForkLift 4 in the Spring of 2021. With increasing the version number we want to make a clear distinction between ForkLift 3 and ForkLift 4 to make the transition for our existing users easier to understand.
If you already have a ForkLift 3 license, then you will be able to use ForkLift 3 for as long as you want. Users who buy license keys to ForkLift after the introduction of the new model will get free updates for 12 months.
Nothing is set in stone, but these are our plans. We would like to hear your feedback. If you have some suggestions or ideas, please write to us at support@binarynights.com or tweet us @BinaryNights.
Fixes
New
Improvements
Fixes
We have learned that ForkLift 3 has a local security vulnerability in its helper tool which affects all previous versions. We kindly ask all users of ForkLift 3 to upgrade to version 3.4 and update the helper tool too if needed.
ForkLift version 3.4 fixes the vulnerability issue in the helper tool but updating to ForkLift version 3.4 doesn’t update the helper tool itself. After updating to version 3.4, ForkLift will ask you to update the helper tool if you had already installed it before. To allow ForkLift to install the new helper tool, enter the password of an administrator of your computer. We highly recommend updating the helper tool if you are prompted to do so.
If you don’t update the helper tool when ForkLift asks you to do it, ForkLift will keep reminding you to update the tool every time you start it. If you accidentally cancel the update, then just restart ForkLift and it will prompt you again to update the helper tool. Please don’t postpone the update of the helper tool if you are asked to update it.
If you are not prompted to update the helper tool after you have updated to ForkLift version 3.4 or later, then it means that you hadn’t installed the old version in the past and don’t need to update it. Should you allow ForkLift to install the helper tool in the future when you want to execute an action which needs elevated user privileges, ForkLift will install the new, updated helper tool.
If you have enabled the Check for updates automatically option in the Preferences of ForkLift, then ForkLift will automatically notify you about the latest update which you can easily install.
If you don’t want to wait until ForkLift sees the new update or you haven’t enabled automatic updates, then go to ForkLift > Check for Updates in the menu of ForkLift and install the latest version that way.
The ForkLift app can only be updated if it is running from the Applications folder. If you can’t update ForkLift because it is not in the Application folder, then quit ForkLift and move it into the Applications folder before trying to update it again.
If you can’t update ForkLift with the methods listed above, then quit it and move it into the Trash and download the latest version from our site by clicking on the Try for Free button on the top of the page. Make sure to move the app into the Applications folder before opening it.
Don’t forget to update the helper tool if you are prompted to do so.
In some cases, the old helper tool installed on your Mac can prevent ForkLift 3.4 from opening. If ForkLift 3.4 hangs after you have tried to open it, do the following:
sudo launchctl unload /Library/LaunchDaemons/com.binarynights.ForkLiftHelper.plist;
sudo rm /Library/LaunchDaemons/com.binarynights.ForkLiftHelper.plist;
sudo rm /Library/PrivilegedHelperTools/com.binarynights.ForkLiftHelper;
If you had been using ForkLift in the past and had installed the helper tool while using it but have deleted ForkLift since then, then the helper tool might still be on your Mac. We recommend deleting the helper tool to eliminate the vulnerability in this case too.
To delete the helper tool from your Mac, open the Terminal app, and run these 3 commands:
sudo launchctl unload /Library/LaunchDaemons/com.binarynights.ForkLiftHelper.plist;
sudo rm /Library/LaunchDaemons/com.binarynights.ForkLiftHelper.plist;
sudo rm /Library/PrivilegedHelperTools/com.binarynights.ForkLiftHelper;
You can run these commands even if you are not sure if you had installed the helper tool in the past.
It is important to mention that after deleting the old helper tool, ForkLift versions older than 3.4 will install and run the old helper tool again if you install the helper tool while using these older versions of ForkLift. To avoid possible vulnerabilities, install ForkLift version 3.4 or later if you wish to use ForkLift again.
By default, applications run as the currently logged in user. Even if you are an administrator, some tasks require additional, elevated privileges. This means that to protect your system, ForkLift doesn’t have the rights to execute some tasks such as creating an item into the root on older OS versions or creating an item into the Users directory without permission of an administrator. Apple requires to only grant these elevated privileges to an application when and as long as these elevated privileges are needed. To make this possible, developers are required to create helper tools which manage these elevated privileges. The first time you want to execute an action which needs elevated privileges, ForkLift asks you to install the helper tool and later on, the helper tool asks for an administrative password every time you want to execute actions which require elevated privileges.
New
Improvements
Fixes