Back To Release Notes List

Back To Release Notes List


1. Dec 2021

6.7 SP 1

  • 1 Warning
  • 1 Hot Feature 6 Features
  • 6 Other changes
  • 20 Bug fixes

Welcome to 6.7 SP1 - please at least read the "Details" below each chapter in this "top" section of the Release Notes.

v6.7 Service Pack (SP) 1 rev. 20130, was released 1. December 2021.

Native v6.7 SP1 changes:
- 1 Warning: fw Client upgrade enforces the Full installer-download to upgrade, Read / Write / app-install Execute OS user permissions are required
- 1 HOT Feature
- 6 Features
- 6 Important Other changes
- 20 Bug fixes

See the changes specific to this version:

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

v6.7 Release rev. 19948, was released 28. July 2021.

Native v6.7 changes:
- 1 Warning: The new "64bit" fw Server installers on Windows and Mac support the auto-upgrade for the fw Client app in certain scenarios.
- 1 HOT Features
- 13 Features
- 12 Important Other changes
- 42+ 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 v6.7":

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

Upgrading to fw 6.7 Release and later - see details!

- You need to have a "Version 6.7" license at hand, before starting the upgrade process.
- To be eligible for a v6.7 license you need to have a valid support subscription (Gold or Silver) with us, at least up to 28. July 2021 or later.

ONLY upgrade your farmerswife (fw) system from v6.7 Release rev. 19948 or later!
If your farmerswife system is still running on older versions, 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.

The built-in "Full Installer download" farmerswife (fw) Client auto-upgrade is active on:
- the NEW macOS "64bit" Server on macOS 10.14 Mojave and later
- the Windows 64bit Servers

The "64bit" fw Server installers can only serve "64bit" fw Client full installers or provide the simple in-application auto-upgrade for already upgraded "64bit" fw Clients!
Any fw Client app on Mac running BELOW macOS Mojave must be manually upgraded by using the "macOS-32bit" installer after each upgrade!

The "32bit" fw Server installers DO NOT support any auto-upgrade!

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.

- Your farmerswife Server application must have been running on versions v6.4 SP2 and then upgraded via 6.5 Release rev. 18623, or later.
- 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 (
=> Upgrade Instructions v6.7:
=> Client Installation Mac:
=> Client Installation Windows:

- Ensure you have the latest Java version (JRE on Windows/Linux, JDK on Mac OS X) installed, for the Web Client and Mobile Web Client to work properly and in the most secure way. Watch out on Windows: here you can run the fw Server application in 32bit mode (farmerswife.exe) or 64bit mode (farmerswife 64bit.exe); and depending in which mode you're running the WIFE Server, you _must_ have JRE installed in the corresponding 32bit or 64bit version.
We strongly recommend to use OpenJDK; more info here:

farmerswife Server upgrade on Mac:

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

macOS 10.14 Mojave is the only macOS on which all fw Server installers will work!
The NEW macOS "64bit" farmerswife_Server will work starting with macOS 10.14 Mojave, macOS 10.15 Catalina, macOS 11.6 Big Sur and macOS Monterey 12.0 and later!

We strongly recommend to ensure your Mac host computer is running on macOS 10.14 Mojave for the successful upgrade from previous versions!

- 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 6.7 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:
On Windows you should only be using the new "fw_server_v607.exe" installer, available since v6.5.
On any old 32bit Windows machines the fw Client application has to be manually upgraded by using the "fw_client_v607-32bit.exe" after each system upgrade.

On Linux there is still only the "Legacy-Linux64" Server installer available.

- 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 v6.7 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, Big Sur or Monterey) 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.7 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.7 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.

If your farmerswife Server or fw Clients are or running a macOS version earlier than Mojave, or a Windows 32bit, or Linux your clients will NOT upgrade automatically!
Use these direct download links for the farmerswife Client desktop application installers:
macOS 10.14 Mojave & macOS 10.15 Catalina & macOS 11.x Big Sur & 12.x Monterey "64bit" fw Client Retina optimized:

macOS 10.14 Mojave & macOS 10.15 Catalina & macOS 11.x Big Sur & 12.x Monterey "64bit" fw Client:

macOS Legacy 32bit Mojave or earlier fw Client

Windows "64bit" fw Client:

Windows Legacy "32bit" fw Client:

Linux "32bit" fw Client: Please contact if you need use the fw Client app on Linux.

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.851 is available on Apple's App Store, click on "+" to see the details!

