Back To Release Notes List

Back To Release Notes List
Release Notes For {{RELEASE_NAME}}

7.0 SP1

Build: 7.0.1001-0-g1dae4c28c

  • 1 Warning
  • 0 HOT Features 0 Features
  • 2 Other changes
  • 15+ Bug fixes

Welcome to v7.0 Service Pack (SP) 1 - please see the "Details" below each chapter in this "top" section of the Release Notes.

v7.0 SP1 Release was built on 2. August 2023.

Native v7.0 changes:
- 1 Warning: v6.8 was the last version to support the "32bit" apps for fw Server and fw Client, warning info was added.
- 0 HOT Features - try the New "Dark Mode"!
Get started on Dark Mode:
- 0 Features
- 2 Important Other change
- 15+ Bug fixes

See the changes specific to this version:

See the full list of all logged changes on our website:

v7.0 Release was built on 23. June 2023

Native v7.0 changes:
- 1 Warning: v6.8 was the last version to support the "32bit" apps for fw Server and fw Client, warning info was added.
- 9 HOT Features including the New "Dark Mode"
To get started on using Dark Mode:
- 61 Features
- 28 Important Other changes
- 115+ Bug fixes

See the changes specific to this version:

See the full list of all logged changes on our website:

... and also take a look into the new highlights summary of the most recent Released version "Whats New in v7.0":

Check out our Getting Started videos for new Advanced Users joining your team!

Upgrading to fw v7.0 SP1 and later - see details!

- You need to be on "Gold Support" past the date of the planned release of this version.
- You need to have a "Version 7.0" license at hand, before starting the upgrade process.
- To be eligible for a v7.0 license you need to have a valid support subscription (Gold or Silver) with us past the public release of this version.

Upgrade your farmerswife (fw) system from v6.8 Service Pack 3 rev. 20627 or from 7.0 Release and later!
If your farmerswife system is still running on older versions than v6.8 SP3, ensure you upgrade the fw Server application as per the must-do upgrade steps; contact should you require further assistance.

The fw-Client-AutoUpgrade functionality is ACTIVE in certain scenarios.

v6.8 was the last version to support the "32bit" apps for fw Server and fw Client!

Any fw Client app on Mac running BELOW macOS Mojave 10.14 can no longer be used! You have to upgrade the Mac to macOS Mojave or later in order to use the latest fw Client desktop app on Mac.

The built-in "Full Installer download" farmerswife (fw) Client auto-upgrade is active on macOS and Windows!

This built-in Full-Installer-download auto-upgrade functionality - requires local OS user permissions read, write AND execute app installers. This will be triggered upon first log-in to the already upgraded fw Server application.
This means, upon login with the fw Client Desktop app, the user has to choose a location where the installer file will be stored on the local machine ... to then automatically continue with the upgrade process.

Installers Download:

- Your farmerswife Server application must have been running on versions v6.4 SP2 and then upgraded via 6.5 Release rev. 18623, or later, then 6.6 SP2, then 6.7 SP1 and finally 6.8 SP3.
- Inform your colleagues about this new version BEFORE you upgrade.
- Run a "Full Backup" BEFORE the upgrade.
- While the Full Backup is taking place, you could now take a look into the documents provided in the "Read And Use Me Upgrade Package" you were issued together with your license of the previous Released version.
- The upgrade itself might require a couple of "Forced Shutdowns" for it to finish.

- If needed, see even more detailed information in the Upgrade Instructions on our open Knowledgebase; they are still the same as for v6.6 Release:
=> Upgrade Instructions v6.7 SP1:
=> Client Installation Mac:
=> Client Installation Windows:

- Ensure you have the Java OpenJDK version 11 installed on the fw Server app host machine, for the Web Client and Mobile Web Client to work properly and in the most secure way.
We strongly recommend to use OpenJDK; more info here:

farmerswife Server upgrade on Mac:

BEFORE you upgrade, verify which macOS version your farmerswife Server host Mac is running on!

