This release of Page builder includes the following improvement:
Personalization no longer requires components to be marked as compatible to be swapped with each other in a page variant. This gives authors more flexibility when configuring personalized experiences and reduces configuration overhead for developers.
This release of Page builder also includes the following fixes:
Container components that are hidden using personalization no longer cause nested components to appear as broken in Page builder.
Authors can now remove or repair components that were inside a broken container directly in Page builder, avoiding the need for manual cleanup in Presentation Details.
The Open in Content editor button is now correctly shown in the right-hand content tab wherever applicable, allowing authors to jump directly from Page builder to Content Editor.
Page translation now correctly includes content coming from associated partial designs, ensuring translated pages are complete.
In the Page content context panel, the fallback value labels now correctly show the language that provides the fallback value, helping editors understand content origin without leaving the builder.
Page builder now fully respects the workflow command Suppress comment configured in Content Editor, so comment prompts only appear when they are expected.
In Rich Text fields, adjacent <ul></ul> blocks as now kept separate <ul> blocks instead of merged, keeping list structure and spacing as authored.
Page builder now sets the dam-content-type metadata correctly when authors add Content Hub assets, ensuring consistent and accurate asset metadata.