Skip to content

Clarify publishing page modernization warnings and retain server errors - #1333

Merged
YifengMao merged 1 commit into
devfrom
yifengmao-clarify-publishing-warning
Nov 16, 2026
Merged

YifengMao merged 1 commit into
devfrom
yifengmao-clarify-publishing-warning

Conversation

@YifengMao

Copy link
Copy Markdown
Contributor

Summary

  • Preserve the original exception message in publishing-page modernization warnings.
  • Explain that failure of the combined version-stamp/publication request does not establish that the page is unpublished.
  • Recommend enabling minor versions only if the returned error indicates that requirement.
  • Keep existing migration behavior and non-publishing-page diagnostics unchanged.

Validation

  • Built the local framework for net10.0 successfully (existing warnings remain).
  • Performed direct local PnP verification through PublishingPageTransformator.CreateInPlace(...).Transform(...) in a dedicated process, verifying the loaded assembly matched the worktree build. This was not public ConvertTo-PnPPage command coverage.
  • Migrated one publishing page into a uniquely named output in a major-only target library. Observed one warning and no errors; the warning retained: You can only publish, unpublish documents in a minor version enabled list.
  • Independently read back the generated page: Published, version 2.0, with the modernization stamp saved.
  • Confirmed source/existing-output metadata and target library settings were unchanged.
  • Browser verification was blocked by Playwright MCP initialization timeouts. No automated test-suite pass is claimed.

Preserve the server error and recommend minor versioning conditionally without claiming that the page is unpublished.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@YifengMao
YifengMao merged commit 180e0b5 into dev Nov 16, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants