Recently, I released new updates for the PnP Starter Intranet solution. Basically, it consists of an overall UI refresh (desktop and mobile) to something lighter than the original 2.0 solution. I also improved the search experience and especially the people search. Now it comes with an alphabetical and dropdowns filters (check the README file in the GitHub repository to set it up).
As usual, it comes directly from the IDRC design requirements so we can say a big thanks to them!
The complete list of updates:
- Updated the global UI experience.
- Improved design implementation using CSS flexboxes instead of the old float based design.
- Improved mobile design.
- Improved search experience.
- Added an alphabetical display template refiner for people search.
- Added a dropdown display template refiner.
- Added a light search box.
- Added a popup with search tips to help users.
- Improved the overall performance.
- Updated the root redirection logic. Now we use a SharePoint redirect page to instantly redirect visitors. People with contribute permissions will have a 5 seconds delay (default behavior).
- Ensured compatibility with IE10, 11, Edge, Firefox and Chrome.
- Added more options for deployments in the PowerShell scripts. Now we can exclude specific handlers (the same as PnP templates ones) for the deployment (i.e TermGroups or Files).
- Updated the « View all » link in content search display template. Now, you can set your own in the Web Part properties (in the CSWP slots).
- Updated the PnP provisioning template schema to 201705.
- Minor bug fixes.
How I can migrate to the 2.1.0 version?
Option #1: run the upgrade script
If you’ve already installed the 2.0.0 version without any customizations, the minimal upgrade path is to run the Upgrade-Solution.ps1 script like this:
$UserName = "<your_username>"
$Password = "<your_password>"
$SiteUrl = "https://<your_site_collection>"
$Script = "<your_installation_folder>\Upgrade-Solution.ps1"
& $Script -SiteUrl $SiteUrl -UserName $UserName -Password $Password
The upgrade process is done as follow:
- The XML root search configuration is applied cumulatively by checking the applicable XML file versions (greater than the current one, identified by file name
convention inside de “updates” folder). It means only new artefacts (managed properties, result sources ,etc.) can be created for new versions due to the default SharePoint import/export feature limitations. Previous configurations can’t be reverted using this method.
- PnP provisioning templates (root and sub sites) are applied again excluding the taxonomy and search settings to avoid merge conflicts.
- Miscellaneous updates in sub sites are done directly in the Setup-Web.ps1 script by ensuring if a resource already exists before creating or
recreating (field, list ,etc.).
By this way we are able to manage incremental updates without being too specific in scripts. Also, if you encounter issues you can re-run the upgrade process by setting the version to 2.0.0 in the site collection property bag:
Set-PnPPropertyBagValue -Key PnPStarterIntranetVersion -Value 2.0.0
Option #2: start from a fresh site collection and migrate your content
If you prefer to perform a clean installation, you can also create a new site collection and then migrate your content with specialized tools (like Sharegate). Using this technique allows you to get the new and old solutions side by side to ensure the migration got well.
The associated documentation has been updated as well. For information, the documentation is here is explain the underlying concepts and usage of the PnP Starter Intranet solution with a developer and an user guide. However, compared to the free version of the solution, it comes with an additionnal (an ridiculous) fee. You can get it here (EN and FR available):
Hope you will like these updates!