February 2025 Releases

The push data source and filter classes ignored the filter.class configuration key. This key was required for each MODIFY request sent to the push API. The lack of the configuration key caused unexpected behavior between data sources depending on the type.

The change implemented applies the filter.classes configuration key value for push data sources if no filter query option is provided with the push API request.

The SEO auditor returned internal content created for accessibility auditing purposes. The incorrect common words appeared in the audit results, making it difficult to interpret them.

The content was removed from the SEO auditor to no longer affect legitimate results returned to users.

The StringDocumentFilter generated an illegal character error when processing a URL set by the plugin, which caused errors while updating the data source with plugins applied.

The plugin framework tool can now handle special characters such as | in the start URLs. A raw string is first converted to a Java URL object and then encoded into a Java URI object while ensuring special characters are accepted by URL and not URI.

Users can now preview configuration files, including metadata-mappings.cfg, xml-index.cfg, and site_profiles.cfg through WebDav and the configuration file manager.

The configuration is displayed in raw format, and users can copy it between different instances or resources.

This minor improvement removes the often cumbersome, time-consuming, and error-prone approach of manually entering the configuration information using the dedicated Administration UI.

The username or password label used for form authentication could be inconsistent. For example, the form label for the username could be email instead of username. Under these conditions, the external crawler could not find the matched username/password value(s) for pre-crawl authentication.

Data source configuration keys were added for username and password labels when encountered in either pre-crawl or in-crawl authentication requests. Username and password labels that are not the typical username/password form labels are now handled correctly.

If a user did not have the correct permission to modify configuration keys in an attempt to update it, instead of the relevant error message the UI was displaying [object] [object].

The error handling under these circumstances was improved so that the user either receives useful feedback about the invalid value of the configuration key or the lack of permissions they hold to modify the key.

Cutting out and pasting back exactly the same content into a FreeMarker template was causing the system to save an empty file.

The system now prevents empty files from being saved when cutting and pasting the same content into the template editor.

The push system attempted to clean up all data sources running as query processors but failed because the document data and delete lists were missing. When setting the push optimization features, the “prepare Funnelback for upgrade” feature failed.

Push optimization features were adjusted to skip cleaning up data sources in SLAVE mode when preparing to run an upgrade. These adjustments allow the optimization features to iterate past the skippable collections and complete the process.

The !FunDoesNotExist:padrenull plugin query appeared in analytics reports because it indicated empty search results. Customers were unsure what the plugin query meant in the context of the analytics report. This confusion caused unnecessary support cases requesting that the plugin query be manually added to the denylist of each affected Squiz Search instance.

The item !FunDoesNotExist:padrenull was added to the global denylist, which prevents the plugin query from appearing in analytics reports.

If the display of a key depended on the value of another key with a parameter, only the first key value with a parameter would be taken into account, instead of any that fulfilled the condition. Adding the next key with a wildcard that fulfilled the dependent key condition would not display the dependent key form to provide its value.

The fix displays the dependent key form if any key with a parameter fulfills the condition instead of only the first key value. Users are now able to provide plugin configuration details.

A new plugin named Faceted navigation - advanced sort by date lets you sort faceted navigation based on dates that use a custom format. This plugin provides an input date format and converts it to a consistent and sortable output format of YYYYMMDDhhmmss.

You can sort a metadata-based facet by date, where the dates are represented in a custom format. If you have facet categories like Jan 2010, Jun 2021, Nov 2019, the facet categories can now be sorted by a normalized date. The plugin converts the metadata labels to dates internally before sorting.

The original maximum timeout that could be set for crawl requests to a web page was 30 seconds. Pages that exceeded the 30 second crawl timeout would not be processed during an update.

The maximum timeout that can be set for crawl requests (crawler.request_timeout) was increased to two minutes (120 seconds). If the crawl request timeout configuration is set to the maximum value, then web pages that take over 30 seconds will now be processed

An aurora replication lag between the read and write database caused issues with determining which metadata version to use when a chained metadata trigger applied updates to an asset. If a chained metadata trigger update was in progress, a second running trigger failed to update the metadata value.

Time checks were added between saving and the next attempt to read the database to determine if the trigger should read from the original database instead of the replica database. This check ensures the most current database is used.

The following types of transient errors were causing OAuth to unexpectedly fail, triggered fatal errors, and ultimately prevented users from continuing with the authentication flow:

Users experiencing these transient errors would see an ungraceful failure in the authentication process and would need to manually restart their attempt.

OAuth authentication has been updated to automatically retry the process in the event of transient errors. Instead of immediately triggering a fatal error, the system now attempts multiple retries before stopping authentication completely.

This change significantly reduces the likelihood of failures and ensures a smoother experience.

Content Management users with system administrator or root user permissions can now set a custom warning message and limit through the Global preferences  Configure warning and limit for containers per standard page setting.

The alert appears when content authors have either reached or exceeded the recommended number of components on the standard page they are creating.

This setting will help content authors make better decisions about how they are building content using standard page assets and will avoid performance issues when configuring too many CCTs on a standard page.

Asset listings were using inefficient methods to query data, work on the data structure, and sort the result. As a result, sorting and rendering results in asset listings was slow, and memory intensive.

Improvements were made to provide a more efficient approach of querying data, modifying data structures and sorting results. These improvements result in better asset listing load performance.

