Live Chat Here!
RSS Feed
Latest Updates
Feb
29
PointFire 2016 v1.0 Update Release, February 29, 2024
Posted by Martin Laplante on 29 February 2024 02:06 PM

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.  

This is the last scheduled release, although support continues.

 

Release Notes – February 29, 2023


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.

C:\Program Files\IceFire\PointFire2016

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

New Features

  • none

Resolved Issues

  • Distorted image of spimn.png seen on a view page when grouped by Modified By

  • Javascript error prompts on search results page with some custom refiners

  • Blank page appears when multiple webparts in a specific sequence are present on a page

  • Possible memory leak with error messages generated in ULS logs

 

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

PointFire 2016 Installation Guide: 
http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation

PointFire 2016 Administrators Guide:

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation

PointFire 2016 Users Guide: 

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation

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

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation


Support
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 icefire@wssplus.ca

 


Read more »



Aug
31
PointFire 365 v2.6.2.0 Release
Posted by Martin Laplante on 31 August 2023 02:26 PM

PointFire 365 v2.6.2.0, August 31, 2023

This release introduces new features, including translation of Choice columns, translation of modern page titles and webpart titles using the Single Page Method.  It also allows MUI translation and Clear Cache to work if scripting is off

This is a supported official release. It can be used for production.  If you were using an earlier supported release, the upgrade requires no change to data or licenses, however you must press the "Activate" button on each site after upgrade or use the ActivateApp script. Some JavaScript from the previous version will remain cached until the next session unless you press Ctrl-F5 or equivalent on your browser.

IMPORTANT NOTICE

Starting in March 2022, all of our PowerShell scripts have switched from the legacy SharePointPnPPowerShellOnline module, which stopped being maintained in 2020, to the PnP.PowerShell module.

The PF365 installation script will uninstall the old module and install the new one on the workstation if that has not already been done. If no one has yet run the command "Register-PnPManagementShellAccess", you must get a global admin to consent for the Tenant. This only has to be done once for the entire tenant.

Details here

https://pnp.github.io/powershell/cmdlets/Register-PnPManagementShellAccess.html

 

New and Changed Features

  • Changes to the dialogue to localize choice columns. Rather than a dropdown and an "Apply" button, there is a list of choice columns each with a checkmark that applies/removes translation of choice columns. The JSON code is no longer being shown.
  • Choice column translation skips hidden and other inappropriate columns
  • Support of Azure Translator private endpoints if applicable
  • Support for forcelocale parameter to change the language within a URL
  • New script for setting PointFire365 footer option at the site collection level: SetFooterPropertyInSiteLevel.ps1
  • New script to store Azure text translation API key and region in the sitecollection level: SetAzureTranslationPropertySiteLevel.ps1
  • New script UserAuthentication.ps1 to set default authentication method to be used in other scripts
  • Changes to SetTenantLicense.ps1 to call the script 'TenantLicenseRequest.ps1', if the number of users is not valid.
  • New script to deactivate PF365 app: DeactivatePF365.ps1
  • get MTL item and its variations from the Tenant root site and parent hub site, if available
  • in DeployingMUIForSite.ps1, include Translate Interface step 1 and step 2, previously only step 3
  • PF365 now declines to make the MTL multilingual.
  • Detect whether this is an initial installation to the app catalog and skip the upgrade of the apps
  • New script SetSinglePageMethod.ps1 to indicate to PointFire that the Single Page Method will be used in a site. This can reduce performance, so it is off by default.
  • New script PF365MigrationTenantLevel.ps1 goes through all the sites of a tenant and then migrates the Item Language and Source Item columns that come from PointFire 2016 or earlier.
  • Making a list/library multilingual now adds the calculated column "ItemLanguageCalculated", which makes searching easier
  • Some scripts are now logging messages to a text file
  • Several changes to support Viva Connections

Resolved Issues

  • Language selector for Web Parts sometimes shows no languages.
  • Do not show 'display this webpart in' option for section property panel since PointFire does not support language setting for sections
  • Some UI elements not being translated when there was a large number of languages
  • Reduce the number of page loads while navigating to another site
  • Issue: Sometimes the redirected URL, for example in Quick Links, is not correct when the link contains special characters.
  • Added changes to skip the translation of read-only Content types.
  • Added changes to retrieve and apply translations in Content Type, inherited from parent site or from content type hub.
  • Personal Menu (me control) items are sometimes in the wrong language
  • Issue: In "New" and "Display" Form, the language change stuck.
  • Some view names not translated correctly.
  • Catch error in activation
  • Fixed styling for translated navigation text when it is selected
  • If we switch libraries using the new Library switcher navigation, the filter field was not getting added to the URL.
  • If choice column value contains single quote value from the beginning, then Json column is not applied successfully.
  • the installed script was first checking for tenant license and then it was again checking the license in site level.
  • While activating PointFire 365 app in a sub site, it was sometimes showing the Error : The managed path sites/demosite is not a managed path in this tenant
  • After changing the language using the Microsoft account setting rather than the language toggle or the profile, list/library was not being filtered.
  • When switching between different views, the language filtering was not automatic, need to refresh the page.
  • More issues related to old Serbian language code, and more still.
  • Improved performance for MUI translation
  • In team site, change the language to French in Home page, then navigate to multilingual Document/sitepage library, language menu is not showing, and language filtering is not working. Need to refresh the page.

 

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 almost entirely in their language, both UI and content, without using Variations.

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.

 


