September 2026 Releases

The help text on the Workflow Rejection Message screen stated that the message is sent only to users on the same workflow step who were able to approve. That description did not reflect actual system behavior. The help text has been updated to state that the message is sent to all users on the current step, as well as users who were able to approve in previous workflow steps before the message was sent.

When morphing a file asset to an incompatible type (for example, a PDF File asset to a Microsoft Word document asset), warning messages are triggered correctly, however the existing file was unexpectedly removed. Users could therefore no longer access or download the file.

If a file cannot be morphed to the selected type, the original file now remains on the asset instead of removing it, with the user receiving a clear warning when morphing is not allowed.

Creating a new iCal Data Source, or opening its Details screen before a feed URL was configured, could show an error and stop user from using the asset.

The iCal Data Source now skips attempting to load the items in a feed if the feed URL is not configured, including upon initial creation.

When form submissions are deleted from the Custom Form Submission Logs screen, deleted submissions were removed from the list but were not placed in Trash, thus orphaning them. This meant the assets could not be purged without a system administrator recovering them via the Orphaned assets tool first.

We corrected the deletion process so submissions are now properly placed in Trash as expected.

By default, Form submission assets are not restricted from read access when disconnected from the respective form asset. This means, if the default denial of public read and write permissions are removed from the submission, it is possible for public read permission to be cascaded to it, making it available for view.

When a form submission is no longer linked to a form’s submissions folder, it now only becomes accessible to users with admin permission, overriding normal read and write permissions. This is the same behavior as if the form submission was contained inside a form with the Restrict submission access setting enabled.

The Asset Management API updated web paths via saveWebPaths() without passing the remap manager’s Automatically add remaps when webpath changed setting, so automatic URL remaps were always added on webpath changes.

Asset Management API webpath updates now respect the remap manager auto remap setting and no longer add automatic remaps when the setting is off, matching admin UI and Update Lookups HIPO behaviour.

An earlier bug fix caused a regression in the JavaScript API asset where if multiple function requests are combined using the batchRequest function, the added check for a well-formed target asset ID was being performed when the batched function does not use the concept of a target asset.

This means that these functions would fail with an error message The asset id must be a string or number, potentially blocking the remainder of the batch if blocking was enabled.

The well-formedness check has been updated to correctly handle functions that do not require a target asset, so that these functions work properly again.

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

Unrestricted file assets, accessed via the /__data path, were served with a header requesting 30-day browser caching, which could persist even when a CDN or customer cache policy was configured to revalidate sooner. End users could keep stale copies of unrestricted files in the browser for up to 30 days, and customers who relied on shorter CDN cache behaviour saw inconsistent results between the edge and the browser.

Unrestricted files accessed via /__data are now sent with a header requesting a shorter browser cache period of 24 hours, along with a 30-day stale while revalidate period. Browsers will now refresh unrestricted /__data content after 24 hours, while CDNs can still hold and revalidate assets for up to 30 days.

When deleting a content page, validation was done against the page content and if a layout had been deleted from the system, validation failed and the page was unable to be deleted.

Validation against page content was unnecessary so it was removed, Content pages with missing layouts can now be deleted.

Opening the Paint Layout tab for an asset that did not have a paint layout linked could cause the screen to display errors instead of showing the normal layout settings. Users could see error messages when viewing the Paint Layout tab on affected assets. This made it difficult to review or update paint layout settings for assets that had no layout assigned yet.

Paint Layout screen now opens correctly for assets with no linked paint layout, displaying the expected settings view instead of errors. User can open the Paint Layout tab on any asset and manage layout settings as expected, whether or not a paint layout is already linked.

When a user downloaded a log file from Log Manager on a Windows computer or browser, the system adjusted line endings in the file before sending it. For large log files, typically around 10 MB or more, this extra step took too long and the download timed out. Users on Windows could see an error, such as a gateway timeout, when downloading large log files from Log Manager. Smaller files and downloads from Mac or Linux were generally not affected.

Log files are now sent directly without changing line endings for Windows users. Modern Windows applications, including Notepad, open these files correctly. Users on Windows can download large log files from Log Manager reliably, in the same way as users on other operating systems.

When looking for expired workflow jobs in the expired workflow scheduled job, or for obsolete Asset Version History versions to remove, all potentially matching entries were fetched from the database. When there were many rows returned, memory could be exhausted, resulting in scheduled job manager failures.

The queries were moved to use lazily evaluated database cursors. Memory pressure is greatly reduced during deleting obsolete Asset Version History entries and searching for expired workflows.

When retrieving the content containers for a page, when running the manage incomplete submissions scheduled job, and in some situations when printing the contents of an asset listing, assets were loaded into the internal asset cache, but missing the indication that the references could be freed. When these actions are performed repeatedly, such as during a scheduled jobs manager run, the references accumulate, and the allocated memory exhausted, leading to a fatal error.

Appropriate calls to allow freeing the internal asset cache for cache entries created were added during the appropriate actions. The asset cache entries created during the actions can be freed, and the asset cache size settings can be respected.

OAuth 2.0 Two-legged for global storage could stop working once the token expired. On public pages, there was no way to refresh and save a new token without write access.

A new optional setting, "Allow automatic global token refresh", is available when token storage is set to Global permanent. When enabled, an expired access token can be refreshed and saved automatically, even for visitors who do not have permission to edit the connection.

Unrestricted files under /__data with a 30 day public cache (expires 30d) when served directly from the web server process. That long browser cache could persist even when a CDN or customer cache policy was configured to revalidate sooner. End users could keep stale copies of unrestricted files in the browser for up to 30 days. Customers who relied on shorter CDN cache behaviour saw inconsistent results between the edge and the browser.

Web server configuration for the /data location was modified to send Cache-Control: public, max-age=86400, stale-while-revalidate=2592000 (24 hour browser cache with up to 30 days stale while revalidate at the origin). Browsers refresh unrestricted /data content within 24 hours while CDNs can still hold and revalidate assets for longer. Reduces unintended long lived browser cache for unrestricted file URLs.

When restricting form submissions when detatched from their form in 6.96.0, a regression was inadvertently caused. Incomplete submissions for multi-page forms were restricted so that effective read access to the submission required admin permissions, where the creator of the submission is only granted write permission. This meant that although users could initially write incomplete submissions, they could not read them back to progress them further. Users were thus no longer able to access their incomplete submissions to continue them.

Incomplete submissions were explictly excluded from restrictions, where the code before 6.96.0 had done so implicitly. Users will now be able to continue their incomplete form submissions.

This feature is on the feature restrictions screen (as well as the content editor feature restrictions screen) and will restrict users from being able to toggle certain 'Cascade' options when moving an asset.

So that certain users can not bypass the schemas already applied.

If applied, users will not be able to uncheck the 'Cascade' options this applies to (Workflow, Roles and Permissions).

Read the September 2026 new features to learn more about the benefits of Consentless personalization.

Read the September 2026 new features to learn more about managing PDF files through Asset Management API.