The latest iOS farmerswife app is v5.0.851 (same as 5.0.844.7) and is available on Apple's App Store since around 26th-November-2021.
IMPORTANT: Requires iOS 13 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 6.6.
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 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 "half way realistic" 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 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:

PASSWORD_POLICIES_SRC default_password_policies.json

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.

Client Upgrade

fw Client upgrade enforces the Full installer-download to upgrade, Read / Write / app-install Execute OS user permissions are required.

See Details

This fw Client app Full-installer-download upgrade mode is required to enforce the installation of a Print Designer PDF-creation related 3rd party library.


Advanced Project Search

Added a new option to main module bar Projects search > Menu > Load View From > User, see details.

See Details

You can now load a Saved View from another user in the (Advanced) Project Search > Menu > Load View From > User.




Fixed a bug causing a fw client crash when using Booking Templates, see details.

See Details

On certain scenarios, using Booking Templates in Long Form would crash the fw client application, particularly when auto-finding Available Objects. This crash bug has been fixed.



Added "Set Sell Rate From Buy" option to contextual menu, see details.

See Details

If you select some Budget Details and right-click, there is now a new option: "Set Sell Rate From Buy..."
This new option will let you enter a markup value, in percent. Then the Sell Rate of the selected details will be set to the Buy Rate plus the entered markup.




Fixed a bug, wrongly causing fw Client to crash related to threads and curly braces.



Fixed a bug on a manual Check Out of an item that owns "Inherit Accessories From Object Class", the Accessories were wrongly added twice, see details.

See Details

If an Object has the setting active "Inherit Accessories From Object Class" it will take the Accessories that are added to its Object Class. When such an Object was added to a manual Check Out in the Dispatch module > New Check Out, the Accessories were wrongly added twice. This has now been fixed.


Financial Report

Added new fields, see details.

See Details

These new fields were added:
- Numbers: Break Name, Break Note
- Project: Container Name
- Class Booking > Involved: Duration - Booked


Added the Container Custom Fields to the Financial Report Grouping by Container in the "Custom Fields" section "Project/Media Order/Unref. Invoi...").


Added "Clear Filters?" dialog before automatically clearing Filters, see details.

See Details

With the optional "Saved Filters" feature, when you switched to a template that doesn't contain any Filters, it previously cleared all filters. Even if you had manually set some filters. Now it will ask before doing so.




Fixed a bug on manually created "overnight" Framework Bookings, wrongly causing them to get removed if timereported via the Web in a special way.




Fixed a bug sometimes making multi-selecting sticky, see details.

See Details

If you accidentally held the Command key while switching applications, farmerswife would sometimes behave as if you pressed Command even after you had released it. That caused multi-selecting bugs in Budgeting, Print Designer and in some file windows.


Invoice Manager


Fixed broken display of Custom Field values.

See Details

The table in Invoice Manager showed incorrect values for Invoice Custom Fields. That is now fixed.


Labour Rules


Fixed a bug in the PM User Report not showing Salary Additions under special circumstances, see details.

See Details

Fixed a bug in the PM User report not showing Salary Additions when a user time-reported over midnight, so that the Salary Additions would belong to the day after, which didn't have any event to draw too.


Media Library

Fixed a bug for Media Library and Media History showing Media as Checked In, when the Dispatch shows as Checked Out.

See Details

The issue with checking-in single "Media" items, of a multi-item Check Out from the Media Library. On checking-in one Media Library item, it would check in the other on the Check Out, meaning the secondary item would wrongly show as Checked In, when it was still out; both on its Media History, and when you go to check-in the other item through the legacy Dispatch module (i.e. without EMT for Object Check In/Out and tracking).


New Web Client


Updated jQuery to version 3.6.0.


Objects Tree

Bookings for the same Project across multiple days now show without "Day Markers" when this setting is unchecked in fw Client > Toolbox Settings > Display > Day Markers.


Print Designer

Re-implemented support for Underline, Umlaute, Accents and Special Characters for PDFs using the "New PDF Rendering (Beta)", see details!

See Details

For v6.7 we implemented a "New PDF Rendering (Beta)" Mode.
And we were now finally able to re-implement the support for Underline, Umlaute (ä, ö, ü, etc.), Accents (á, é, ó, etc.) and other Special Characters like the €-symbol.

Also TrueType Font Collection support has been improved, for customers using special TTF collections within the Print Designer.


