Issue Summary

After converting a legacy page to the new editor, complex/unsupported content is wrapped in a Legacy content macro. If a third‑party macro sits inside that Legacy content macro, and that is inside an Excerpt, the Insert Excerpt macro on another page fails to render the third‑party macro’s output. The Insert Excerpt region may appear empty or only show plain text, silently dropping the nested macro content. This is a limitation of how Insert Excerpt interacts with Legacy content and nested macros after migration, breaking previously working Excerpt/Insert Excerpt setups from the legacy editor.

Steps to Reproduce

1. In the legacy editor, create Page A.

1. On Page A, add a third‑party macro (from a Marketplace app).

1. Wrap that macro in an Excerpt macro so the macro is inside the Excerpt body.

1. Create Page B (legacy editor) and add an Insert Excerpt macro that pulls the excerpt from Page A. Confirm the third‑party macro output displays correctly on Page B.

1. Convert both Page A and Page B to the new editor.

• • On Page A, verify that the third‑party macro is now wrapped in a Legacy content macro, which itself sits inside the Excerpt macro.

1. View Page B in the new editor and publish it.

Observed: The Insert Excerpt macro on Page B no longer shows the third‑party macro output (the excerpt appears empty or only shows non‑macro text).

Expected Results

• After converting both pages to the new editor, the Insert Excerpt macro on Page B should continue to display the same content as before conversion, including the rendered output of the third‑party macro contained in the Excerpt on Page A.

• Migrating from the legacy editor to the new editor should not change or break how Excerpt/Insert Excerpt renders the reused content.

Actual Results

• On Page B, the Insert Excerpt macro no longer displays the third‑party macro output from Page A.

• The excerpt region either appears blank/empty or shows only partial/plain text, silently omitting the nested third‑party macro content that is now wrapped in the Legacy content macro.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available