PointFire 365 v2.7.0.0, April 9, 2024

This release introduces new features and improves existing ones, including better user counts, more complete deactivation, and better performance.  Version 2.7 is the final version using the two-app architecture.  Version 3.0 will only need the modern app.

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

• In single-page model, translations of Call to Action text in Hero webpart
• ApplyingMUIFromTenantRootSiteWithoutUsingSiteLevelMTL.ps1: New script gets the MTL entries from tenant root site and applies the translations in all the sites present in a tenant without using the site level MTL.
• Script DeactivatePF365.ps1 now optionally removes Multilingual Translations list and Multilingual column 'Item Language' and 'Source Item' from site
• Improved performance for lists and libraries newly made multilingual
• ItemLanguageCalculated hidden added to lists and libraries newly made multilingual, to help with PnP modern search.
• Improved message in MUI step 3 when the app is not trusted
• More consistent override of translations: Resx<root<hub<site
• Scripts changed to use PnP.PowerShell rather than native login: EnableScriptingMultiSites.ps1 SetFooterPropertyInTenantLevel.ps1 EnableScripting.ps1
• MTL was cluttered with language codes when there was a choice column with those codes.
• No making Page library multilingual if MLP feature is enabled (still allow translating choice column)

Resolved Issues

• In MUI step 3 for classic webpart title translations, 'Exception has been thrown by the target of an invocation'
• Manage variation page names Blank for library with more than 5000 pages
• MUI step 3 stuck for library with more than 5000 pages
• Poorer performance with more than 5000 pages
• When custom scripting is enabled and the Edit permission user is setting the webpart language, showing 'Please enable custom scripting on the SharePoint admin center.'
• Errors when using "forceLocale=" URL parameters
• While making the Library Multilingual, it is showing the error "FAILED: The content type {...} is read only." in console when a new content type is read-only
• The script ActivateApp.ps1 showed the Error "The remote name could not be resolved: 'mytenant-admin.sharepoint.comfalse' Method invocation failed because [System.String] does not contain a method named 'Load'."
• Error running EnableScriptingMultiSites.ps1 for some subsites
• After running Uninstall.exe, some files did not remove from folder
• Error while running script DeployingMUIForSite.ps1 when there is certain sealed content types
• Eliminated instances of error "Refused to set unsafe header "Origin"' in the console
• More accurate users count while checking the PF365 license
• In Manage Variations on list with more than 5000 items, Save and Publish is not working
• In MUI step 1, it sometimes did not add the choice column choices value to the Multilingual Translation list
• Rare ActivateApp error "cannot convert argument 'context', with value "PnP.Framework.PnPClientContext", for "GetAppInstances" to type "Microsoft.SharePoint.Client.ClientRuntimeContext" :"
• After clicking on the Deactivate button, the removal was not complete
• "Created date" format issue for items with two instances of "Created date", one hidden
• On a site where Multilingual Page Publishing was once enabled, language variation fields in MUI step 2 sometimes incorrect
• MUI step 3 "Error in StartApplyTrans5: Unexpected response data from server."
• PF365Installer.ps1, when it is activating the app in sites that it upgraded, message "You must add PointFire 365 add-in app to this site"
• CallActivateAppMultiSite.ps1 sometimes activated all the languages not just the selected one.

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.