When an asset was published or set to live, a bug with how version history event listeners were loaded caused minor version history entries (for example, 0.x.0) to not be recorded. This issue caused inconsistencies between the documented versioning rules and the stored version history, making it difficult for users to track version changes.

The event listeners are loaded before proceeding deep into the HIPO execution path. Customers can now reliably track minor version history updates made to assets.

There was no mechanism in the stylesheet to show a scrollbar when the root node drop-down height exceeded the browser viewport’s height. When many root nodes were in the drop-down, some entries at the bottom could not be selected.

Updated stylesheet rules were applied to the root node drop-down to show the scrollbar when needed. The stylesheet change lets users scroll the asset tree and select the asset they need from the list.

A blank content page triggers an issue where the reload button appears clickable but does nothing, leading to user confusion.

The logic for the reload button was modified to perform its intended function even when there is no content to be reloaded. With these changes, the reload button now correctly performs a reload action and animates upon click.

A recent issue occurred when an unexpected and unhandled error was detected within a component while evaluating JSON schema for live previewing Squiz Content Management asset pointers. This error prevented all of Page Builder from loading.

Error handling has been added to mitigate JSON schema interactions that cause errors when fetching Squiz Content Management asset pointers. A customError block issue type and improved error messaging have also been introduced to report errors handled by the system, providing users with instructions on how to proceed correctly.

In Preview mode, users encountered an issue where the total segment count was not visible when selecting multiple segments, particularly when the longest priority segment had a lengthy name.

This limitation has been addressed by displaying the total segment count in Preview mode, even when the highest priority segment is selected with a long name.

Following feedback from our APB beta testing, it was observed that users were experiencing confusion between the Page Builder Edit mode toggle button and the button used to acquire page locks in Matrix.

To clarify this, we have renamed the "Edit mode" toggle button to simply "Build mode", streamlining the user interface to reduce potential misunderstandings.

Previously, the File Store UI did not support uploads larger than 50 MB while the API handled up to 100 MB.

This change brings the UI up to API feature parity, offering a more convenient way to manage files through the UI.

When configuring a CDP event with an Authorized condition, the Events UI did not protect against selecting unsupported rule types or typing string values when the condition required boolean values.

To fix this problem, the Authorized event condition now automatically fills the correct values, which are read-only and set to equals true. Users can now configure Authorized event conditions that behave as expected.

Fixed how the Queues page renders for retry flows.

Fixed a RangeError: Maximum call stack size exceeded console error when navigating to a locked workspace using the Tenant Admin UI.

Fixed an issue where the erroneous filter was not applying when redirecting from the Dashboard to Executions.

Fixed an issue where some threads were missing on the Execution page after applying specific filters.

Fixed an issue where the three-dots menu was not clickable when the full-screen mode was toggled for the credentials menu.

Fixed an issue in the Implement tab where changes to the shutdown timeout for a flow did not apply without refreshing the page.

Fixed an issue where unnecessary \ characters were added to the $getPassthrough() expression when the user switched the mapping section from developer mode to integrator mode.

This component is a copy of the existing Email component, enhanced with the ability to set custom credentials.

This addition allows flexible management of different domains, workflows, and API keys.

REST assets had code that only functioned if they were running within a web request with "Append Query String" enabled. If REST assets were used through a scheduled task, the task would fail to run and cause a cron deadlock.

REST assets have been updated to assume an empty query string when running without a web request. REST assets with "Append Query String" enabled can be run from scheduled tasks.

The upgrade to PHP 8.1 altered the behavior of a control statement that caused an unexpected assignment of a null value for an element in the $asset_ids array. This condition occurred when an empty Link Information value was saved on a Link asset. The issue caused a fatal error and prevented users from saving link information.

The control statement was updated to explicitly handle cases where $_REQUEST[$prefix]['assetid'] is not set or is null before adding it to the $asset_ids array. This change prevents invalid asset IDs from being introduced into the system. Users can now save empty Link Information values if they need to.

Mirror and asset syncing operations only searched for asset IDs in specific patterns to avoid treating random numbers as asset IDs. Designs that specified a Menu Normal Design Area with a root_node asset ID configured directly in the parse file would be erroneously excluded from the search and break the imported design because they failed to migrate.

Mirror was updated to match asset IDs in Menu Normal Design Area root_nodes, which allows them to migrate correctly with Mirror or asset syncing.

The value for Global preferences  Component preferences  Default presentation types was not correctly set for custom components. If Article was the default presentation type, the custom component used block (div) when a user created a custom component.

This fix ensures custom components use the default presentation type specified in Global preferences.

Quick options in components initially supported enum properties. This release has expanded quick options properties to support boolean types. This minor improvement helps component developers create more flexible components that meet organizational needs.

The subscription anniversary date was manually set against a customer’s subscription, but was not being updated when the anniversary date passed. This meant that customers could not see accurate dates and usage data against their DXP subscription.

The subscription anniversary date now automatically updates for each year that passes, always showing the most up-to-date anniversary date. DXP subscription usage will be relative to that date.

Functionality to update access within Advanced Forms was only passing updated access requirements and not the user’s name, which accidentally overrides the name with "undefined". Any reporting or viewing of users will show "undefined undefined" as the author’s name.

With this release the full name of the user is updated in Advanced Forms each time their access is updated. Full names of users are correctly showing up in reports.