September 2025 Releases

The comparison used to check which component is selected wasn’t checking against the component set. Regardless of the component set, any component with the same name appeared to be selected.

The comparison check now compares against the slug, version, and component set. The correct component can now be selected based on the component set it is a part of.

Inline Squiz Link and Squiz Image selection buttons were rendered in read-only mode. Users could change a Squiz Link or Squiz Image for a read-only section of the page.

The fix ensures that inline Squiz Link and Squiz Image selection buttons no longer render when in read-only mode. Squiz link or image selection is no longer visible for read-only sections on a content page.

Long-running cron job processing could run concurrently, resulting in Out of Memory events on the cron system.

Cron jobs would stop running and deadlock, causing functionality relying on these processes to fail.

The fix introduced the LongRunningJobRunner to process long-running cron jobs independently of the regular cron jobs to ensure long-running cron jobs are never run concurrently.

This change reduces the possibility of cron jobs failing due to out-of-memory fatal errors and provides better debugging tools.

Redirects for an asset on the /__data path could unintentionally redirect back to the /__data path. This behavior could cause a redirect loop and confuse users.

The redirection logic now checks for this scenario. It only redirects if it discovers a non /__data path URL for the requested asset. Redirects from the /__data path will no longer redirect back to the /__data path.

Previously, component-dependent parents needed to be looked up by multiple pieces of functionality on the standard page Contents screen.

The contents screen on standard page assets loads faster because of improvements to how the lookup function parses the component-dependent parents.

An array-only method was used on a value that was not an array, which caused a fatal error in certain metadata time triggers.

The value is now checked before calling the array-specific method, which prevents the fatal error from occurring.

A non-numeric value was used in a date-related function requiring a numeric value. This condition could contribute to causing a fatal error during a cron run.

The value is checked before use to determine if it is numeric. Cron runs will no longer experience a fatal error due to the presence of non-numeric strings in the formatDateTime method.

Changes in the metadata UI code caused the custom edit layouts metadata section keywords to always assume the section ID was valid. Invalid metadata section keywords would generate a fatal error, making the contents screen unable to load.

Metadata interface code was adjusted to protect from invalid metadata section keywords. Custom edit layouts referencing invalid metadata section keywords should function as they did before 6.70.

Previously, the system would retrieve all lock types for an asset individually, resulting in more round-trips to ElastiCache than required.

The minor improvement uses the Redis MGET request type to retrieve all lock types of an asset in one request, improving performance.

A feature of the Page Builder Service’s WYSIWYG editor is to open links in the content page preview in a new tab rather than the preview frame navigating to another page.

Because of this opening behavior, inline editable links were incorrectly updated to open in a new window with target="_blank", even if explicitly changed to exclude the logic.

The code that sets preview frame links to open in a new tab now ignores any links within an editable region. Inline editable links can now have their target set correctly.

The collection alias endpoint returned a 500 error when both endpoints did not share the same event property configuration. This condition meant that requests could not be made to the affected endpoints.

A fix was implemented to the endpoint, allowing collection requests to alias endpoints where event properties differ.

Dependencies have been upgraded to address security issues, ensuring a safer and more reliable system.