v6.8 Service Pack (SP) 3 Release rev. 20627, was released 16. January 2023.

Native v6.8 changes:
- 1 Warning: Added "Warning" pop-up messages when launching a 32bit fw Client app and on the app title bar after login.
- 5 Important Other changes
- 6+ Bug fixes

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-68/SP-3/

See the full list of all logged changes on our website: https://www.farmerswife.com/releasenotes/

... and also take a look into the new highlights summary of the most recent Released version "Whats New in v6.8": https://blog.farmerswife.com/farmerswife-release-v6.8

Check out our Getting Started videos for new Advanced Users joining your team!
https://www.youtube.com/playlist?list=PLA74zQEGurSW7WY9LJqO0jWLjaQnMXxPI

---------------------------------------------------
v6.8 Service Pack (SP) 2 Release rev. 20613, was released 26. October 2022.

Native v6.8 changes:
- 1 Warning: Added "Warning" pop-up messages when launching a 32bit fw Client app and on the app title bar after login.
- 3 Features
- 6 Important Other changes
- 13+ Bug fixes

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-68/SP-2/

See the full list of all logged changes on our website: https://www.farmerswife.com/releasenotes/

... and also take a look into the new highlights summary of the most recent Released version "Whats New in v6.8": https://blog.farmerswife.com/farmerswife-release-v6.8

Check out our Getting Started videos for new Advanced Users joining your team!
https://www.youtube.com/playlist?list=PLA74zQEGurSW7WY9LJqO0jWLjaQnMXxPI

---------------------------------------------------
v6.8 Service Pack (SP) 1 Release rev. 20580, was released 24. August 2022.

Native v6.8 changes:
- 1 Warning: Added "Warning" pop-up messages when launching a 32bit fw Client app and on the app title bar after login.
- 5 Features
- 4 Important Other changes
- 23+ Bug fixes

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-68/SP-1/

See the full list of all logged changes on our website: https://www.farmerswife.com/releasenotes/

... and also take a look into the new highlights summary of the most recent Released version "Whats New in v6.8": https://blog.farmerswife.com/farmerswife-release-v6.8

Check out our Getting Started videos for new Advanced Users joining your team!
https://www.youtube.com/playlist?list=PLA74zQEGurSW7WY9LJqO0jWLjaQnMXxPI

---------------------------------------------------
v6.8 Release rev. 20523, was released 8. June 2022.

Native v6.8 changes:
- 1 Warning: Added "Warning" pop-up messages when launching a 32bit fw Client app and on the app title bar after login.
- 12 HOT Features
- 56 Features
- 40 Important Other changes
- 57+ Bug fixes

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-68/R/

See the full list of all logged changes on our website: https://www.farmerswife.com/releasenotes/

... and also take a look into the new highlights summary of the most recent Released version "Whats New in v6.8": https://blog.farmerswife.com/farmerswife-release-v6.8

Check out our Getting Started videos for new Advanced Users joining your team!
https://www.youtube.com/playlist?list=PLA74zQEGurSW7WY9LJqO0jWLjaQnMXxPI

Basics
- You need to have a "Version 6.8" license at hand, before starting the upgrade process.
- To be eligible for a v6.8 license you need to have a valid support subscription (Gold or Silver) with us, at least up to 8. June 2022 or later.

IMPORTANT:
ONLY upgrade your farmerswife (fw) system from v6.7 Service Pack 1 rev. 20130 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 support@farmerswife.com 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 macOS "64bit" Server on macOS 10.14 Mojave and later
- the Windows 64bit Server

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.

Upgrading
- 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 and finally 6.7 SP1.
- 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 since v6.6 Release:
=> Upgrade Instructions v6.8 ... these have been updated for 6.8 SP3 Release: https://support.farmerswife.com/support/solutions/articles/17000125890-upgrade-instructions-6-8
=> Client Installation Mac: https://support.farmerswife.com/en/support/solutions/articles/17000026002-client-installation-mac
=> Client Installation Windows: https://support.farmerswife.com/en/support/solutions/articles/17000026003-client-installation-on-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: https://support.farmerswife.com/support/solutions/articles/17000095590-how-to-replace-java-oracle-with-openjdk

farmerswife Server upgrade on Mac:

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

