November 2024 Releases
Learn about the changes to Squiz DXP released in November 2024.
Looking for release info before October 2024?
Visit the changelog areas for each DXP capability for features and changelogs published before October 2024.
- Advanced Forms
- Component Service
- Content Management
- Data Services
- Integrations
- Search
What’s new in November 2024
The November 2024 release focused on improvements relating to the Content Management area of the DXP.
Content Management
- Add option to show a general warning for fatal errors or uncaught exceptions on websites
-
When server errors were encountered, output buffers were printed without final processing. Unprocessed code, such as keywords or server side javascript could be output under these circumstances.
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.
Something went wrong trying to render this page... Request ID: b34b5303-a5ca-454c-9eb0-09ab6e4e37720
The request ID can be used to find the uncaught exception error through the Error log in the Log Manager instead of trying to use the partially rendered content to diagnose the issue.
What’s changed in November 2024
In addition to the new features released in November 2024 the following bug fixes and improvements were released across the Squiz DXP.
Type | Description | Capability | Release date | Release version |
---|---|---|---|---|
3 Bug fixes |
Manifest error message when component manifests or schema are not available DetailsIf 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. |
Content Management |
2024-11-07 |
CMS/6.50 |
2 Minor improvements |
Improve component error removal logic DetailsWhen 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. |
Content Management |
2024-11-07 |
CMS/6.50 |
2 Minor improvements |
LDAP timeout needs to be configurable DetailsLDAP 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. |
Content Management |
2024-11-07 |
CMS/6.50 |
3 Bug fixes |
Metadata screen can produce an unsaved changes popup when no changes have been made DetailsA 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. |
Content Management |
2024-11-07 |
CMS/6.50 |
3 Bug fixes |
Fatal errors from RenderTimeLimit DetailsThe 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. |
Content Management |
2024-11-07 |
CMS/6.50 |