October 2026 Releases

The Set File Contents trigger checked file ancestry using type info that was not always loaded earlier in the request on PHP 8. Triggers could fail with a server error instead of updating the file or returning a controlled failure. The action now loads type ancestors before the file check. Set File Contents runs without that error on PHP 8, and non file assets still fail the action without a fatal error.

When asset cleanup update lookups failed, error details were built from raw HIPO rows instead of their message text. AMAPI asset cleanup could return opaque errors in responses and logs, which made permission, lock, or lookup failures hard to diagnose. We now extract HIPO message values before building the exception string, with the same approach for purge trash errors where applicable. Failed update lookups during AMAPI asset cleanup now surface readable messages so operators and integrators can see why the step failed.

API users can provide a url query param to any by_url endpoint to resolve an asset. But this url lookup did not work if the value included suffixes (e.g. /_nocache) or query params.

After this change, an asset can now resolve successfully with these additional URL components.

When URL path exclusions were applied to a site crawl after an initial indexing run, some previously indexed URLs could still be cited as source pages in chatbot and Question/Answer responses.

Changes have been made to the index during crawl updates, ensuring that excluded pages are never cited as response sources.

A recent change stopped passing through the HTTP status from the upstream API when visitors open a REST Resource page directly on the public site. Error responses were often sent as a successful page load instead of the real error status.

Edge caches and monitoring tools could not tell a failed API call from a successful one. Caching rules that depend on error status did not behave as expected. Integrations that rely on standard HTTP status codes could misread failures.

Direct requests to a REST Resource page again use the upstream HTTP status when the API returns an error or the connection fails. A new Expose HTTP status on frontend option on the REST Resource lets you control this: it should be enabled when passing the status directly is desired, and disabled when your Javascript will process any errors.

Caching and observability can now use real error status codes where you enable the option, while existing Javascript-based error handling can stay on the previous behaviour when you leave the option disabled.

Recipient de-duplication ran before trimming whitespace around each address.

The same person could receive multiple copies of one email when their address appeared more than once with different spacing (for example from permission keyword lists combined with plain To rows).

We now trim and drop blank entries before de-duplicating recipients, and use the same list for sending and outbound logging.

Each intended recipient now receives one email per send.

When a content page is in workflow waiting for approval status, a user that otherwise has write access could be blocked from front-end rendering unless that status is specifically exempted from the default behaviour.

Workflow waiting-for-approval statuses are now exempt from blocking page render when the user would otherwise have access.

Users can see the page preview in Page Builder after setting the content page to waiting for approval.

When content is copy/pasted into Viper from an external source it may include empty elements. If those elements appear at the end of a node list within a container, the browser may not render them when it cannot calculate the size of the bounding box. When an empty list item is in that state and the site CSS removes the default bullet, the browser will not render the element in the Formatted Text Editor and a user cannot delete the element.

Empty list item elements now receive a style that places a space in the context so the browser can render the element.

Users can delete empty elements within the Viper editor.

When a component in a locked zone on a template was upgraded to a new version, both the page and template could try to upgrade it. Saving only the page could leave the component out of sync with the template and trigger a persistent unsaved changes alert.

Version upgrade for components in locked zones on a page is now prevented so the component does not get out of sync with the template.