This release corrects certain issues. If you received an interim release from IceFire support for testing, it must be updated with this release. This release is a bug fix release, with minor functionality changes. It is recommended that you update if you have encountered the issues that are discussed.
Documentation is available here.
The next update release is expected in March 2018.
Release Notes – October 11, 2017
Deploying PointFire 2016
It is recommended that you run the installation on the server where Central Administration is located. Once PointFire 2016 is installed on the target server you can deploy the feature by running the PFConfiguration tool:
Start ->PointFire 2016 ->PFConfig
Note: If you experience issues running the configuration tool from the shortcut, you can navigate to the PointFire directory and run PFConfig or one of the installation scripts directly.
⦁ PFConfig.exe – PointFire Deployment Manager
⦁ InstallPointFire.ps1 - to install PointFire using PowerShell.
⦁ UpgradePointFire.ps1 - Upgrade PointFire using PowerShell.
⦁ RemovePointFire.ps1 - To retract the solution using PowerShell
Note: Deploying using the scripts requires additional configuration steps. Please see the install guide for detailed information.
Updating PointFire 2016
If you are updating an existing PointFire 2016 deployment, launch the PointFire Deployment Manager and follow through the upgrade process, or retract then re-deploy PointFire, or navigate to the installation directory to run the upgrade script.
Note: If configuration keys in the web.config files have been edited manually after PFConfig initially set them, using PFConfig to update the PointFire may erase or overwrite some of those keys. For safety, note the values of the keys currently in web.config prior to updating.
Upgrading from PointFire 2013
If you are upgrading from a PointFire 2013 deployment, please consult the PointFire 2013 v1.0 to 2016 v1.0 Upgrade Guide.
- There is a new method of making sure that a user's language preference is maintained across subdomains. Please contact support for a revised configuration file if you need this feature.
- It was not possible to connect a Language Filter Webpart to a library/list manually on a web part page. The connection only worked when done automatically using PointFire ribbon icon
- Eliminated one particular source of the following error message in the event viewer "An error occured caching the Top Level Translations (CacheTopLevel): Object reference not set to an instance of an object. at PointFire2016.PFHttpModule.a(CacheObject A_0)"
- Column names are not translated on NewForm.aspx
- One class of license key was being checked incorrectly. Please note: this only affects a small number of licensees who are being contacted, but please check with firstname.lastname@example.org before installing this release in production, in case a new license key is required for you.
- This release has not been fully tested with Feature Pack 2 of SharePoint 2016. There is a possibility that machine translation may be affected by this feature pack.
- When a choice column has a default value, this default may not be correctly selected in languages other than the originalFunctionality is not complete in mobile mode.
- No “Add Un-translated Terms” and “Multilingual Site settings” popup on site settings pages.
- In some site settings pages Multilingual Translations menu options may not work for domains other than the default domain
Documentation for PointFire 2016 is available to be downloaded from the following links:
PointFire 2016 Installation Guide:
PointFire 2016 Administrators Guide:
PointFire 2016 Users Guide:
PointFire 2013 v1.0 to 2016 v1.0 Upgrade Guide:
We recommend that you, or whoever you designate for support, register an account on the support site http://community.icefire.ca/index.php?/Base/UserRegistration/Register . Support can be obtained by clicking on New Ticket on the site after you login or by sending an e-mail to email@example.com