February 2026 Releases

For a tenant with custom roles enabled and a single Search instance when non-owners logged in non of there custom roles were being used.

When logging in a user the code changed there user record type and roles to only include the clients primary role. Consequence:

The code has been adjusted to ensure the user record is not changed when a user logs in.

The useer has the roles assigned to them to complete required Search tasks.

The segment sets feature allows administrators and site builders to scope Personalization segment sets based on their required availability across sites.

The documentation required to understand this feature was updated to reflect the support for segment sets in Squiz Content Management.

Read the Segment scoping documentation to learn more.

Added: Send event on non-push data source update stop. Changed: Send event after successful view swap for non-push data sources as a post swap step instead of during the index phase. Send event after successful commit for push data sources as a post commit step instead of during the index phase.

An incorrect name for the page parameter was used when creating page navigation links.

Page navigation links contained multiple incorrect parameters for page numbers, and the wrong page was loaded.

Page parameter name is fixed when generating URL links, so the parameter is properly cleared and set to the correct page number.

Page navigation links now only contain a single page parameter with the correct value.

preg_replace works with URLs that include query params. Some replacement patterns preserve query params in the output, then the code appends them again, causing duplicates.

Query parameters are duplicated in redirect URLs when remap rules have "Preserve query string in remaps" enabled. For example, /example?foo=bar redirects to /example2?foo=bar?foo=bar instead of /example2?foo=bar.

The fix extracts query params before regular expression replacement, strips them from the URL, then merges the query parameters back by using getRemapUrlWithQueryString(), which handles the existing ? correctly.

Query parameters are preserved exactly once in redirect URLs.

A value used in Workflows was not being correctly type-checked, which caused a PHP fatal error in certain circumstances.

The value causing the fatal error now has correct type checking in place.

The ability to preserve legacy handling of HTML entities and special character encodings was added in 6.80.0 as described in the January 2026 errata.

It was discovered that this feature change could not accept null values from other parts of the codebase. Fatal errors were generated (including visible errors on the frontend interface) when certain variables or keyword modifiers are used.

The fix combines Null values into an empty string before handling.

The original fatal errors no longer occur, and null values are treated as empty strings.

Squiz Content Management was unable to cache asset URLs in DejaVu, so whenever URLs were used, a Database lookup was required even if the asset was already cached in DejaVu.

Squiz Content Management will now cache asset URL information in DejaVu alongside the rest of the Asset details, reducing database queries and improving page render times for pages with many URL lookups.

Squiz Content Management was unable to cache asset permissions or major links (Type 1/2) within DejaVu, so any requests had to go to the database to fetch those details.

Squiz Content Management will now cache asset permissions & major links (Type 1/2) in DejaVu alongside the rest of the asset details, reducing database queries and improving page render times for pages with many URL lookups.

The "missing zone" reason is attributed to top-level zones changing from page-managed to locked.

An incorrect zone reason was displayed for template-locked top-level zones in unused content.

Detect when the page managed zone specifically changed to template-locked and assign the correct reason.

The correct locked zone reason appears when the page zone is changed to template-locked.

Unused content zones could sometimes appear in a random order and not align with the zone order in the template/page.

Zones in unused content appear in the order they are on the page/template, with any deleted zones appearing at the top.

Each code sample in the Data Services documentation now shows the configuration file it is associated with.

This additional prescriptiveness will help readers clearly identify which persistent file any given code sample is from.

Mentions of server components and server-based static file support documentation are now unavailable in the Component Service documentation.

Read the February 2026 enablement updates section to learn more.

A bug was discovered where the date filter plugin threw an error when the Facebook Data Source returned a page type other than POST or EVENT.

The plugin was updated to process page types other than POST or EVENT.

This plugin was changed to allow reading the last x-forwarded-for IP address from the access_restriction.prefer_x_forwarded_for parameter.

This change lets the plugin retain the last IP address if the option is set. This behavior is required by Content Management and Squiz Search to properly track the locations of users who request searches through Content Management.

Documentation required updates that reflected the behavior of search user accounts in Squiz DXP.

Added notes on search user account behavior when DXP users are turned off or re-enabled.

Read Squiz DXP Console Search Custom Roles documentation for more information.

The documentation lacked operational nuances and exhaustive technical restrictions relevant to custom roles in Squiz DXP.

Consolidated all technical guardrails, operational behaviors, and best practices into the public documentation.

Read Search Custom Roles documentation for more information.

The Datastore documentation feature page for JavaScript SDK did not contain links to the SDK.

Improved the aggregation feature page to clearly link to the JavaScript SDK usage page, which now contains links to the SDK itself.

Read Datastore Aggregation documentation for more information.

Read the February 2026 new features to learn more.

Read the February 2026 new features to learn more.

Read the February 2026 new features to learn more.

Read the February 2026 new features to learn more.