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.

Pages were allowed to save when SquizLink fields inside components were in an inconsistent state.

This prevented pages in draft that were saved with a link in this inconsistent state from being set to live.

Page editors can no longer save the page and receive a frontend validation warning if the link is not filled out correctly.

Bulk form submission deletions using the UI could exceed PHP execution time limits, resulting in HTTP 504 timeouts.

When users triggered bulk deletion from the UI, the form submissions were not reliably deleted.

The fix introduces a HIPO job to delete form submissions in batches. The HIPO job framework uses iterations per request, so long auto steps can refresh progress in the browser.

Bulk UI deletion is completed through batched HIPO processing, avoiding the 504 timeout failure mode.

When the 'Use static cache file?' feature is enabled, requested CSS Design File & SCSS Design file assets will now be cached by the browser through setting a max-age header.

With the deprecation of __data paths and the Linked CSS design area, it was important to add this and align the behavior with other similar assets (for example, CSS File).

The query to draw asset children in the asset tree did not use the limit already set in pagination. Opening an asset with a large number of children (150,000+) in the asset tree caused out-of-memory issues.

A limit based on the children pagination setting has been included in the query for fetching the list of children. Now, opening an asset with many children no longer causes an Out of Memory error.

Under certain conditions, a Workflow step could set a shadow bridge asset to null when a method on the asset was called. This would result in a fatal TypeError.

The shadow bridge asset is now checked before attempting to call the method on it, and skipped if it is no longer there. The Workflow step condition will no longer be fatal in this way.

The state of an asset is saved for Safe Edit using all known values at the time that the asset is put into Safe Edit. No updates are made to this when new metadata fields are added to the asset. When canceling Safe Edit, the saved metadata values are applied to the fields that had them, and no other changes are made.

If a metadata field is added to an asset (for example, added to a schema applied to it) after it is placed in Safe Edit, then when canceling Safe Edit, that field will have whatever value has been set. This means that changes made during Safe Editing have been effectively published.

Avoid adding fields to schemas that are in use by assets in Safe Edit status. If a field is added to an asset in Safe Edit, do not change it from the default.

Use one of these workarounds to solve the issue:

There are gaps in the processing of templated layouts on pages when multiple updates are applied to the template at once. For example, moving a layout, locking the original layout zone, and deleting content from within the moved layout. Content saved to the page disappeared and was not found in Unused Content. The page editor had no way to recover the content.

Processing of templated Content Pages now handles these combined actions. In this scenario, the saved page content is no longer missing and will correctly appear in the Unused Content panel.

Duplicated or template-conflicting node IDs in page-managed content are now reset when a page is initially loaded and when it is saved.

When node IDs were duplicated, overlays didn’t render correctly. With stricter templated page validation planned, duplicated or template-conflicting node IDs will prevent saving if detected.

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

Read the June 2026 Enablement features to learn more about this feature.