Read more »



Jul
14
PointFire 2019 v1.0 Update Release, July 14, 2023
Posted by Jordan Vincent on 14 July 2023 03:20 PM

This is a v1.0 update release of PointFire 2019.  It supports SharePoint classic pages as well as Modern ones.  If you received an interim release from IceFire support for testing, it must be updated with this release.  This release is an update release, with many resolved issues.

The installation package and documentation are available here.  

The next update release is expected in July 2024.

 

Release Notes – July 14, 2023

Deploying PointFire 2019

It is recommended that you run the installation on the server where Central Administration is located. Once PointFire 2019 is installed on the target server you can deploy the feature by running the PFConfiguration tool:
Start ->PointFire 2019 ->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\PointFire2019

  • 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.
PointFire 2019 also includes an optional app for modern sites.

Updating PointFire 2019
If you are updating an existing PointFire 2019 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.

Also remember to update the PointFire-2019.app in the app catalog and in the individual sites.

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.

PointFire 2019 also includes an optional app for modern sites. To add it to app catalog ur update it, you can drag and drop the pointfire-2019-sppkg file, or use the PowerShell script UploadAppToAppCatalogSite.ps1 . Then for each site, add it using the Site Contents page, or upgrade it if a previous version is already on the site, or use the scripts InstallAppFromAppCatalog.ps1 or UpgradeAppFromAppCatalog.ps1 .

Upgrading from PointFire 2016

Upgrading from a PointFire 2016 is not yet fully supported. Contact support for availability. The scripts PF2019Migration.ps1, SetWebPartLangSetting.ps1 and CallSetWebPartLangSetting.ps1 are included, but additional work is needed to complete the migration. Please note that Item Language and language variations columns have changed, so any customizations based on them will also have to be revised.

New Features

  • (none)

Resolved Issues

  • JavaScript issue when changing language on page whose URL has a case that does not match
  • Large list/library with many columns and thousands of items is slow to load in alternate language
  • Variation of classic blog post does not redirect when the language is changed
  • In modern mode, if we change the language from en to fr, then for the multilingual library, it is first filtering the page to en and then to fr
  • In modern mode, if we unfilter the list/library, then it is first reloading filtered then reloading unfiltered
  • The personal menu did not translate.
  • Invisible console error when ensuring that JavaScript file is loaded

 


Documentation
Documentation for PointFire 2019 is available to be downloaded from the following links:
PointFire 2019 Installation Guide
PointFire 2019 Administrators Guide
PointFire 2019 Users Guide

PointFire 2016 v1.0 to 2019 v1.0 Upgrade Guide:

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/142/0/pointfire-2019

 

Support

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 icefire@wssplus.ca


Read more »



Jun
16
PointFire Translator version 2.2.1.0 is released
Posted by Jordan Vincent on 16 June 2023 02:54 PM

This is a supported release.  It fixes several errors in v2.2.0 and adds several features.

It makes it simple to translate Modern pages such as the ones in Communication and Teams sites and those produced by the Multilingual Page Publishing feature, as well as classic pages, documents, lists, and metadata.  It has several interfaces, including via a SharePoint App, a web interface, scripting, and Power Automate.

IMPORTANT NOTICE

All of our PowerShell scripts have switched from the legacy SharePointPnPPowerShellOnline module, which stopped being maintained two years ago, to the new PnP.PowerShell module.  This may require global admin consent.

New Features

  • Language selection in "To" and "From" parameter in the web interface is now a datalist dropdown, with values retrieved from the site. You can select or type a language code.
  • The Azure Document Translator config should only be available if tenant and site are not configured for PointFire Translator Server, unless Azure Document Translator config was already added
  • The more detailed Microsoft Identity Extensions error message, with the useful link to the installation, will appear even if the user is translating from the app.
  • Several improvements to behaviour and error messages when the authentication wishes to open a pop-up while PointFire Translator is running as a service, where pop-ups are not allowed. MFA credentials cannot be refreshed in service mode.
  • After doing set credentials for MFA user, in future uses of Set Credentials, default will be MFA="Yes" and erase any stored userID/password information.
  • App version is shown even if PointFire Translator server is not reachable
  • New PowerShell script 'UserAuthentication.ps1' to set the Environment variable to know whether scripts should use "Interactive" or "UseWebLogin" authentication method.
  • SetLanguagePreferenceInSiteLevel.ps1 script added to override mapping of SharePoint to Translator language codes, for example "fr:fr-CA"
  • NEW Alternative authentication method for the Server using app registration and MSAL

