Sp-starter-kit: Changing default footer links

Created on 9 Jul 2018  路  7Comments  路  Source: pnp/sp-starter-kit

Can the default information in the footer be edited prior to deployment including [email protected] and site links?

image

Most helpful comment

Thanks @eoverfield. I used the remove-pnpcustomaction as also recommended by @bcameron1231 and it worked.
Thank you very much:
https://beaucameron.net/2018/07/19/customizing-the-pnp-starter-kit-for-office-365-part-1-portal-footer/

All 7 comments

PnP-PortalFooter-Links.xml does not appear to allow editing of the bottom orange bar is this possible?

@nicholas-morris PnP-PortalFooter-Links.xml is the PnP Provisioning template that deploys the footer link list for the expanded footer, as well as a few site columns and a content type used by this list. If you want to change the content in the orange bar itself, there are two places you should review.

First, the footer itself is an application customizer that the provisioning process as well as a site script add to sites via custom actions. During the addition process, properties are set for the SPFx extension including the copyright and support properties.

You will need to set these properties in both ./provisioning/hubsite.xml around line 500 where you should find: <pnp:CustomAction Name="PortalFooter" as well as in the site script, ./provisioning/collabcommunicationsite.json, around line 13 where you should find: clientSideComponentProperties...

Once you update these two files, you will need to re-provision the starter kit, in particular you are looking to have hubsite.xml re-provisioned to your hub portal, and the site script updated.

Closing as @eoverfield answered on this.

@eoverfield : We have followed the steps to change the footer text (@Corpyright Contoso). We re-provisioned (i.e. re-ran the deploy.ps1 script). Still the Copyright Tag is not getting updated. What are we missing?

@gokello you might want to try removing the custom actions / extensions from the portal and then re-running the deploy script. It could be that the provisioning template is ignoring the already added custom action.

I suggest powershell, in particular remove-pnpcustomaction
https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/remove-pnpcustomaction?view=sharepoint-ps

Thanks @eoverfield. I used the remove-pnpcustomaction as also recommended by @bcameron1231 and it worked.
Thank you very much:
https://beaucameron.net/2018/07/19/customizing-the-pnp-starter-kit-for-office-365-part-1-portal-footer/

This was driving me crazy, finally sorted it. Run this as admin on PS (change the fields as needed):

Connect-PnPOnline https://.sharepoint.com/sites/
Remove-PnPCustomAction -Identity "PortalFooter"

Add-PnPCustomAction -Name "PortalFooter" -Title "PortalFooter" -ClientSideComponentId b8eb4ec9-934a-4248-a15f-863d27f94f60 -Location "ClientSideExtension.ApplicationCustomizer" -ClientSideComponentProperties "{""linksListTitle"":""PnP-PortalFooter-Links"",""copyright"":""@Copyright , 2020-2021"",""support"":"""",""personalItemsStorageProperty"":""PnP-CollabFooter-MyLinks""}"

Hope this help.
ACE

Was this page helpful?
0 / 5 - 0 ratings