Skip to content

Varying Compositions in Invariant Document Types, Cherrypick of #21267#21472

Merged
AndyButland merged 2 commits intorelease/16.5from
v16/bugfix/backport-20758
Jan 21, 2026
Merged

Varying Compositions in Invariant Document Types, Cherrypick of #21267#21472
AndyButland merged 2 commits intorelease/16.5from
v16/bugfix/backport-20758

Conversation

@nielslyngsoe
Copy link
Member

Fixes #21267

By cherry-picking the fix from #20758 into 16.5

Copilot AI review requested due to automatic review settings January 21, 2026 14:37
@nielslyngsoe nielslyngsoe changed the base branch from main to release/16.5 January 21, 2026 14:37
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR cherry-picks a fix from PR #20758 to address issue #21267, which involves handling varying compositions in invariant document types. The change ensures that property variance settings (by culture and segment) are only applied when the content type itself supports variation.

Changes:

  • Retrieves content type variation settings before processing property types
  • Conditionally applies property-level variance based on content type variance capabilities

Copy link
Contributor

@AndyButland AndyButland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've verified this works as expected. I could replicate the issue on 16.5 before the merge of this fix, and confirm that it resolves the reported issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Composition field blocking publishing a page

3 participants