Live Chat Here!
RSS Feed
March 30 2018 Update Release for PointFire 2013 v1.0
Posted by Martin Laplante on 30 March 2018 12:49 PM

This release corrects several 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. It is recommended that you update only if you have encountered the resolved issues below.

Documentation is available here.  

The next update release is expected in September 2018.


Release Notes – March 30, 2018

Deploying PointFire 2013

It is recommended that you run the installation on the server where Central Administration is located, that "Microsoft SharePoint Foundation Web Application" is started on all application and all web servers before installingans that in Central Administration -> System Settings -> Manage services on server -> Microsoft SharePoint Foundation Web Application is started. Once PointFire 2013 is installed on the target server you can deploy the feature by running the PFConfiguration tool:

Start ->PointFire 2013 ->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. 
C:\Program Files\IceFire\PointFire2013
⦁ 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 2013

If you are updating an existing PointFire 2013 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 2010

If you are upgrading from a PointFire 2010 deployment, please consult the PointFire 2010 v1.0 to 2013 v1.0 Upgrade Guide.


New Features

⦁ (none)

Resolved Issues

⦁ Some characters like "<", ">", ":" separated by spaces appear in encoded form on language change if EnableDST is false (recommended setting)
⦁ On web part pages, view names displayed inside list view webparts do not translate
⦁ Some column names starting with a special character such as "%" do not translate
⦁ On malformed list templates, some drop down fields and people fields contain character sequences like ";;#" with data from another field
⦁ Errors like "Invalid URL argument" being logged into the event viewer

Known Issues
⦁ There are known combinations of settings where creation of a Document Set that includes a date can cause an error when saving. Contact support for a workaround if you encounter this.
⦁ Undocumented feature, sorting on column headers, in Manage Variations is disabled.
⦁ No “Add Un-translated Terms” and “Multilingual Site settings” popup on Site Settings and on Manage Site Features pages.


Documentation for PointFire 2013 is available to be downloaded from the following links:
PointFire 2013 Installation Guide:

PointFire 2013 Administrators Guide:

PointFire 2013 Users Guide:

PointFire 2010 v1.0 to 2013 v1.0 Upgrade Guide:

We recommend that you, or whoever you designate for support, register an account on the support site . Support can be obtained by clicking on New Ticket on the site after you login or by sending an e-mail to


Comments (0)
IceFire Home | Support Center | PointFire Home
© Copyright IceFire Studios Corp. 2019 - All Rights Reserved.