DXP Releases for 2024

Modifications have been made to the Resource Browser header, enhancing user experience when utilizing the resource browser in conjunction with other systems.

Read December 2024 Releases to learn more.

Top-level object fields in the component editing UI have been redesigned as collapsible accordions, allowing developers to more easily group related fields.

Read December 2024 Releases to learn more.

The Dates screen has been added to several types of Metadata Schemas, Sections and Fields.

Read December 2024 Releases to learn more.

Trigger categories were sorted via an expensive calculation for display in the Asset Tree every time a Trigger was loaded. This led to noticeable slowdowns on systems with over 500 triggers. As a result, the sorting process has been optimized, only being applied when necessary.

On certain metadata screens, Viper could be initialized too early without any HTML to attach to. This premature initialization could cause JavaScript errors and prevent usage of the metadata screen. To address this issue, a rigorous check has been implemented to ensure that HTML is rendered before attempting to attach Viper.

The global access token was not being filtered by the frontend, allowing public users to potentially manipulate it. As a result of this issue, implementing a filter has corrected the problem, ensuring that the global access token is now properly secured.

Type 2 links weren’t configured to show tooltips, preventing them from being displayed when hovering over assets of this type. This issue has been resolved by updating the CSS configuration.

The System Configuration screen now offers the Do not show fatal errors and exceptions on frontend setting in the Error/debug settings group. When this setting is activated, fatal errors or uncaught exceptions show a general warning and a Request ID.

Read November 2024 Releases for more details.

If there was an issue loading a manifest or schema for a component, the content page could not be saved and an error is shown. Users were unsure which component or variation needed to be removed to save the page because the error was not tightly linked to the component or variation with the manifest error. An error is now shown for the component or variation in question so that the user can identify which component needs correction before the page can be saved successfully.

When a content page component was loaded with a manifest fetching error, the only way to fix the error was to delete the whole block because the manifest fetching error could remain and block users from saving. When deleting a variant that contains errors on a component, the cache refresh now runs to clear up any errors persisting in the cache from the erroneous variant and allows the page to save.

LDAP bridge assets now offer a configurable Network Timeout field. This field allows setting the timeout for a connection to the LDAP server and defaults to 10 seconds. Ten seconds was the previous limit, but it could not be configured per bridge.

A race condition was observed when React.js components took over 1 second to load on the Metadata screen. The unsaved popup appeared even though no changes were made on the Metadata screen due to the screen’s state being empty. The state is now re-initialized inside the Metadata screen code, which prevents the popup from appearing if no changes to the screen are made.

The RenderTimeLimitException, introduced as part of the Enable Render Short Circuiting beta feature, was unhandled on some code paths. The unhandled exception could cause unexpected fatal server errors. RenderTimeLimitException is now handled on the identified code paths and prevents errors from occurring.

Storage metrics for File Store are now being collected. Read October 2024 Releases for more details.

Success and error log support is now available in the File Store. Read October 2024 Releases for more details.

File Store now offers a scalable virus scanner stack that allows files to be processed more efficiently. Read October 2024 Releases for more details.

Static site serving when serving a folder’s index.html file will now redirect to the version of the folder with a trailing slash. Read October 2024 Releases for more details.

Added logging for static site setting changes to display in the DXP Console log service.

Logs now appear in the log service when a tenant setting is changed for auditing and support purposes.

Adding URLs to API endpoints allows users interfacing with the REST API to view the mapped URLs for a file. You can now view file and folder URLs returned from any endpoints within the REST API.

Improved virus scanning batching and error reporting to reduce wait times for file deployment or static site updates. File scans occur more frequently and efficiently, leading to faster access and deploy times overall.

Increased cloud infrastructure memory and processor limits to improve request processing times and faster request handling. API requests to directories with large numbers of files are now more performant.

Minor tweaks to styling for components with no fields (preconfigured components) inside content page assets are available in this release.

The Component info label in Page Builder content blocks was missing the action keyword like other labels in this area. The label is now updated to View component info which improves the consistency of the Actions menu language.

Internal cloud version history triggered deletes from the File Store DB, causing some API requests to miss files. This abnormal delete operation caused a temporary impact on API queries showing all files within a directory. A validation script was updated to keep file and DB storage in sync, ensuring no lasting performance impacts.

Special reserved characters in file names or paths caused the virus scanner queue to become deadlocked. The virus scanner could slow down or become unresponsive until the issue was resolved. More robust handling of virus scanner queuing was implemented. The virus scanner now functions more efficiently and can self-recover from issues.

A race condition occurred when uploading large files using multi-part upload, causing the virus scanner to mark the placeholder file as the newest version. The race condition affecting the virus scanner made large files difficult to upload and process. In some cases, the files became corrupted. The race condition was removed which means that File Store can handle multi-part uploads correctly.

The way components were added to standard pages is by submitting a form. When the form was submitted, page validation was executed, and any required fields caused validation to fail. Components with required fields could not be deleted until valid values were added to the fields. The fix now skips or forces validation to pass when deleting the component. Components can now be deleted without filling in their required fields.

An issue with strict code typing on certain trigger event actions caused triggers that watched for Before asset deleted events with a Trigger log message (Error) action to run after the HIPO job deleted the asset. This code typing behavior caused the trigger actions designed to prevent assets from being deleted based on the error status sent to the logging system to be ignored by the HIPO delete process. The strict code typing for the trigger action was relaxed so that the trigger action fired before the delete action ran in the HIPO job. If Error is selected in the trigger action, the Before asset deleted trigger condition prevents the HIPO job from deleting the asset.

Cloudflare was unable to refresh the cache for authenticated users. Authors could see old content on the frontend for an extended time. Stale requests from Cloudflare are now always rendered as the public user. The Cloudflare cache will now refresh for all user types.

Tracking used to prevent circular dependencies in keywords was stored in the session. If a fatal error occurred during an %assets_contents% keyword render, that user session could not later render anything with an %asset_contents%` keyword. This incorrect user session state would often result in all asset listings rendering without contents for the session and potentially entering the cache for other users. The circular dependency tracking was moved to track at the request level. Fatal errors within the circular dependency tracking no longer affect other requests or users.

The render time threshold was constrained to 60s. Legacy-hosted Content Management instances might have very large or slow-loading pages that could not be generated after upgrading to 6.47. The threshold restrictions were adjusted to ensure the value was an integer. Legacy-hosted Matrix instances can now generate large, slow-loading pages.

Components were being obstructed with an error message when they experienced issues with fetching their manifest or schema after being added to a page. Under these conditions, the component cannot be deleted, edited, or saved. The error block now offers a remove option so it can be dismissed and the normal function returned to the component editing experience.

Styles that controlled the look and feel of the Content Page builder were not applied correctly which caused the preview window to function incorrectly. Feature scope rules were updated so that the styles that control the look and feel of the Content Page Builder are now correctly applied.

If the binoculars need to switch trees to find an asset that is not found underneath the current one’s restricted root node, the current selection was cleared on the original (and thus incorrect) asset tree. Multiple assets could be selected on the newly shown asset tree when using the binoculars. The asset selection-clearing logic was updated to match the existing selection-clearing code logic. Only the asset being located through the quick search feature is selected.