PointFire 365 v3.0.0.0, October 22, 2024

This is an optional official release. It can be used for production. It adds few new features and corrects some issues. Although it has little new functionality, it makes major changes to the user interface.  PointFire 365 is phasing out the "PointFire 365" add-in and putting all functionality into the "PointFire 365 Modern" app.

If this is a new install, you will only need the "PointFire 365 Modern" app, not the "PointFire 365" add-in. It you are updating an existing install, you will still need both, as part of the transition to eliminating the add-in before Microsoft's April 2026 deadline. All configuration functionality has been moved from PointFire 365" to PointFire 365 Modern", and all PointFire screens are now side panels.

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

All of our PowerShell scripts use the PnP.PowerShell module. The PF365 installation script will install it if that has not already been done.  In addition, Microsoft has recently deleted the app registration on which the "Interactive" login relies.  You can run UserAuthentication.ps1 to create a new app registration in your own tenant, or to change authentication methods

Details here
https://github.com/pnp/powershell/issues/4250

New and Changed Features

• Installation installs both apps in upgrades of previous versions, but not in new installs.
• Clicking PointFire 365 in Site Contents now only explains that configuration has moved to PointFire 365 Modern
• Clicking PointFire 365 Modern in Site Contents brings up configuration, now in a side panel
• All former PointFire 365 pages and pop-ups are now side panels

Resolved Issues

• All scripts now work in both PowerShell 5 and PowerShell 7. PowerShell 7 is recommended and will become mandatory in a future release. 

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.

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.

PointFire 365 v2.7.2.0, September 20, 2024

This is a recommended official release.  It can be used for production.  It adds a new feature and corrects many issues.

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

All of our PowerShell scripts use the PnP.PowerShell module. The PF365 installation script will install it if that has not already been done.  In addition, Microsoft has recently deleted the app registration on which the "Interactive" login relies.  You can run UserAuthentication.ps1 to create a new app registration in your own tenant, or to change authentication methods

Details here
https://github.com/pnp/powershell/issues/4250

New and Changed Features

• Translation of items in submenus of Footer links is now supported
• UserAuthentication.ps1 now creates create an app registration in Azure, named "PointFire PnP login" to overcome the deletion of the PnP group's multi-tenant application that "Interactive" login relies on.

Resolved Issues

• In MUI 2 when translating text with certain characters, strings were untranslated or had low-quality translations
• In MUI 2 when certain characters are present error "The body of the request is not valid JSON."
• In MUI 3 when translating certain strings including those in the Asset Manager list template, error "{Culture is not supported. Parameter name: <text> is an invalid culture identifier.}
   

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.

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.

This is a supported release.  It fixes several errors in v2.2.1 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 require the new PnP.PowerShell module.  installing the latest version may require global admin consent.  In addition, Microsoft has recently deleted the app registration on which the "Interactive" login relies.  You can run UserAuthentication.ps1 to create a new app registration in your own tenant, or to change authentication methods

New and Changed Features

• Custom connector has new Advanced Parameters: To, From, Publish, IsFileNameToTranslate
• Custom connector to translate list items
• Store the settings and credentials so they are not user-specific
• Pre-populate credentials, keys, etc in Set Credentials so they don't need to be re-entered every time.
• Appropriate message when the Service is not running
• Remove the abililty for PointFire Translator Add-In to work without PointFire Translator Server. Use PointFire Translator Express instead
• Improved troubleshooting for add-in connection to server
• Translation is now possible with contribute rather than edit permission
• UserAuthentication.ps1  script can create the necessary app registtration in the tenant to replace the multi-tenant app registration that PnP deleted on Sept 8 2024

Resolved Issues

