Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue when saving IClientsidePage with new banner section / page head functionality #3116

Closed
Bobinho4711 opened this issue Aug 13, 2024 · 2 comments

Comments

@Bobinho4711
Copy link

Major Version

3.x

Minor Version Number

3.17.0

Target environment

All

Additional environment details

Using it in an Azure function, but I assume all environments are affected.

Expected or Desired Behavior

Simplified case:
I want to create a new Page via the SharePoint frontend and publish it.
Afterwards I want to fetch it via my app as an IClientSidepage object and save it.
I would expect that the page looks like it looked before the save.

Observed Behavior

Microsoft recently introducted this Banner Section, which is also used by Microsoft to replace the Page Header as we knew it.
Once you save the page via PNP, PNP add the "old" header in top, so that it is displayed twice:

Original, created via frontend:
image

Afterwards, just after save:
image

This happens independently of the banner type.
image

Steps to Reproduce

Simplified case:
Im trying to get an IClientSidepage Object via

sp.web.loadClientsidePage("some ur");

and save it afterwards, without any changes:

page.save(true);

Afterwards page is broken as shown above.

@bcameron1231
Copy link
Collaborator

Duplicate of #3095 and #3096

Copy link

This issue is locked for inactivity or age. If you have a related issue please open a new issue and reference this one. Closed issues are not tracked.

@github-actions github-actions bot locked and limited conversation to collaborators Aug 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants