Last updated: 16th March 2026
Released: 16th March 2026
When you upgrade your website to the latest version of Acquia Site Studio, database updates are applied. This prevents 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.
This update adds support for the HTML title attribute on video elements. If the video element uses an iframe, Acquia Site Studio adds the title to the iframe tag.
Video elements include the title attribute to provide additional context for Web Content Accessibility Guidelines (WCAG) and Search Engine Optimization (SEO).
To use this feature, you must add a title to your video elements in the component configuration.
None.
This fix addresses an issue where Drupal tokens were not replaced in styles in templates. This issue caused tokens to output as literal text instead of their corresponding values.
Styles in templates correctly replace Drupal tokens with their corresponding values. This ensures that dynamic styling based on tokens functions as intended.
You must run a Site Studio rebuild or do a new save on affected templates to regenerate styles.
None.
This fix addresses an issue where the browser automatically moved to default-open accordion or tab items on page load even when no URL hash was present. This occurred after a user enabled the Scroll to open toggle in Accordion or Tabs Container components. Additionally, tabs mode had issues where page reload with a hash did not scroll correctly, and external links to tab items did not scroll on the first click.
Accordion and Tabs Container components function correctly:
No auto-scroll on page load when the URL has no hash.
Proper scroll behavior when a hash matches a specific accordion or tab item.
Tabs mode scrolls correctly on page reload with a hash.
External links to tabs work on the first click.
Multiple accordion or tab containers on the same page work independently.
A Site Studio import is required to ensure that the system loads the updated JavaScript assets.
None.
This fix addresses an issue where element breakpoint CSS files were not ordered correctly when the grid was set to mobile-first. This caused an incorrect CSS cascade and broken styling for elements such as accordions and tabs.
Element breakpoint CSS is correctly ordered based on the grid type, and the system saves responsive grid settings against the correct theme.
Save the Website Settings responsive grid configuration and run a Site Studio rebuild.
None.
This fix addresses an issue where the system did not always generate styles in the correct order, which led to unexpected styling results on the front end.
The system generates styles in the correct order to ensure that CSS rules apply as intended.
Run a Site Studio rebuild to regenerate stylesheets.
None.
This fix addresses an issue where views templated in Site Studio that use pagination failed to render after an update to Drupal 11.3 because of updates in pager preprocessing.
Views pagination renders correctly in Drupal 10, 11.3, and later versions.
None.
None.
textarea fields line breaks on editThis fix addresses an issue where textarea fields in Page Builder components lost line breaks after a user used the Apply or Cancel buttons in edit-in-place mode. Text content with newlines either collapsed into a single line or disappeared.
Users can edit textarea fields in Page Builder without loss of line breaks. The system preserves content with multiple lines after a user selects Apply or Cancel during inline editing.
A Site Studio import is required to ensure that the system loads the updated JavaScript assets.
None.
views_views_pre_render function in Drupal 11.3This update replaces the views_views_pre_render function that was deprecated and removed in Drupal 11.3. The system previously used this function in the views and infinite scroll integration.
The views and infinite scroll integration continues to function correctly in Drupal 11.3 and later versions without reliance on the removed function.
None.
None.
This fix addresses an issue where Page Builder loaded the default Published revision instead of the latest Draft revision. This caused errors after a user attempted to transition moderation states from Draft to other states in Page Builder.
Users can successfully change moderation states such as Draft to In Review to Published directly from Page Builder without permission errors. The moderation state widget correctly reflects the current state of the content.
None. The fix applies after you update to this version.
None.
This fix addresses an issue where the page became unresponsive after a user removed a What You See Is What You Get (WYSIWYG) field from a pattern repeater after selection of the About text formats link.
Users can safely add, remove, and interact with multiple WYSIWYG fields in pattern repeaters without the page becoming unresponsive.
A Site Studio import is required to ensure that the system loads the updated JavaScript assets.
None.
This fix addresses an issue where accordions set to scroll to on open and create # url moved to the accordion on page load even if there was no hash in the URL.
On page load, the system only moves to the accordion if there is a hash in the URL.
Run a Site Studio import.
None.
This fix addresses an issue where blocks in Site Studio hidden regions applied their cache metadata to pages even after the system denied access. It also addresses an issue where the hasDrupalPermission() Twig function always returned TRUE for single permission strings without a check of user permissions.
Pages with inaccessible blocks now cache correctly. The system applies only the cache metadata of the access result when blocks do not render, which prevents cache pollution and maintains proper cache invalidation.
None.
None.