• Set Credentials is stuck for MFA
• Target page content is blank if there is a double quotation in the source page title.
• When translating items with special characters which is not the source file, the message is not showing properly.
• Changes for installing PnP.PowerShell version 1.12.0 in script
• Use -Interactive -ForceAuthentication instead of -UseWebLogin in Connect-PnPOnline
• While translating Visio file getting the Error: System.Runtime.InteropServices.COMException (0x86DB03E7)
• Added support for new lanugagea including Bhojpuri
• Set the correct file version and preserve file version history history after translation
• SP Quick Links web parts containing links with MSTrans.dic terms not rendered correctly during translation
• 429 error more retries until timeout reaches 60 seconds.
• Messages improvements for error 429000, 429001, and 429003
• Error messages when translating very large pages.
• Some pages are sent for translation twice. Also the message shown for successful translations are printed twice.
• Translation service not working on some browsers when using self-signed SSL certificate
• Error 429 (throttling) when using free version ot Azure AI Translator
• After providing correct appcatalog url, it is showing "incorrect appcatalog url" in PointFireTranslatorInstaller.ps1
• SharePoint Page translation using source language other than EN produced non-translated pages
• "The given list/library is not present in the site" for certain lists created programmatically
• After updating from older verion of PointFire Translator to the newer version. If set credential is not done, then it is not showing the message properly.
• While translating through TranslateSPLibrary, the Item language for pt-br and pt-pt is set as pt. Also retranslation is not working as expected
• If Isfilenametotranslate=yes, language code has been added to translated pagename.
• After updating from older version of PointFire Translator to the newer version. If set credential is not done, then it is not showing the message properly
• While translating through TranslateSPLibrary, the Item language for pt-br and pt-pt is set as pt. Also retranslation did not work properly
• Translation for parameter IsFileNameToTranslate was not working as expected
• Issue with special character
• When MLP is enabled in the site and translating two pages at a time the translation process is in progress for a long time and later get the error "ERROR: Error updating the fields in translated item. Object reference not set to an instance of an object."
• After modifying a page whose translation is already available in MLP folder, it did not update the translation.
• When MLP and required check out are enabled in Site pages and translating through TranslateSPLibrary, it is showing errors
• For some pages, page contents are getting translated but shows incorrect error message
• When translating a lis, shows incorrect "ERROR: Detected an older version of PointFire Translator Add-in which does not support single sign on. Please update it."
• When MLP is enabled, could not translate some pages with large contents and webparts
• Translating a blank document, it is showing the error "ERROR: Error while detecting the language of the item. Index was out of range. Must be non-negative and less than the size of the collection."
• If file translation is present and checking out the source file, then it is showing "ERROR: Error while processing target language value. The file "{path and name}" is not checked out. You must first check out this document before making changes."
• If required check out is enabled and after modifying a page whose translation is already available in MLP folder, then translating did not update the page.

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

PointFire 365 v2.7.1.0, August 16, 2024

This is a recommended official release.  It can be used for production.  It adds several new features and corrects many issues.  It corrects an error caused by a Miocrsoft update that has started rolling out.

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

All of our PowerShell scripts use the PnP.PowerShell module. The PF365 installation script will install it 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. Contact support if you need an alternative.

Details here

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

New and Changed Features

• Translation button in the footer now calls PointFire Translator Express if it is installed.
• Speed up redirection caching when translating using PointFire Translator Express

Resolved Issues

• Activation button did not blink when app was updated
• Infinite reload issue in some cases
• While performing MUI step 2, error "The body of the request is not valid JSON(400 bad request)" when certain characters are encountered
• "Display this webpart in option" is not showing after Microsoft rolls out a change

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.

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.

This release of PointFire SE is the current supported release version 1.0.10509.  Release date May 10, 2024

PointFire SE can only be installed on SharePoint SE (Subscription Edition) servers.  If you have been using an interim release, you must upgrade as soon as possible.  For a complete list of fixes and known issues, consult the release announcement or the readme.rtf file (copy attached).  This release is suitable for a production environment.

The installation package and documentation are available here.  

The next update release is expected in February 2025.

Release Notes – May 10, 2024

Deploying PointFire SE
It is recommended that you run the installation on the server where Central Administration is located. Once PointFire SE is installed on the target server you can deploy the feature by running the PFConfiguration tool:

Start ->PointFire SE ->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\PointFireSE

⦁ 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 SE also includes an optional app for modern sites. To add it to app catalog ur update it, you can drag and drop the pointfire-SE-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 .

Updating PointFire SE

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

Upgrading from PointFire 2019
Upgrading from a PointFire 2019 is not yet fully supported. Contact support for availability. The scripts PFSEMigration.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

• Users with read only access can see the "Multilingual Setting" and "Translate Document" options in classic and modern view.
• Content type name from Content type hub which are already associated with a document library does not translate.
• When using a custom master page (not Seattle or Oslo), the language change does not work and the page does not reload.
• Group By on columns like Created By and Modified By does not work in a classic list view for some content types
• Adding some specific text into a multiline text column, results to a blank page.
• Web part menu option "Display this web part in" is not available in modern mode.
• Sometimes language menu is not visible in modern mode after clearing the cache
  
  

Please read the manuals attached and the readme.rtf file within the installation.

The PointFire 2016 language packs can be used and are optional.

This is a trial version, which you may use for development and testing.  To obtain a licence key, contact sales@icefire.ca

If you already have a licensed or unlicensed version installed, this package will install the upgrade.

To get support, submit a ticket here