December 2025 Releases

Content API requests were leaving 7-day TTL public user sessions. Squiz Content Management instances with a high volume of Content API requests would store a large number of sessions, potentially causing Redis to crash.

Content API requests will not create sessions, which allows for more stability in Redis and Content Management instances.

In certain cases, cloning a standard page asset with metadata and no URL can result in array-specific operations being performed on a null value, leading to a fatal error.

The value is initialised to an array prior to the array-specific operation being performed. When hitting the originally reported cause of the issue, a fatal error no longer occurs.

Reordering bodycopy components through the page outline sidebar was done in whatever database Matrix was using. If Matrix had a faster replica DB available, reordering would fail with a message about read-only SQL transactions.

Now, Squiz Content Management always switches to a writeable database before saving component orders, which allows the system to reorder components through the page outline sidebar.

Admin code that failed to specify a query’s need for the write DB was intermittently downgrading it to the read-only DB when Read from replica DBs in admin was enabled. If Matrix had a faster replica DB available and read from replica DBs in admin, some operations would fail in the admin interface.

Squiz Content Management forces write queries onto the write DB even when the existing code specifies the read-only DB. Read from replica DBs in admin can be safely enabled.

Missing detection of fully empty layouts when reconciling template/page nodes in template reflow. There was no way for a page editor to see (and therefore recover) fully empty layouts from unused content.

Add detecting and handling for empty layouts in template reflow. Empty layouts are now visible in the unused content panel.

To accommodate more complicated site structures, the limit of layouts able to be nested has been increased from two to three across Template Builder and Page Builder.

Using the content adder, a content editor can now nest levels of layouts through the Page Outline or Page Preview.

The Content Auditor Summary tile was broken due to unescaped double and single quotes. This issue is now resolved, and the tile shows the correct data.

Previously, date facets were using server dates, which were based on UTC.

The schedule.timezone search package key now sets timezone information which is used by date facets to calculate the correct date.

Now, date facets and other Squiz Search features use the timezone information in the schedule.timezone search package key.

A change was made to the data source creation process, which sets "Access restriction" to "No access" by default. This lead to a broken view of cached pages in search results. The change has been reverted, and cached pages have started working again.

Profile names were being removed from the list of accessible profiles in the resources role. This caused people to get "access denied" when using functionality that uses profiles. Extra security was added in the code to ensure profile information about the resources role couldn’t be removed. This means that any feature that uses profiles is available to users with access to the associated profiles.

Access permissions to Accessibility Auditor were not being assigned correctly. This meant users couldn’t see or update Acknowledgements in Accessibility Auditor. The logic that assigned permissions was modified to ensure all functionality in DXP Search was correctly applied. This will allow users to review and update Acknowledgements in the Accessibility Auditor.

The content auditor summary tile was broken due to unescaped double and single quotes. This behavior is fixed, and the tile is rendering the correct data.

During deployments and other outages, the system now queues push requests when the deployment is complete and processes the requests from the queue. This is so that clients don’t have to resend requests that fail to be processed due to the outage.

The logic uses the first instance of logs in the path. Therefore, if the data source or search package name contain the series of characters logs, the path is incorrect. This means when the log file is retrieved, it is incorrect, and HTML is displayed instead of the log file contents. This has been fixed by modifying the logic to read the last characters of logs/ in the path. This new logic correctly identifies the path and the content of the log is shown.

schedule.timezone search package key now sets timezone information which is used by date facets to calculate the correct date.

Previously, date facets were using server dates, which were based on UTC.

Now date facets and other Squiz Search search features use the timezone information in the schedule.timezone search package key.

The CDP instance activation command was failing due to an incorrect API request format.

The HTTP PUT request was missing a required parameter, causing activation requests to fail. CDP activations via the DXP CLI now work correctly.

Previously, it was necessary to update both the URL template and the configuration for the result-per-page change.

This update adds a new keyword — ${recordsPerPage} — for use in the Start URL template for Offset mode. The new keyword represents the number of records per page.

By using this keyword, the Generate start URLs plugin version 1.3.0 now supports number of records per page in Offset mode without requiring further configuration.

Tealium has been added as a DXP integration service. Customers can now confidently use Tealium to personalize their DXP experience.

Find out more in the Tealium docs.

Website visitors were not getting captured on visits from marketing URLs.

Anonymous profiles are now created based on data extracted from campaign URLs.

Find out more in the Anonymous profile event feed docs.

A gap between deprecations occurring in Squiz Content Management and the docs being updated caused some pages to appear as though they were still describing available functions and features in Squiz DXP.

Pages that contained mentions of deprecated features now have clear admonition statements that highlight the fact that the feature persists in the product for migration purposes, but should not be used for solutions today.

This stance in the docs should help customers understand the reason why the information persists in the docs and help them learn more about other deprecated features in Squiz Content Management.

The course material for Step 7 of Creating your First Component now includes the following topics:

This information brings this part of the course up to current configuration recommendations.

The course material now includes recommendations for adding translatable fields to your custom components.

This information brings this part of the course up to current configuration guidelines.

It was discovered that a change to the logs service filtering was not correctly captured in the docs resources.

The logs filtering time was extended from the initial launch limit of 15 to a maximum of 90 days of log records.

The documentation for the Logging Service now accurately reflects these limits.

The Trigger sign-out method docs were missing two critical steps. Without the steps being outlined in the docs, developers could not get the Trigger method to sign a user out through SAML.

Two steps were added to the Logging a user out steps, which describe the additional steps required. The trigger sign-out method is now accurately described in the documentation.