IMPORTANT:
macOS 10.14 Mojave is the only macOS on which all fw Server installers will work!
The macOS "64bit" farmerswife_Server will work ONLY on macOS 10.14 Mojave, macOS 10.15 Catalina, macOS 11.6 Big Sure, macOS Monterey 12.4 or 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.8 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 "Windows-x64-64bit_farmerswife_Server...exe" installer, available since v6.5.
On any old 32bit Windows machines the fw Client application has to be manually upgraded by using the "Legacy-Windows-x86-32bit_farmerswife_Client.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: https://support.farmerswife.com/a/solutions/articles/17000026005-server-and-client-installation-linux
- Quit the running farmerswife Server.
- Now copy the new v6.8 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.8 fw server.
- macOS (Mojave, Catalina, Big Sur or Monterey) fw Clients will perform a full install when they first connect to the upgraded v6.8 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 running a macOS version earlier than Mojave, or a Windows 32bit, or Linux your fw client apps will NOT upgrade automatically!
Use these direct download links for the farmerswife Client desktop application installers ... allow below links are pending to be updated for the Release of v6.8:

macOS 10.14 Mojave & macOS 10.15 Catalina & macOS 11.6.5 Big Sur & macOS Monterey 12.4 "64bit" fw Client: https://www.farmerswife.com/downloadsWeb/fw_client_v608_SP2.dmg

macOS Legacy 32bit Mojave or earlier fw Client https://www.farmerswife.com/downloadsWeb/fw_client_v608-SP2-32bit.dmg

Windows "64bit" fw Client: https://www.farmerswife.com/downloadsWeb/fw_client_v608-SP2.exe

Windows Legacy "32bit" fw Client: https://www.farmerswife.com/downloadsWeb/fw_client_v608-SP2-32bit.exe
=> Support will stop end of 2022!

Linux "32bit" fw Client: Please contact support@farmerswife.com 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 support@farmerswife.com; this is very important information for us which helps us to provide the best possible support for you.

The latest iOS farmerswife app is v5.0.865 and is available on Apple's App Store since 15th-December-2022.
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.

IMPORTANT:
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.857; it requires iOS 13.4 and later (ideally you're always using 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.

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.

IMPORTANT:
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:

FW_IP
FW_PORT
EXTERNAL_PORT
HTTP_PORT
HTTP_HOME
USE_SSL
HTTP_SSL_PORT
HTTP_UPLOAD_PORT
FTP_ALLOW
FTP_PORT
FTP_PASV_PORT
FILE_PORT
PROXY_FILE_PORT
FILE_PORT_LOW
FILE_PORT_HIGH
MAIL_OK
MAIL_SERVER
MAIL_PORT
MAIL_USER
MAIL_PASSWORD
USE_SQL
SQL_USER
SQL_PASS
SQL_DB_HOST
SQL_DB_NAME
SQL_PORT
PRJ_CHECK_FOLDERS
LDAP_DEBUG
HTTP_DEBUG
EXCHANGE_DEBUG
MAIL_DEBUG
BARN_ACTIVE
APNS_ENABLED
HTTP_XML_PORT
WEBCLIENT20_ENABLED
WEBCLIENT20_PORT
WEBCLIENT20_COM_PORT
ALLOW_FORCE_RUN_NIGHTLY_SCRIPT
ALLOW_FORCE_RUN_PLAY_BILLABLES
TIMED_SCRIPTS_INTERVAL_SECONDS
MSAD_ENABLED
USE_EXCHANGE
READ_SCRIPTS_AS_UTF8
GOOGLE_SYNC
A5_ENABLED
A5_URL
A5_KEY
A5_SECRET
CIRKUS_ENABLED <= This is from the legacy "Cirkus Sync v1" integration and this should always be disabled on any farmerswife system!
FORCE_SHUTDOWN
USE_MSAZUREAD
USE_THREADS
BACKUP_TIME
FULLBACKUP_CYCLES
FULLBACKUP_TIME
HTTP_HOME_ADD_WEBCLIENT_PORT
CRK_ENABLED
CRK_ORG_ID
CRK_URL
CRK_READONLY
CRK_BOOKING_SYNC_ENABLED
CRK_TR_SYNC_ENABLED
WEBCAL_ADD_WEBCLIENT_PORT
FORCE_WEBCAL_URI

These are additional settings/variables not set by default:
APNS_ENABLED
EXCHANGE_DEBUG
HTTP_DEBUG
LDAP_DEBUG

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!
FILE_PORT
PROXY_FILE_PORT

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

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:
MAIL_OK 0
USE_SQL 0
PRJ_CHECK_FOLDERS 0
APNS_ENABLED 0
MSAD_ENABLED 0
USE_EXCHANGE 0
GOOGLE_SYNC 0
CIRKUS_ENABLED 0
USE_MSAZUREAD 0
CRK_ENABLED 0

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" (https://mailtrap.io).
You then need to update this variables with your access details:
MAIL_OK
MAIL_SERVER
MAIL_PORT
MAIL_USER
MAIL_PASSWORD

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.

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.