August 2025 Releases

Learn about the changes to Squiz DXP released in August 2025.

Visit the changelog areas for each DXP capability for features and changelogs published before October 2024.

What’s new in August 2025

No new features announced yet in August 2025.

What’s changed in August 2025

Other minor improvements and bug fixes for this month are described in the changelog table.

Type Description Capability Release date Release version Link

3 Bug fixes

The null field does not work in the oneOf composition

Details

The null option within the oneOf schema could be auto-transformed to an undefined value. This transformation caused the schema validation to fail. Subsequently, it blocked the selected null option from saving on the content page.

When handling changes under the component edit form, the fix adds a transformation layer to ensure the unexpected undefined value is normalised to null (for oneOf composition only).

The null option within the oneOf schema can now be saved successfully on content pages.

Component Service

2025-08-01

6.69.0

4 Important changes

All suffix-related fields in the System Configuration page are no longer editable

Details

The Preview option in Page Builder content page assets does not work with a custom /_nocache suffix.

All customizable suffixes on the Content Management System Configuration screen are no longer editable from this release onwards.

Effective date: August 1, 2025

Content Management

2025-08-01

6.69.0

3 Bug fixes

Unable to add GET parameters to Nested Content

Details

Due to the PHP 8.1 upgrade in function signatures, htmlspecialchars was escaping single quotes in the nested content area. The system did not properly identify the GET parameters in nested content, and they were not saved.

The fix adjusts the htmlspecialchars behaviour to prevent escaping single quote characters, which allows GET parameters to be saved.

Content Management

2025-08-01

6.69.0

3 Bug fixes

Stop "Attribute …​ not found" warnings for keywords

Details

Squiz Content Management was generating warnings for keywords that accessed attributes that did not exist.

Depending on the configuration, warnings would appear on the frontend. More generally, the error log would contain many warnings about missing attributes that were ignored because the implementation worked fine with the missing data.

The fix makes adjustments to the asset_attribute keywords so they do not produce any warnings when something is wrong with the keyword. This change brings this keyword behavior inline with most other keywords. Implementations (such as designs) that generically reference attributes that can sometimes be missing will log fewer warnings.

Content Management

2025-08-01

6.69.0