November 2025 Releases

Valid URLs that included - in the URL (for example, https://test.funnelback-search.com) were not accepted by the "Total page API URL" field. This issue is now addressed, and hyphens are now accepted inside valid URLs.

An issue was discovered in the Image asset’s getAsset() bridge function when attempting to retrieve an image variety that’s under Safe Edit (from File Versioning). If retrieval failed to check out the live version of the variety, the function:

The getAsset() function now correctly returns NULL on checkout failure, which prevents the TypeError. This change aligns with the function’s intended permissive behavior of gracefully handling cases where an image variety may not have existed when the parent image was placed into Safe Edit, allowing the system to handle the error appropriately (such as returning a 404) rather than crashing with a fatal error.

The Squiz DXP Console login session timeout has been increased to three hours from one hour.

Customer feedback suggested that one hour was too short, and resulted in having to sign back into the Squiz DXP too frequently.

An additional argument was inadvertently included in the file versioning checkout call when correcting the Image asset’s getAsset() method, which incorrectly returned FALSE.

Image varieties in Safe Edit status (including Safe Edit Awaiting Approval and Safe Edit Approved To Go Live) that were viewed by users who can not see the draft version failed to load in some circumstances. Pages that use certain keywords related to the varieties can also experience fatal errors.

The temporary workaround for this specific issue is to transition the affected image to Live status by approving or cancelling Safe Edit. The image assets will function correctly in Live status.

A fix for this is scheduled for release in 6.77.0. Systems known to be affected by this issue are being updated to address the issue. This issue may prevent systems that were in the 6.76 upgrade queue from proceeding. Instead, these system upgrades will be paused in favour of receiving the 6.77.0 release.

A recent change to how content pages are rendered introduced a pre-existing query parameter to not render page content when the page builder preview initially loaded. As a result, nested page contents in page layouts did not render in Page Builder preview frames.

The fix adds a check to ensure that page content rendering is stopped for the main frontend asset only, but allows rendering for nested assets within paint layouts. The nested page content in paint layouts are now rendered correctly in the content page’s preview frame.

An initial value would not be set when a user first visited the /_performance URL in a session, which caused a PHP warning to appear.

The presence of a value is now checked prior to use and a sensible default set where a value is not present.

The rules for considering whether a request was considered stale were broadened to better allow public caching of stale requests. The legacy MAC proxy layer assumed that Edge Side Include (ESI) requests would always be for the same user making the request, and ignored any suggestions from the server that it was a public response. When MAC forwarded a stale request for an object with both public and authenticated variants to the CMS server, it cached a response for the public version to the user’s specific permissions cache.

This caching behavior caused public versions of assets with both public and authenticated variants to be sometimes displayed to authenticated users. The public asset variant is no longer rendered when a stale request is received from the legacy MAC proxy layer, which ensures authenticated users are presented with the correct variant.

Some Facebook pages generated errors. The plugin now handles the different Facebook elements as expected and these elements are now parsed without error.

If you select a segment, open the edit panel, or set a custom preview width on a Content Page, and then move to a template, those selections could incorrectly remain active.

The fix resets the page selection state each time the template builder opens. This prevents previously selected pages from remaining active when moving between pages and templates.

If a layout change caused unused content, you might have seen an unnecessary 'unsaved changes' warning—even if you made no edits.

The fix now waits for all layout changes to finish processing before checking for unsaved changes. This ensures users only see the warning when they have truly unsaved changes due to their own actions.

Reference page values on templates were being set with cached data. If you changed a reference page without saving and navigated away, the unsaved reference stayed connected to the Template when you returned.

The fix delays setting a reference page value until new template content is fully fetched. This ensures the correct reference is used and that unsaved changes do not appear to persist across navigation. Unsaved reference page changes are now cleared when you leave and return to the template.

The page selection state was not resetting in the template builder, causing selections from Content Pages to persist when navigating to a template. Selections made on a Content Page, like segment selection, edit panel, or custom preview width, would incorrectly persist after navigating to a template.

The fix resets the page selection state in the template builder, so selections do not persist between pages and templates.

Layout zone placeholders were included in the main iframe document, rather than in a shadow DOM, unlike other inline elements. As a result, site designs and CSS could unintentionally change how these placeholders looked in the preview panel.

The fix uses CSS all: initial on placeholders and adds !important where required. This stops site CSS from affecting placeholder display, ensuring these elements look the same regardless of the site’s styles.

Page building would fail under three conditions: the page had layouts but no template, you applied a template with a primary zone, and the template’s primary zone blocked layouts.

The fix creates a duplicate of the layout object before making updates. This allows the template to apply properly and places layouts into the unused content area if necessary, ensuring a stable process.

A query string was being used incorrectly by the asset tree, which caused an error because it was not a valid asset ID.

The fix now removes any problematic query string from the URL before the user is redirected. This eliminates the asset ID error in the asset tree after a Squiz DXP SSO sign in.

A change added an extra argument to a file check-out method for images in Safe Edit, causing a regression. Image varieties in Safe Edit (including Safe Edit Awaiting Approval and Safe Edit Approved To Go Live) that were viewed by users who could not see the draft version may fail to load. Pages that used certain keywords related to the varieties may also throw errors.

The fix corrects the extra parameter in the file versioning check-out call. This restores intended loading, so Safe Edit image varieties appear as expected, and related keyword errors do not occur.

Files with 'Allow unrestricted' on but no public read permission weren’t handled correctly. This caused some files to get a 404 instead of being redirected.

The fix updates the logic that combines the Allow unrestricted setting and public read permission. Now, files that meet these conditions are redirected correctly, rather than mistakenly returning a 404 error.

Matrix Cache uses sets to track all cache entries associated with a specific URL or asset ID. It was discovered that Matrix Cache sets did not have expiry periods (TTL) set, which caused the Matrix Cache to leak memory and led to stability issues.

The fix adds expiry times (TTL) to Matrix Cache sets so unused entries are automatically removed. This prevents memory leaks and resolves related stability issues.

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

Campaign customers in the Single Customer View (SCV) API can now retrieve their encrypted customer reference ID through the customer-get endpoint. This unblocks Advanced Form answers being captured into a campaign customer Single Customer View profile.

Previously, campaign customers had no ability to access any of their own data through the API. This enhancement enables campaign customers to obtain their $customerReference (encrypted customer ID) while maintaining strict security boundaries.

Key features:

The Content Management docs have received a minor update to promote the Templates and Layouts features.

The Getting Started section now focuses on Content Pages as the preferred asset type to use.

Other areas of the documentation that deal extensively with Standard Pages now feature a note that guides customers towards the Page Builder docs.

The asset_file_type keyword is described in the Keyword Replacements documentation for Squiz Content Management.

This keyword was present in the legacy Matrix 5 keyword list but was not discoverable in the Squiz Content Management docs.