Live Chat Here!
RSS Feed
Latest Updates
Aug
31
PointFIre 2016 has been released!
Posted by Martin Laplante on 31 August 2016 05:39 PM

After many months in beta, PointFire 2016 for SharePoint 2016 has been released!

PointFire makes SharePoint truly multilingual and lets your users collaborate in their language.  Two different users going to the same page on the same site will each see it entirely in their language, both UI and content, without using Variations.  And when used in combination with PointFire 365, the hybrid cloud is here!

To get your copy, go to http://community.icefire.ca/index.php?/Knowledgebase/List/Index/1/pointfire-installation-packages and log in or create an account.

The fully-featured trial version can be downloaded for free and can be used for development and testing, with some pre-sale support.

We thank everyone who participated in the beta testing program for their valuable input.

 


Read more »



May
31
May 31 2016 PointFire 2013 v1.0 Update Release
Posted by Martin Laplante on 31 May 2016 05:35 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, with minor functionality changes.  It is recommended that you update.

Documentation is available here.  

The next update release is expected in August 2016.

 

Release Notes – May 31, 2016

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:

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 Promoted Links with Unicode characters not being translated
  • Some column names with Unicode characters not being translated
  • In-library search coudl throw javascript error when no search results returned
  • Setting "PFHideListSettingsMenus" in web config to TRUE does not hide the ribbon button to make list multilingual
  • Choice items in dropdowns in client-rendered add/edit form did not translate
  • Managed metadata fields from term sets sometimes appeared in the wrong language depending on browser settings.
  • On a document itme page, Document Set title did not translate
  • Custom items in "Add property restrictions" dropdown on the advanced search webpart did not translate
  • Refiner titles on search results page sometimes did not translate
    in list view webpart with a visible content type column, content type name did not translate
  • In a document library with deep folder structure, folder name in "Choose folder" dialog did not translate
  • On some updated Microsoft operating systems, the message "The signature of the program is corrupt or invalid." could appear. Microsoft is changing its code signing standards from SHA-1 to SHA-2. We are starting to use dual-signing to support highest security levels of old and new operating systems.

Known Issues

  • 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.

  • Incomplete translation of Hover Panel in search results.

     

Documentation

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

PointFire 2013 Installation Guide:

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/116/18/pointfire-2013

 

PointFire 2013 Administrators Guide:

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/116/18/pointfire-2013

 

PointFire 2013 Users Guide:

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/116/18/pointfire-2013

 

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

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/116/18/pointfire-2013


Read more »



Apr
21
November 2016, come see us in Vienna
Posted by Martin Laplante on 21 April 2016 11:14 AM

The programme for the European SharePoint Conference Nov 14-17 in Vienna, Austria, has been announced.  Like every year, we will be a conference sponsor.

This is an exciting year for SharePoint and for PointFire.  If you go to Vienna, come visit us to see the new PointFire 2016 and PointFire 365 in action.  Learn more about how PointFire's new cloud software helps make Office 365 multilingual, or learn more about how Office 365 handles languages in general.  See you there!


Read more »



Jan
15
January 14 2016 PointFire 2013 v1.0 Update Release
Posted by Martin Laplante on 15 January 2016 07:47 AM

This release corrects several issues, provides better support for Edge and other browsers, and makes PointFire run about 100 times faster than a year ago on the most common types of pages.  If you received an interim release from IceFire support for testing, it must be updated with this release.  This release is a bug fix and performance enhancement release, with minor functionality changes.  It is recommended that you update.

Documentation is available here.  

The next update release is expected in May 2016.

 

Release Notes – January 14, 2015

Deploying PointFire 2013

It is recommended that you run the installation on the server where Central Administration is located.

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 

  • Additional performance improvements if PFPerf is set to 2 instead of default value of 1. Please note: PFPerf = 2 is not yet as exhaustively tested, but it is consistently over 100 times faster than 2 versions ago.