Added the 6th "Print Designer Version" - now focussed on fixing wrong y position in the Elements Rows section, see details.

See Details

Go to fw Client > Toolbox > Settings > Server Setup > “Print Designer Version” by which you can select and keep using a specific version of the Print Designer, while we continue fixing and adding new versions solving other issues.

This latest “Print Designer Version: 6" is specially focussed on fixing wrong y position in the Elements Rows section, when one of the elements jumps to the next page and following ones need to start in the same position than the element that caused the page break.

Summary of all 6 “Print Designer Version" options:
1: Default "Built In PDF Printer".

2: To help when using Print Designer Templates with many "loops" and Rectangles.

3: Specially focused to fix issues on Print Designer Templates, where the Text Elements do not aligning properly after a Page Break, where this is caused by using multiple-line texts in "Loop" and "Page" positions with Rectangles causing Page Breaks.

4. Specially focused to fix issues on Print Designer Templates, where in the template's "Setup" "Show Header In Each Page" is being used. This could wrongly cause, that some Text Elements were wrongly overlapping after a Page Break.

5. Specially focused to fix issues on Page Breaks issues caused within the Total sections, when using multiline texts and many “dynamic” Total values positioned next to each text line.

6. Specially focused to fix issues on wrong y position in the Elements Rows section, when one of the elements jumps to the next page and following ones need to start in the same position than the element that caused the page break.


Implemented the next font encoding fix attempt.


Implemented unicode formalisations for the "New PDF Rendering" mode; this again requires Full Installer fwClient-upgrade mode; Read / Write / app-install Execute OS user permissions are required.



Fix at build system level to add support for Truetype Collection font files (.ttc) when printing


Fixed a bug for PDF printouts that was causing errors when using Adobe Acrobat Reader.


New PDF Printing: Fix for landscape print designer templates and printouts


PDF printing improvements

See Details

- Fixed a freeze when reading some true type font collections in New PDF Rendering (Beta)
- Improved default font usage when getting font errors at the moment of printing in New PDF Rendering (Beta)


Project Report

Fixed rendering of Object Custom Fields in the Project Report, see details.

See Details

In Project Report, Object Custom Fields showed incorrect values for certain Custom Field types.




Added a new column to the "Import Projects" feature to link a imported Project to an existing Container by using the Container Name, see details.

See Details

You need to add a new column the Project import .csv file called “Container” with the Container Names as the values. Then at the moment of importing, a new option “Container” is available in the Project Import fields mapping selectors, which needs to be set.

See more info here:


Added “Import Projects” option to fw Client > Toolbox > Settings > Server Setup.


Fixed a bug when a user opened a Project in "read-only mode", this was wrongly causing data overrides when clicking "OK" or when clicking "Save" in the Budget window.


Projects Tree

You can now Expand / Collapse all Projects loaded on the Long Form > Projects tree, see details.

See Details

It is now possible in fw Client > Long Form > Projects tree icon click > "Expand / Collapse All Loaded Projects In Tree", that allows you to expand or collapse all loaded Projects within the Project's tree.

This has also been added as a Hot Key option, in fw Client > Toolbox > Settings > Miscellaneous > Hotkeys Editor > "Expand / Collapse All Loaded Projects In Tree".


Fixed a bug wrongly causing a very long wait when expanding a Booking in the Long Form > Projects tree with +200 Objects and many Accessories.


Punch Clock

Fixed crash when activating Punch Clock and setting Start Date.

See Details

The Punch Clock feature is activated in Server Setup > Users. When you activate it, it asks if you want to set the Start Date, i.e. the date from which users are supposed to start filling in their in/out times. Clicking Yes in that dialog caused a crash that is now fixed.



Added low-level debugging info "Slow", "Very Slow" and "Very Very Slow" to the logged data on the log.txt, see details.

See Details

Should you take a look into the fw Server apps log.txt (inside the "system" folder), then you might notice "Very Very Slow" info among the data. Please feel free to send us the info to together with the fresh "Send Backup Now" from your farmerswife server app and ideally with replication steps, should you know what action within farmerswife caused the slowness.


Server Database


Implemented optimization to clean-up of failed "Notification Events", if older than 14 days.

See Details

This can cause that the size of the main database file (current45.efdb) to get reduced file size after the upgrade.




Added a tweak to stop loosing "multiple selection" in the Toolbox when toggling it using the Space key.


Previous Releases


23. Jul 2021

6.7 Release