Last updated: 17th September 2026
Released: 17th September 2026
When you upgrade your website to the latest version of Acquia Site Studio, the system applies database updates. These updates prevent the database from rolling back to the previous version.
Acquia recommends that you apply updates in your development environment and back up your website, including the database, before you upgrade Acquia Site Studio.
Site Studio Page Builder supports Navigation module in Drupal 11.3+. The Page Builder button opens in the Navigation top bar to enable access to visual edit mode.
The Page Builder button opens in the Navigation top bar after the Navigation module is enabled in Drupal 11.3+. On Drupal 10, the button continues to open in Admin Toolbar.
None.
No.
Resolves an issue where the token browser does not display all available tokens on components. An unnecessary context restriction prevented token display.
All tokens display in the token browser on components.
None.
No.
Resolves an issue where a View row rendered inside a component drop zone displays only the first result across every row, instead of iteration through the view results.
Views render each row correctly.
None.
No.
Resolves errors during a rebuild process after modules such as Event-Condition-Action (ECA) are enabled. Site Studio validates tokens before transmission to Site Studio Application Programming Interface (API) and omits invalid tokens from processing.
Modules such as ECA do not cause errors during a rebuild.
None.
No.
Resolves an Asynchronous JavaScript and XML (AJAX) error that occurs during a new preview image upload for a component with one attached tag.
Users can upload a new preview image for a component with one attached tag without error.
None.
No.
Resolves a fatal error triggered during a translation request through TMGMT on content with an empty or uninitialized Layout Canvas field.
Translation requests through TMGMT execute without fatal errors when content contains an empty or uninitialized Layout Canvas field.
None.
No.
Resolves an issue where a cleared Video URL field in a component form repopulates default values during component re-render.
Content editors can clear video URLs from component forms and maintain empty fields without default URL repopulation.
None.
No.
Resolves two input issues that lock the dx8-gateway Node service during posts to the /build/style endpoint. Both inputs drove the Cascading Style Sheets (CSS) value parser into an infinite loop and caused request expirations:
A font stack that contains a Google Fonts stylesheet Uniform Resource Locator (URL) with pipe characters.
A style value that contains a non-breaking space (U+00A0) adjacent to a function, such as a box-shadow or RGB value pasted from a rich-text editor.
Style compilation completes for these payloads. URL-shaped font stacks stay preserved as quoted values. Non-breaking spaces in style values convert to regular spaces before parsing.
None.
Only affected inputs change behavior. URL-shaped font stacks emit as quoted values, and non-breaking spaces convert to regular spaces. Output for all other styles remains unchanged.
Resolves an issue where the rebuild process did not log all rebuilt entities. The process logs all entities during execution.
Execution of a rebuild through Drush logs all rebuilt entities.
Run a rebuild in verbose mode to access all logged information.
No.
Resolves an issue where the Default value field did not display during form field element edits in Style guide builder.
Users can set default values for Style guide form field elements.
Site Studio import is required to ensure that updated JavaScript assets load.
No.
Resolves an issue where leftover REST resource configurations in the database or config export cause errors after upgrade to version 8.2.7. Database updates remove unused REST resource configurations. If configurations remain in exported files, import operations ignore those specific REST resource configurations.
Database updates remove REST resource configurations from the database.
Run a database update and remove REST resource configurations from config exports.
No.
Resolves an issue where in-place editing targeted incorrect fields or displayed empty values in nested component structures.
In-place editing opens the correct input or WYSIWYG field in nested component structures and retains values during edits.
Clear caches after updates to rebuild nested component templates.
No.
Resolves an issue where tokenized values with HyperText Markup Language (HTML) tags rendered literally instead of executing on templates due to token replacement changes.
Templates render HTML tags in tokenized values correctly. Unsafe tags continue to render literally.
Resave affected templates or run a Site Studio rebuild.
No.
Resolves error log entries generated when rendering Site Studio menu templates mixed with links from other modules, such as Taxonomy Menu or Views.
Applications prevent unnecessary error log entries when rendering mixed menus.
None.
No.