macOS 10.14 Mojave is the only macOS on which both the legacy "32bit" and the current "64bit" fw Server installers will work!
When upgrading from fw versions below v6.8 on macOS ensure your Mac host computer is running on macOS 10.14 Mojave!

- Copy the NEW farmerswife Server package to the machine hosting the WIFE Server.
- Un-zip and rename it to include "NEW" in the package name.
- Place it in the same location as the previous running farmerswife Server.
- Quit the running WIFE Server.
- Rename the previous farmerswife Server, to include "OLD" in the package name.
- On both packages do <Control> + click and select "Show Package Contents" in the pop-up menu.
- In the OLD package select the "system" and "files" folders and use <Control> + click and select "Copy 2 Items".
- In the NEW package use <Control> + click and select "Paste 2 Items".
- Now copy the new Version 7.0 license files into the "system" of the NEW WIFE server.
- On the 1st start-up only, right-mouse click and use "Open" to launch the fw Server and allow it to run to start the actual upgrade process.
Note: The upgrade itself might require a couple of "Forced Shutdowns" for it to finish; this depends on your usage of the system.
From now on you can simply double click on the NEW farmerswife Server package icon to launch it.
- Once everything worked out fine, remove or update any Dock or Desktop links. And if needed remove the OLD Server package; because up until now, this was a working "roll-back" backup, just in case something went wrong.
- After the upgrade, start the farmerswife Server as usual.

* You might also need to copy the "html_templates" (only if used and if it contains customized templates) folder. And if you are using any 3rd party integration scripts, don't forget to manually migrate these from OLD WIFE Server package > Contents > "Show Package Contents" > lib > scripts > ... and then here only copy the integration script files from the according sub-folder and not the whole "scripts" folder.
Note: The "files" folder might not even be there, since it was broken out, to reside on some other storage device within your network.

farmerswife Server upgrade on Windows and Linux:
- Make sure you are logged into the host machine with the same "admin" user as on the initial installation of the farmerswife server application.
- Copy the NEW farmerswife Server installer file to the machine hosting the WIFE Server.
=> On Windows this is a .exe file
=> On Linux use these instructions:
- Quit the running farmerswife Server.
- Now copy the new v7.0 license files into the "system" of the NEW WIFE server.
- Double click to run the installer file in the same manner as the previous installation (for example did you use "Run As Administrator" on Windows?).
- Follow the instructions of the install wizard.
- After the upgrade, start the farmerswife Server as usual.

The farmerswife Client desktop applications can potentially use the fw Server auto-upgrade functionality...
... by using the "FULL" Client upgrade process; OS admin user permissions Read, Write AND Execute are necessary on the initial upgrade.

If your farmerswife Server is macOS 64bit (Mojave, Catalina or Big Sur) or Windows (64bit):
- Windows "64bit" fw Clients will be "auto upgraded" by using the simple-in-application-auto-upgrade when they first connect to the upgraded v6.9 Beta fw server.
- macOS (Mojave, Catalina, Big Sur, Monterey and later) fw clients will perform a full install when they first connect to the upgraded v6.9 Beta fw server, by getting the Full Installer downloaded to the local computer to then be used to Replace the existing "farmerswife64" app within the "Applications" folder.

IMPORTANT for the supported auto-upgrade functionality in later versions:
For the farmerswife Client applications on Windows the "simple in-application" auto-upgrade process to work (once supported in later versions), "normal user" Operating System permissions (Read / Write) are sufficient. You log-in, you confirm that you want to upgrade, the needed files are transferred, the WIFE Client restarts, done.

IMPORTANT when upgrading the WIFE Client on Mac: If you have a mix of Admin and Standard users on a Mac, make sure to be logged-in as a Standard user. Then after mounting the .dmg file, drag-and-drop it to the Applications folder. You then need to authenticate with the Admin users credentials! The farmerswife Client will not work for the Standard user, if installed while being logged-in as the Admin user. For the farmerswife Client applications the "simple in-application" auto-upgrade process is supported, "normal user" Operating System permissions (Read / Write) are sufficient. You log-in, you confirm that you want to upgrade, the needed files are transferred, the WIFE Client restarts, done. This upgrade process is not explained in any further detail.

