June 2026 Releases

SquizLink forms previously output an empty text parameter on every field change, even when no additional information was entered. This behavior resulted in failed validation.

The fix updates the component editing UI to standardize SquizLink field outputs, returning an empty result only if no field contains meaningful data.

Pages now pass validation when a Squizlink field in a component is cleared.

Processing an online quiz form with a checkbox or options list could omit one value, occasionally resulting in an 'array'. This sometimes resulted in a fatal error.

The form now accounts for values being arrays and handles them accordingly.

A write access check was not performed before a nested check that would trigger an error about notice links. This situation could cause bodycopy container generation to fail in specific scenarios.

The fix ensures a user’s write access is verified prior to that code path. Bodycopy container generation will not trigger an error due to write access issues with notice links.

Sometimes Deja Vu’s cache for bodycopies can hold onto container links to assets that no longer exist. Pages using bodycopies in this state would error until DeJa Vu was cleared.

The fix clears the bodycopy cache and retrieves fresh links from the database if a link points to a missing asset. Pages now render correctly even if the Deja Vu cache references non-existent assets.

On page load, the reflow algorithm mistakenly normalized single-zone templated pages using '__main' as the key, which should have applied only to untemplated pages. Page content followed the main zone reflow rather than the unlocked zone matching. This caused content to be missing from both the outline and the unused content.

The fix now restricts single-zone normalization to non-templated pages. Saved content for moved template-managed blocks now appears in the new location. Blocks left in the deleted zone will now appear in the unused content section.

Fallback matching now handles text, components, layouts, and variation blocks saved with a previous ID.

Previously, matching would not occur if a page zone ID was a prior template ID. This sent affected page content to unused content.

When a component service error, such as a schema validation issue, occurred during a POST/PATCH operation on a content page, the Asset Management API (AMAPI) returned "Validation failed" with no context for how to fix the issue.

Error details now pass through to AMAPI (Asset Management API) error responses, offering full context for Zod validation errors—including location within the data structure (path) and associated messages—so users can understand where and why errors occur.

When using the Asset Management API (AMAPI) to PATCH/POST templated pages, a matching nodeId (unique identifier for a layout block) for layouts in template-unlocked zones is required. If a user did not provide this nodeID, the validation failed. If a nodeId was omitted, it was auto-generated, validation failed, and the auto-generated nodeId was provided in the response.

API users were getting confused by the error message as it was difficult to understand where in their payload they had provided an incorrect nodeId (bcc36b32-ada1-44cb-a448-82a0e372c9ae in the following example).

The fix now aligns error responses for both cases—when a nodeId is provided and when it is omitted—and no longer references the auto-generated nodeId.

These recent improvements and iterations are part of the ongoing strategy to rapidly iterate on these resources while customers provide feedback about using Content Intelligence.

Read Content Intelligence to view the latest changes.

When string or FormattedText fields are empty, the Page Builder preview often hides the content region, which makes inline editing unavailable until developers add defaults or custom render logic.

Component manifests support previewPlaceholder on those field types so editors see hint text in the preview while a field is empty.

Developers can set explicit placeholder copy, use the field title (true), or combine default with previewPlaceholder (default on first load; placeholder after the editor clears the field).

Complex previews may still use JavaScript in main with ctx.editor where manifest placeholders are not enough.

Read Placeholder content in the Component Service docs to learn more.

Dependencies have been upgraded to address security issues, ensuring a safer and more reliable system.

Read the June 2026 Enablement features to learn more about placeholder text support.