Resolved Issues

  • On certain browsers, including the Windows 10 Edge browser, the Icefire banner on unlicensed servers was not centered correctly at the bottom of the page.
  • For web parts on search results page, while trying to save language display preference, error message "Sorry, something went wrong Trying to use an SPWeb object that has been closed or disposed and is no longer valid."
  • On libraries/lists which have been made multilingual, the ribbon was not initially visible by default unless the user clicked on the list view webpart.
  • For a site which is in 2010 compatibility mode, language preference of web parts were being ignored and web parts could be displayed in all languages irrespective of any language saved using PointFire menu.
  • When a list view name matched certain keywords, it could result in JS or CSS errors on the view page.
  • Machine translation of documents now translates document titles.
  • Post-machine-translation duplication of unique document titles handled.
  • Error message in Event log when certain invalid escape sequences were found in translation text.
  • Better error handling when using PointFire Deployment Manager (PFConfig) to update PointFire farms having multiple web applications, when using an account that has access to the configuration of one but not all of them.

Known Issues

  • 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.

  • Incomplete translation of Hover Panel in search results.

  • Some client-rendered choice column drop-down menu items not being translated after Cumulative Update. Contact support for workaround.

  • In some complex scenarios where different license keys have been used in deploying to different web applications, PointFire or PFConfig may have difficulty correctly determining which license is expired. Please contact support if a valid license is being flagged as expired.

     

 

Documentation

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

PointFire 2013 Installation Guide:

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/116/18/pointfire-2013

 

PointFire 2013 Administrators Guide:

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/116/18/pointfire-2013

 

PointFire 2013 Users Guide:

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/116/18/pointfire-2013

 

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

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/116/18/pointfire-2013


Read more »



Jul
23
July 23 2015 PointFire 2013 v1.0 Update Release
Posted by Martin Laplante on 23 July 2015 01:09 PM

Performance Breakthrough!

This release makes PointFire run 10-50 times faster on the most common types of pages.  If you received an interim release from IceFire support for testing, it must be updated with this release.  This release is a bug fix and performance enhancement release, with no new functionality beyond the ability to turn off the performance enhancement.  It is recommended that you update.

Documentation is available here.  

The next update release is expected in October 2015.

 

PointFire 2013 – v1.0 

Release Notes – July 23, 2015

 

Deploying PointFire 2013

It is recommended that you run the installation on the server where Central Administration is located.

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 

  • Performance breakthrough! 10-50 times faster on most pages that require translation.
  • Change to configuration key PFPerf (numeric) Some minor differences in the treatment of whitespace mean there is a chance some translations may not be found in some cases. PFPerf=1, faster processing, is the default. PFPerf=0 uses the old processing model. PFPerf=2 is an experimental setting, use with care.
  • When PointFire is invoked for the first time by a user, it will initially defer to the language setting logic used by SharePoint rather than following its own fixed rule.

Resolved Issues

  • If you had been told by support to change your setting to PFPerf=0, it is likely that the default setting of PFPerf=1 will now work correctly again. This change is required in order to benefit from most of the improved performance.
  • Errors when activating or deactivating PointFire feature using PowerShell or using C#.
  • Errors when restoring from the Recycle Bin.
  • Error in certain terms in the ribbon with a capital Ω.
  • Improved persistence of user's language choice if the default that is set by SharePoint is not changed.
  • Use correct language for most _layouts/15/ pages, fewer errors logged.
  • Use consistent default language when the user language is not detected or incorrect.
  • Allow more translation on managefeatures.aspx page.

Known Issues

  • 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.
  • Incomplete translation of Hover Panel in search results.
  • Activation of PointFire feature via PowerShell does not create local Multilingual Translations List.  Please request a PowerShell script workaround from support.

 

Documentation

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

PointFire 2013 Installation Guide:

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/116/18/pointfire-2013

 

PointFire 2013 Administrators Guide:

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/116/18/pointfire-2013

 

PointFire 2013 Users Guide:

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/116/18/pointfire-2013

 

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

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/116/18/pointfire-2013


Read more »




IceFire Home | Support Center | PointFire Home
© Copyright IceFire Studios Corp. 2015 - All Rights Reserved.