Once you've successfully upgraded, please inform us by sending a short email to; this is very important information for us which helps us to provide the best possible support for you.

Latest free universal iOS farmerswife app v5.0.868 is available on Apple's App Store, click on "+" to see the details!

The latest iOS farmerswife app is v5.0.868 and it's available on Apple's App Store since 6th-July-2023.
IMPORTANT: Requires iOS 13.4 or later.

And since v5.0.840: Added new barcode-scan support for the built-in Camera on the iOS device to be used for scanning items!
This is also in response to previously working 3rd party external barcode scanner support to no longer function, as support was removed by Apple.

The previous farmerswife app v5.0.825 (available since 4-June-2018) works from iOS 9 through to iOS 12.
NOTE: iOS 9 required since iOS farmerswife app v5.0.706.
Requires farmerswife v6.1 SP1 rev 16195 and later versions!

This means:
You should upgrade as soon as possible to the latest released version.
If you can't upgrade your fw Server application to v6.1 SP1 rev 16195 or later (was released 20. July 2016), then you can't use the latest available iOS farmerswife app on iOS 8.4 or later.
You will get a "Error Failed To Connect" message.

How to install the iOS farmerswife app:
On your Apple mobile device go to the "App Store" app and search for "farmerswife"; depending on which iOS version you have installed, it will show you different iOS farmerswife app versions.
Latest iOS farmerswife app version is 5.0.840; it requires iOS 12 and later (ideally you're always on the latest iOS version).
Version 5.0.59 requires iOS 7 or later. This is the iOS 7 optimized version.
For iOS 6, the latest iOS farmerswife app is still version 5.0.34.

IMPORTANT for older versions:
The latest v5 universal iOS farmerswife app for iOS 7 or later: v5.0.59 is available on Apples App Store since 12-September-2014.
Your WIFE Server needs to be at least on version 6.1 SP1 or later to use iOS farmerswife app version v5.0.59 and later.

Running a separate TEST WIFE Server

This chapter describes the recommended best practice on working on and with a separate TEST/STAGE farmerswife (fw) Server system.
This might be needed when running on Beta versions, or new Service Packs or in general when you first want to run an upgrade check, or evaluate new modules or new functionality on a separate TEST fw Server environment.

You can always use a fw Server app in "Demo Mode" (also with your database (DB) files) and it will run for 60 min. and you have 40 sessions.
An additional "TEST fw Server" license can be provided upon request, available for customer with a valid service agreement in place;
include in your request the Company Name, the info of the local static IPv4 address and the used Operating System of the machine to host the TEST fw Server.

farmerswife supports Push and Feed functionality, and various other email notifications (if enabled); and it can be integrated to various other 3rd party systems; and you can also break out folder structures to network shares which are normally locally hosted on the fw Server's host machine, etc.
All this functionality is therefore also enabled by default on a separate new TEST fw Server environment you might be using. And if not handled with care and turned OFF in a good way, this will lead to duplicate or wrong notifications to your users, or update wrong information on your real live Production farmerswife system.
Please read on.

For a "close as possible" TEST environment, copy the "system" folder from your fw PRODUCTION Server, more info below!
Depending on how you use farmerswife, you might also need to copy other files or folders.

Use the "server.cfg" file to control certain vital parts of your separate TEST fw Server:
This "server configuration" file (server.cfg) provides the option to change certain "General tab" settings "outside" of the actual fw Server application.
You use this file to ensure certain settings are NOT enabled on your TEST fw Server BEOFRE it gets started.

These settings/variables are available by default on this version:

CIRKUS_ENABLED <= This is from the legacy "Cirkus Sync v1" integration and this should always be disabled on any farmerswife system!

These are additional settings/variables not set by default:

Since v6.4 these two settings/variables are special, because on a "standard" and "not externally proxied" fw Server installation, both of these MUST have the SAME port value!

On our "Demo DB" these settings/variables will look like this:

Note: Only licensed features and their variables will be effected by any changes within this .cfg file.

A proper fw Test installation works like this:

- Quit your farmerswife PRODUCTION Server.
- Create a file called "server.cfg" within your PRODUCTION fw Server's "system" folder.
- Start up your PRODUCTION fw Server for the first time with the "server.cfg" file in place, then Quit it again, to trigger flushing your existing configuration settings into this "server.cfg" file.
- Install the TEST fw Server application on your test machine.
- Now copy at least the "system" folder from your fw "production" Server to within your "test" fw Server's installation folder. If you have the time, feel free to also copy the "files" folder; and if you have customized anything within the "html_templates" or "/lib/scripts/...", copy these sub-folders, and IF you are using anything "customized" within these folders, the related files might need to be copied as well.

BEFORE (!!!) the first start-up of the TEST fw Server, edit the server.cfg file with a text editor application within your TEST fw Server's "system" folder and add or set at least these variables to "0", like this:

Save the server.cfg file. Copy it again to a "safe" location on your test machine, so you can re-use it for the next DB file updates. Please read on.

Now start your TEST fw Server application.

VERY IMPORTANT after the first launch and after each update of database files of a separate TEST Server
Go to the running fw Server application > Setup > General tab > "Full Backup Time" and set it to "Never"!
The "server.cfg" does not yet support this feature, and if you do not turn it off, this might interfere with your actual real "Full Backups" from your "in-production" farmerswife system!

NOTE: to test "Allow Mail" functionality from a "test" fw Server, you can use for example a service like "Mailtrap" (
You then need to update this variables with your access details:

Repeat the above steps, for any upgrade or repeated update of the "system" folder on your Test fw Server.
We recommend to save the correctly configured "server.cfg" file for the TEST environment in a good way, and then simply replace it prior to the first start-up.

NOTE: Once you have properly configured your TEST fw Server as described above, you can save time in the future by only copying these files from your PRODUCTION fw Server > from within the "system" folder:
- current45.efdb
- fwdb.db3
- histories.db3
- despatches.db3
- log.txt

... and "paste" into your TEST fw Server's "system" folder and "replace" the previous files. Then rename the fresh "log.txt" to include "date-of-copying-yyyy-mm-dd_InitialsWhoCopied_log.txt". This helps on keeping track.

About these Release Notes, Disclaimer and Legal Information

The content of this Release Notes document is subject to change without notice. The information in this document is furnished for informational use only and should not be construed as a commitment by farmerswife. farmerswife assumes no responsibility or liability for any errors or inaccuracies that may appear in this document or any software that may be provided in association with this document. Except as permitted by such license, no part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means without the express written consent of farmerswife.


v6.8 was the last version to support the "32bit" apps for fw Server and fw Client, warning info was added, see details.

See Details

v6.8 was the last version to support the 32bit apps both for the fw Server app and the fw Client app, on Windows and macOS.

Also fw Client-side platform info in fw Server logs when logging in was added.

The "Warning" pop-up message states:
"You are using the 32b it version of the farmerswife client application. Support will stop by the end of 2022. Please contact or your System Administrator to upgrade to a working system."

On the fw Client 32bit app title bar:
"Support for the 32bit app will stop by the end of 2022".




Fixed for Option Bookings wrongly not using the fw Server's colors configuration.




Added additional info to the Budgeting Actuals to be able to trace them back to Cirkus Tasks, see details.

See Details

• Budgeting: Added "Date" column to the Actuals table.
• Budgeting: Added Cirkus Task Number and Name to the Description column.


Fixed a bug preventing Actuals with Binders from getting correct Budget suggestions, see details.

See Details

If a Budget has a Binder selected, and an Actual has the same Binder set, it will pre-select the Budget in the Actuals table.
However, if you were using Sub-Binders this was broken since farmerswife 7.0 Beta 14.
It still worked for Parent Binders.
The bug is now fixed.


Fixed a bug when adding Objects to a Budget when filtering by Object Class.


Cirkus Sync

Fixed "argument list too long" bug when syncing Projects, see details.

See Details

If there was a lot of Projects data that needed to be synced to Cirkus, it could fail with the following error:
[Cirkus Sync]: Error Syncing Projects: couldn't execute "curl": argument list too long

That bug is now fixed.


Fixed "can't read method: no such variable" error, see details.

See Details

After the upgrade from fw v6.8 to v7.0, it was not able to sync existing synced Bookings, due to an error that said: "can't read "method": no such variable".
The same bug could cause errors when deleting synced Bookings.
This bug is now fixed.


Fixed an encoding issue when trying to add Users/Objects from the Object Manager on a Windows fw Client, see details.

See Details

In fw Client app > main module bar "Object Manager", you can use "Add To Cirkus" on Users/Objects in order to create them in Cirkus.
But if the User/Object or its Object Class contained special characters, such as umlauts, and the operation was performed from a Windows fw Client application, the name would be wrong on the Cirkus side. So it would not consider the User/Object/Object Class when syncing.


Fixed an error syncing Bookings, Time Reports and Tasks (as billables), if lots of Projects have been synced, see details.

See Details

If many Projects were synced between fw and Cirkus, the syncing of Bookings, Cirkus Time Reports and Tasks (as billables, using Task Template Mappings) would fail with the error: "Error Syncing Bookings: No Change Events Found In: ..." or "Error Syncing Booking Time Reports: No Change Events Found In: ..."

For the Bookings sync this was introduced in 7.0 Release, but for the others it's an older bug.


Fixed an error when syncing Bookings to Tasks in Projects, where the logged-in fw user was not a member, see details.

See Details

When fw Bookings are synced to Cirkus Tasks, the User who is logged into fw is saved as "creator" on the Cirkus Task.
However, this only worked if that User was a Member in the Task's Project in Cirkus. If not, there was an error and the Booking would not get synced.
Now it will automatically add the User to the Cirkus Project before creating the Task.


Contact Import


Fixed a bug after importing Contacts from the fw Server app's Setup, which could then not be modified.

See Details

Fixed an error that prevented Contacts being modified in the fw Client desktop app, after being imported on the fw Server-side > Setup > Contacts > "Import Contacts" feature.


Financial Report


Fixed a bug when reporting on Invoices coming from Bookings with Fixed Price, see details.

See Details

If an Invoice was created from a Class Booking that had a Fixed Price on it, and you ran a Financial Report on that Invoice, it would fail to generate report rows for it, resulting in zero Totals.
This bug was introduced in farmerswife v6.7.


Invoice Editor


Fixed multiple issues on when using "Fixed Price" on Invoices, see details.

See Details

Both in the Invoice Creator and Invoice Manager and the Invoice Report, when using the "Fixed Price" feature, the set fixed price was wrongly not saved and thus not available.
This is now fixed.


Invoice Manager


Fixed Invoice Custom Fields columns displaying wrong info in the Invoice Manager.


Object Manager / Server Setup

Fixed a bug with Object Custom Field display in Object Manager, see details.

See Details

If you had some feature's "column" enabled which was later removed from the license (e.g. Cirkus), the columns would wrongly shift the displayed information to the wrong column. This is now fixed.


Object Manager Report


Fixed a bug listing Classes' Activities twice, see details.

See Details

In the Object Manager Report, you can list the Activities for each Object. But when you did this on an Object Class, it would wrongly list each Activity twice.
This bug is now fixed.


Web & Mobile Client

Added missing "Show Password Policy Configuration" details for the "Expired Password" pop-up in Web Client and Mobile Web Client.

See Details

See also more info about "Password Policies" here:




Improved changing "Expired Password" on iOS fw app and added missing "Password Policy Configuration" details on the new "Please reset password" pop-up.

See Details

See also more info about "Password Policies" here: