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 January 2023.

Release Notes – May 20, 2022

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

• Force Page View setting was causing an error with some sites with wiki pages
• Site contents page blank if PointFire modern app is missing
• Translations in Nintex edit form
• Fix for translation of some site columns and column names in quick edit view
• Performance issue with Modern sites with unilingual library
• User names not resolving in Nintex picker dialog
• Global navigation translation did not update unless going to a new tab
• Unable to change language for some farm architectures
• Pointfire error when opening quick edit in library that includes certain lookup columns
• Filtering page with custom Master page
• In MUI step-3, when the value of Term does not match that of English Variation in Multilingual Translations List, translations are not applied correctly
• In Document set, All page properties, choice column values not translated
• Blog site translation issue when there are French and English posts, for example: changing language repeatedly makes it get stuck
• Content Type name is not translated in List view
• Issue with Default Value of Choice Column
• For some URLs, in classic mode Language change is stuck, in modern mode the columns names do not translate properly
• In DispForm.aspx the Title column value is not getting translated

Known Issues

• Other instances where refiners are not being translated
• Global navigation for Publishing sites is not getting translated in Modern mode
• Quick Launch is not translated for read only users in Modern mode unless they have "Edit Personal User Information" permission level
• A 1 to 5 second performance issue on some libraries with many folders
• Some ribbon icon text not localized in modern mode
• View name containing a double quote is translated in the custom list in the webpart, but it is not translated in the ribbon.

   

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

This is a supported release.  It fixes several errors in v2.1.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

In this release, all of our PowerShell scripts are switching from the legacy SharePointPnPPowerShellOnline module, which stopped being maintained over a year ago, to the new PnP.PowerShell module.  This may require global admin consent.

New Features

• On install, clean up old version's folders, delete old Windows Service from a different directory, but keep some of the settings
• On uninstall, check if any console window is running, stop it if required
• PointFireTranslatorInstaller.ps1 will update the Add-in in the app catalog and in all sites where it is installed. Executed during installation, but can also be run separately
• Removed the code of adding Add-in to the app catalog in AppReg.ps1 since it is now done by the installer script.
• Support the language codes Inuktitut (Latin) - "iu-latn", Somali - "so", Zulu - "zu", and Upper Sorbian - "hsb".
• Change from unsupported SharePointPnPPowerShellOnline module to the PnP.PowerShell module in the scripts 'PointFireTranslatorInstaller.ps1' 'AppReg.ps1'

Resolved Issues

• In web interface, while doing setcredential for the PointFire Translator Add-in, it showed a blank page.
• Says it's translating but not translating some pages on some sites depending on configuration.
• Changed the download location when Microsoft Identity Extensions is not installed.
• Error: "The property or field has not been initialized. It has not been requested or the request has not been executed" This error is sometimes related to the check out policy of the library. With a modern page and with a classic webpart page the content were not getting translated, only the title
• When "required check out" is enabled, some pages did not translate and showed the error "The file "{filename}" is not checked out. You must first check out this document before making changes."
• The AppReg script did not allow hyphens in the host name in the URL.
• In publishing site the Enterprise wiki page contents was not getting translated or partly translated.
• On a classic Enterprise wiki site with an Enterprise wiki home page CEWP was not translating.
• For classic pages, translate "Publishing html" columns, including for custom layouts and custom master pages
• When translating a page which is already translated, it shows the error messages "The property or field has not been initialized. It has not been requested or the request has not been executed. It may need to be explicitly requested.", "The 'sId' argument is invalid.", "Documents failed to translate."
• Classic webparts page not translating content editor and script editor webparts
• When the translation copy is available for a webpart page and we modify the source page and send it for translation then it shows a failed message that the translation is already available.
• Translator server, stored credentials requiring MFA: if access token is expired then refresh the authentication token, but not if running in service mode.
• The "Publish" parameter is no longer case sensitive
• For classic pages with the value Publish=Yes, it is showing the errors "You cannot perform this action on a checked out document." "Documents failed to translate."
• PowerShell sample scripts: Added changes for the Publish parameter.
• While translating a classic page, it is showing ERROR: Version conflict.
• When retranslating the source page, it created another copy for some languages
• Error when a parent site name is a substring of a subsite name
• For the root communication site if we do not enter the "/" after the site url, getting the error "The remote server returned an error: (403) Forbidden. Something went wrong in getAuthorizedContext: The remote server returned an error: (403) Forbidden"
• After translating a modern page, the news webpart filter property language is not always set to the correct value.
• Improvement to the translation of filtering conditions in webparts for certain languages
• For wiki page, success/failure message is not showing properly after translating the page through the Add-in.
• Check if PointFire Translator server is running in console when updating software CheckForTXServiceConsole.ps1
• Check if the service is installed and running when updating sofware
• Various performance improvements in translation.
• While translating modern pages using the Add-in or Translate document option, the page title was not translated like the file name
• Changed upload to the app catalog so that it works when the app catalog site is not English

PointFire Translator can translate individual items or entire libraries or lists in SharePoint Online.  It includes the PoinFire Translator App which will use PointFire Translator Server as a default translation service, and fall back to SharePoint's Machine Translation Service 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

This is a recommended update release for PointFire 365 for SharePoint Online, part of Office 365.  It includes many bug fixes and adds some significant new functionality.  The June release will be a mandatory release.

This release adds support for new and changed Microsoft functionality and corrects a number of issues in version 2.5.0.  If you were provided with an interim release numbered v2.5.0.x, you should update to this release.

IMPORTANT NOTICE

In this release, all of our PowerShell scripts are switching from the legacy SharePointPnPPowerShellOnline module, which stopped being maintained over a year ago, to the new PnP.PowerShell module.

The PF365 installation script will uninstall the old one 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

• All scripts have been converted to use the new PnP.PowerShell module
• If required, Installer script uninstalls the old SharePoint PnP Powershell module, installs the new PnP.PowerShell
• Easier to skip installer script altogether and install manually
• In installer script, it will force a new login if already logged in, in case existing login was not the intended account
• More consistent login experience in scripts for MFA and non-MFA
• New script SetFooterPropertyInTenantLevel.ps1 allows you to opt out of having the modern page translation option in the footer
• In MUI translation, better support for very large number of UI items and duplicate values in MUI step 3
• Accessibility change: Improved colour contrast
• Accessibility change: Improved tabbing in screens and menus, can use keyboard rather than mouse
• Accessibility change: Improved tabbing feedback, fields highlighted when tabbed to
• Accessibility change: Removed suite bar from some screens for easier tabbing and less scrolling
• Accessibility change: Buttons interact better with screen readers
• In PF365Migration script, better support for migration from older versions of PointFire 2010, 2013, 2016
   

Resolved Issues

• If the app in the app catalog was checked out by another user, it gave an error message but continued installation
• Sys.InvalidOperationException error message in some contexts when using "Translate Page" option in footer.
• Font color of the "PointFire Translator" link in footer is not changing when changing theme.
• Some column names in SharePoint site templates were not translating when Microsoft gave them non-unique GUIDs
• Performance issue and possible throttling PointFire while a modern page is being edited.
• In installer script, some sites were not updated if permissions in parent site and in subsite differed
• When language is toggled, sometimes some of the UI ("Edit" for example) did not change until next page load
• Opening a new tab on a modern page seems to reset the "Filtered" toggle to "On"
• Change the language, toggle the filter, then navigate to another site, language menu option is sometimes not showing.
• In Manage Variations, when selecting "Save & Publish", when unlinking one file and linking another, the change to the unlinked file is not published.
• Site title sometimes did not translate 

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.

This is a recommended update release for PointFire 365 for SharePoint Online, part of Office 365.  It includes many bug fixes and adds some significant new functionality.

This release adds support for new and changed Microsoft functionality and corrects a number of issues in version 2.4.2.  If you were provided with an interim release numbered v2.4.2.x, you should update to this release.

New and Changed Features

• PF365Installer Installation exe that installs/updates apps on the tenant app catalog, replacing previous zip file.
• If PointFire Translator app is also installed, link on the modern page footer to trigger a page translation without leaving the page, if library is multilingual
• If PointFire Translator app is not installed, link on the modern page footer to copy the page, ready for translation, if library is multilingual.
• In Manage Variations, folder icons for folders, and files within a folder indented under the folder.
• "Filter" and "Unfilter" options changed to "Filtered" toggle option.
• Translate modern webpart titles. Only on pages in a page library that do not redirect and for webparts that do not show/hide by language.
• Passwords more consistently hidden on the screen
• Support for Global navigation and changes in Hub navigation
• Added script PF365MigrationFromMLP.ps1 to migrate sites from Multilingual Page Publishing to PointFire 365
• Added script EnableScriptingMultiSites.ps1 to enable custom scripting in multiple sites.

Resolved Issues

• Very slow redirect on a site with a new user having non-default language in their profile, or starting a new session
• Possible redirect Loop for a few minutes for users who navigate from a site with full control to a site where they are read-only
• In Manage Variations page, After language change the filter option is not working.
• In Manage Variations page, no items showed up in the list on the right of while the language was French.
• In Manage Variations page, not able to select the file if the file name contains a single quote (').
• In Manage Variations page, not able to select the file if the file name is too long
• After language change from a site, navigate to a classic site and the page reloads continuously if a current language is not activated on that classic site.
• The home page did not redirect in a classic site.
• Page redirection issue while navigating from one site to another when Item Language and Source Item columns are set manually rather than by PointFire.
• In UI Translation step 1, error "Multilingual Translations list is not present" when there are a large number of lists
• When using UI Translation on the hidden site contentTypeHub, new custom content type names did not translate.
• Optimization of process query calls for UI Translation for faster performance, less throttling
• After performing UI Translation Step-3, delete some items from the MTL, then perform Step-1 by unchecking the "Untranslated Only" option. We can see the deleted terms are added but their variations are not added.
• UI Translation Step-1 is getting some zeroes "0" for Term field and blank value for variation fields when the "Untranslated Only" option is unchecked
• After clicking on UI Translation Step-3, it is getting stuck and only showing the message "Started".
• If two folders have the same item names, then the source item and item language are sometimes not set properly.
• If we enable make multilingual and select all items as en then it is only adding the item languages of the current page items as en but inside the folder items are not set to en.
• Hub navigation not translating in some cases.

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.

This is a supported release.  It fixes several errors in v2.0.1, adds several features, and is even easier to install.

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.

The older single-user version 1.2 branch, which does not require AAD app registration, is still supported, and a new version will be released in the coming days with many of the same new features and bug fixes.
 

New Features

• Parameter ":n" after the language to use a unique name based on the original file name rather than translating the file name.
• Command line parameter "publish" for publishing translations
• In AppReg, check for and install Module SharepointPNPPowershellOnline if it's not installed
• In AppReg, if there is an error when setting permissions, display the message in the browser, otherwise "Success".
• At the end of Appreg, check and add/upgrade the app to tenant app catalog
• Removed Category Id and Region parameter in User Interface. These were often given incorrect values, and usually do not need a value. They are available through the command line.
• Several error messages changed to say why the error occured and what to do differently
• Site-specific configuration section (3 fields) is hidden unless expanded by admin user. By default the app will use the tenant configuration, but it is possible to override it at the site level.
• When loading the app page, automatically check & show app version and server version. If not, provide a link about server installation.
• Pre-populate the source item language if it's already set or detectable.
• Option to use "fr-ca" rather than "fr-fr"
• App is more consistently called "PointFire Translator Add-in"
• Passwords are more consistently hidden on screen
• The web interface has a more intuitive way to enter the name of a file within a folder, as "/foldername/filename"
• For web interface and scripts, checking that username in stored credentials is authorized is moved to Set Credentials rather than re-checking every time.
• Add-in main screen is more aware of different scenarios with MLP or not, with no alternate languages and with some and with all alternate languages, and gives appropriate advice.
• Now supports over 100 languages

Resolved Issues

• Doing Set Credentials while SPSiteURL is the root site gave (403) Forbidden

• Doing set credential under power Automate tab, it is adding unnecessary SPsiteUrl value.

• In certain languages, Home page translations through web interface gives "ERROR: The property or field 'Name' has not been initialized. It has not been requested or the request has not been executed. It may need to be explicitly requested."

• When translating classic calendar, set values for start time and end time field that do not depend on time zone of user or server.

• When translating classic calendar, sometimes get "ERROR: The given list/library is not present in site."

• if translating the home page to 2 or more languages at a time then the translated page is blank for some languages

• Users now need "Edit" permission, not "Manage Lists" to translate with the app. Previously when trying to translate a document with permissions, could get the errors "ERROR: Something went wrong in getList:Access denied.", "ERROR: Abnormal termination (Access denied.)"

• Web interface: when translating a document that does not exist in the document library, it showed Success message on the top right corner while in the bottom it showed File cannot be found in Document library.

• When translating a PDF, got complex error message if Office was not installed on server, like "Retrieving the COM class factory for component with CLSID" or "Class not registered" Replaced with a clearer message.

• While translating a document using the web interface, gave this error "ERROR: User name in stored credentials must match one of the authorized users in Usernames." even though user is authorized.

• Translating with SharePoint Multilingual Page Publishing feature gave the message "You can not translate the page." Replaced with clearer messages saying why not.

• Re-translating with SharePoint Multilingual Page Publishing was not translating new changes.

• Difficulties in translating a page within a folder. Syntax for documents within folders made more flexible.

• Translating site pages with MLP feature for multiple languages, including unsupported ones, it shows the success messages but not the errors.

• While translating to multiple languages through App, the Translation Details is only showing the message "Documents translated successfully: 5". There is no message to which languages the page is translated.

• Some interfaces were not recognizing "zh-CHS" as a SharePoint language and an alias of "zh-CN"

• When translating a list item, the Translation details is blank when translation is successful.

• After translation, language code within the file name was sometimes incorrect for recently-supported languages like Macedonian and unsupported languages Basque and Galician.

• When translating a document inside a folder to multiple languages, Chinese simplified translation did not work. When Chinese simplified and Chinese traditional were both requested, both translations are the same.

• After successful translation send it again for retranslation, in query result it says that it successfully translated for zh-cn and zh-tw (should not re-translate if original is unchanged). Similar issues for (sv,it,et,uk,pl,cs,bs,hr,bg,sk,da,sl,ru,es,de)\

• Translating pages with MLP to all languages, if the page does not have copies for MLP folders in all site languages, it does not show which ones are missing.

• PointFire 365 and MLP both active (not supported), translate library using web interface to pt-pt and pt-br. Query results shows only one translation.

• MLP is active, translate the SitePages using 'Translate SharePoint Library', re-translation of the pages shows successful message, despite nothing to retranslate.

• MLP is active, translate the SitePages without having MLP copies or folders, the message showed only failed but did not say which ones or why.

• Translate through Translate SharePoint library, pages within a folder, then re-translate. it shows success message. (should not re-translate unchanged pages)

• Translate through Translate SharePoint library, pages within a folder. Page title is not always translated inside the page.

• Translate a text file to all language and then wait for some hours then send the same file for re-translation. Sometimes get the error " The remote server returned an error: (401) unauthorized". This may be because the submit button was double-clicked.

• Sent a document for translation to pt-pt,pt-br. File names incorrect, pt-pt document name is Documento9[pt-br].docx, pt-br document name is Documento9[pt-pt].docx if original file name ends with a digit.

• When using App and using MTS. discontinued language code "sr-latn-cs" was still accepted, should map to "sr-Latn-RS", if it is ever used in error.

• In communication site, send a Library for translation to fr,de,es,pt-br using web interface. The document did not translate to pt-br. But if we specify only pt-br then it is translated successfully.

• When we translate a document to Dari (prs or prs-af) it returns with Item Language set to "fa"' in UI.

• When we send a page for translation after making the library multilingual directly through the PointFire Translator app then the item name is showing twice in the message.

• After clicking on the "Go back to site" button too soon, the temporary file was not deleted.

• If it fails because document is locked (open for editing) or other reasons, the temporary file was not deleted.

• In general when the Translator server is not available, the app should switch to the MTS service. In some cases it does not switch, it shows an error message saying it can't reach it.

• When the app is adding the Item Language column, apply to all content types, set the default language and the language of existing items like PF365 does

• In PointFire Translator Add-in app Page, "Go back to site" button is sometimes not working. If we click on this it is redirecting to the same page.

• On a site with MLP, all languages, incorrectly had errors for language codes ga-ie, no, az-latn-az, mk-mk, kk-kz

• Activate all language in PF 365. Then select a document and send it for translation through MTS. Don't select any source language. After translation, is translated to English and there are two documents with the same source item and item language "en".

• The Add-in said "you are about to translate xxxx.docx into all the languages of this site" even in only some languages selected. Now lists the languages instead.

• The Add-in now switches to the MTS in most situations when the PointFire Translator Server is not reachable.

• When we send a document but the document does not exist in the document library. It is showing Success message on the top right corner while in the bottom it is showing that File cannot be found in Document library

• When you enter "txfire setcredentials /?" in the command line, it gives a list of the arguments, but it was not clear which are mandatory.

• When you send a page for translation after making the library multilingual through the PointFire Translator app then the item name is showing twice in the message

• When all languages are activated, and clicked on a calendar item to translate through PointFire translator app, the scroll bar was not appearing on the pop up window.

• Issues with double quotes within mstrans.dic file

• For TranslateDocuments.ps1, while translating a document having a title with space, it is showing cannot be found in library.
• Many other small fixes and performance enhancements

PointFire Translator can translate individual items or entire libraries or lists in SharePoint Online.  It includes the PoinFire Translator App which will use PointFire Translator Server as a default translation service, and fall back to SharePoint's Machine Translation Service 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

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 January 2022.

Release Notes – July 7, 2021

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

• InstallAppFromAppCatalogWebApplication.ps1 New scripts to install/update the PF219 modern app at the web application level
• ApplyTranslationsMultiSites.ps1 New script to apply MUI step 3 to multiple sites
• Pf2019MigrationSiteLevel.ps1 New post-migration script to update Multilingual Translations lists
• PF2019 Migration script - which level: Web Application, Site Collection, Site

Resolved Issues

• Modern Quick edit ignores unfiltered setting
• Not all items in the list were being shown in the Quick View.
• Values in the dropdown choice column options are not translated in quick edit mode
• Values in the dropdown multi look up column options are not translated in quick edit mode
• The values of multiple value Look up field is not translated in New/edit form
• When multilingual list/library default language selected as English, it does not set the source item field of the source document to "en"
• If you translate the Home.aspx modern page, then the translated (copied) page content only contains News and activity webparts.
• Infinite page reload for the translated (copied) pages.
• While sending the document for translation through "Translate Document", it shows "An Error occurred while creating new Variations for items.". But the items is uploaded successfully and the item language set is wrong.
• Translating classic wiki pages, doesn't copy webparts.
• Send the document/list item for translation through "Translate Document/Item" you can see the error "An Error occurred while creating new Variations for items."
• Send a wiki page for translation through "Translate Document". You can see only the page contents are copied in the translated page.
• Send a list item/wiki page for translation using Translate item/Translate document option. You can see a pop up message saying "Machine Translation is not available. Item copied instead." and the list item and page content are copied.
• In Team site, global navigation terms are not added in MTL, when unclicked Untranslated only option and performed step 1
• In MUI step 1, when Untranslated Only is unchecked, it does not retrieve all items and they all have their wrong variations added in MTL.
• In MUI step 2, the Column/list title and description have got same variation for both en and fr
• After performing MUI step 3, delete some terms from MTL and perform step 1 (Unchecked). It is getting the terms with wrong variations. for eg:- for Site name it has added the site description value as the Variation.
• After performing MUI step 3, delete all term from MTL and perform step 1 (Checked). It is getting all terms but should only get untranslated terms.
• Refiner Labels not translating on Results page. The Site is using the results.aspx page (on the same site) for their search results, with refiners on this page.
• he refiner labels are not translated on the results page.
• Filtering on a choice column (regular view). When in French interface, if you select a value from one of the choice column, the filter is applied but the values in that choice column now show in English.
• The MTL "term" column is not unique. That means they can add duplicate items to the list.
• If we have three languages activated in the site and you have provided the variation of two languages, while saving it is showing save failed. But it successfully saved.
• Changed the language to French then while doing manage variation, the pop up message is showing in English.
• After removing Multilingual in modern page, the redirection is still working.
• Read only user can open the Multilingual Setting option.
• In event list Calendar view filter/unfilter is not working
• Issue when redirecting from "Calendar" view to "All events" view
• Error with French characters the ULS.
• Toggle language unresponsive when anchor tag in URL
• Many other minor changes and optimizations
  
  

Known Issues

• Other instances where refiners are not being translated
• Global navigation for Publishing sites is not getting translated in Modern mode
• Quick Launch is not translated for read only users in Modern mode unless they have "Edit Personal User Information" permission level
• A 1 to 5 second performance issue on some libraries with many folders
• Some ribbon icon text not localized in modern mode
• View name containing a double quote is translated in the custom list in the webpart, but it is not translated in the ribbon.

   

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