Resolved Issues

  • Error for some users, and for some languages including Dari: Abnormal termination (Object reference not set to an instance of an object.).
  • While translating through PointFire Translator app, it sometimes opened unnecessary authentication pop up.
  • Error message "please provide valid username" at the time of pressing Submit, when MFA changes the value of the username wildcard(s)
  • Multiple errors after entering wrong site url. For MFA user, it is asking for the credential repeatedly. Otherwise, 401 error. It also changes default URL for Set Credentials to subsite URL
  • Multiple possible errors when the language is entered in upper case in Web Interface: Document failed to translate. Other error if MLP enabled or Item Language value is blank
  • Various errors and incorrect messages when translating mix of correct and incorrect file names, or mix of modern and classic pages
  • When sending one correct file name and one incorrect file name for translation, wrong message is showing "MESSAGE: Document Home.aspx already has a translation into fr-fr; skipping."
  • While translating multiple pages which contain both modern and classic pages, modern pages did not translate
  • If a user sets their language preference to a non-SharePoint language variant (not using PointFire 365) like en-CA, then Translator may try to use that language code and fail
  • Message giving the count of translated items is sometimes showing twice. Other duplicate messages
  • We are not storing the latest URL used in the SiteURL section in Translate documents/Translate SharePoint list/Translate SharePoint library
  • If we change the SiteUrl in Translate Document, then it is changing the SiteUrl in setcredential.
  • While translating a blank .xlsx file, it showed errors: "ERROR: Error while processing file: {file}.xlsx to language {lang} with error: Object reference not set to an instance of an object." "ERROR: Object reference not set to an instance of an object."
  • "Please enable custom scripting" message has not been localized.
  • In PointFire Translator app page, after clicking on the save setting button, it is not showing any success or failure mark. In the console it is showing error "l is not defined"
  • While translating the Document.docx inside a folder: "ERROR: File Document.docx cannot be found in library Documents."
  • While sending older Word format ".doc" file for translation, it showed "Error while processing the source file. The specified package is invalid. The main part is missing."
  • Classic page did not translate when Multilingual Page Publishing is enabled, but no appropriate message
  • While running SetCredential.ps1 script, found error "Unable to find type [TXFIRE.TXLIB]."
  • While doing set credential kept space after comma in user name, causing "ERROR: User name in stored credentials must match one of the authorized users in Usernames."
  • When the user name stored in Set Credentials contains a space, subsequent document translations did not succeed
  • Show blank value in the configuration parameters rather than "undefined".
  • When the service is running in Services mode, sent a document for translation to "fr" language through PointFire Translator app. It is translating to all activated language.
  • 'Error: The File does not have any content.' should be in red .
  • When the sub site URL contains a space (in tbe name), it is changing the URL in Translate Document tab, after doing translation in web interface.
  • Entering "docu" as a document name translates "Document Test.docx" which is present in the Document library.

 

PointFire Translator can translate individual items or entire libraries or lists in SharePoint Online.  It includes the PointFire Translator App which will use PointFire Translator Server as a default translation service, and fall back to Azure Translation Service if configured and if PointFire Translator is not available.

It can be downloaded here (login required)

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/146/30/pointfire-translator-server

For more information, contact sales@icefire.ca


Read more »



Mar
15
PointFire 2016 v1.0 Update Release, March 15, 2023
Posted by Martin Laplante on 15 March 2023 03:34 PM

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

 

Release Notes – March 15, 2023


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.

C:\Program Files\IceFire\PointFire2016

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

New Features

  • none

Resolved Issues

  • Digital signing and timestamping improvements

  • "All properties" page of a document set have blank values, and missing translation of column names

  • The people picker is not returning any results and keeps spinning

  • Translation in Hyperlinks not working if item value matches column name

  • Some list items were blank rather than translated 

 

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

PointFire 2016 Installation Guide: 
http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation

PointFire 2016 Administrators Guide:

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation

PointFire 2016 Users Guide: 

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation

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

http://community.icefire.ca/index.php?/Knowledgebase/Article/View/134/0/pointfire-2016-documentation


Support
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 icefire@wssplus.ca

 


Read more »




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