--- title: "Site Studio 8.2.4 - March 16, 2026" date: "2026-03-11T07:23:15+00:00" summary: image: type: "announcement" url: "/drupal-starter-kits/add-ons/site-studio/release/2026-03-16/96476-site-studio-824-march-16-2026" id: "4e8ba5b9-6d2b-499b-98f3-9072d517df84" --- Table of contents will be added Last updated: 16th March 2026 Released: 16th March 2026 Important 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. * [Highlights](#highlights) * [Bug fixes](#bug-fixes) Highlights ---------- ### Video element title attribute support #### What is it? 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. #### What impact will there be? Video elements include the title attribute to provide additional context for Web Content Accessibility Guidelines (WCAG) and Search Engine Optimization (SEO). #### What actions do I need to take? To use this feature, you must add a title to your video elements in the component configuration. #### Are there any risks I should be aware of? None. Bug fixes --------- ### Drupal tokens not replaced in styles within templates #### What is it? 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. #### What impact will there be? Styles in templates correctly replace Drupal tokens with their corresponding values. This ensures that dynamic styling based on tokens functions as intended. #### What actions do I need to take? You must run a Site Studio rebuild or do a new save on affected templates to regenerate styles. #### Are there any risks I should be aware of? None. ### Unintended auto-scroll to default-open Accordion and Tabs items on page load #### What is it? 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. #### What impact will there be? 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. #### What actions do I need to take? A Site Studio import is required to ensure that the system loads the updated JavaScript assets. #### Are there any risks I should be aware of? None. ### Element CSS split by breakpoint order for mobile-first grid #### What is it? 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. #### What impact will there be? Element breakpoint CSS is correctly ordered based on the grid type, and the system saves responsive grid settings against the correct theme. #### What actions do I need to take? Save the Website Settings responsive grid configuration and run a Site Studio rebuild. #### Are there any risks I should be aware of? None. ### Style generation order #### What is it? 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. #### What impact will there be? The system generates styles in the correct order to ensure that CSS rules apply as intended. #### What actions do I need to take? Run a Site Studio rebuild to regenerate stylesheets. #### Are there any risks I should be aware of? None. ### Views pagination after Drupal 11.3 update #### What is it? 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. #### What impact will there be? Views pagination renders correctly in Drupal 10, 11.3, and later versions. #### What actions do I need to take? None. #### Are there any risks I should be aware of? None. ### Page Builder `textarea` fields line breaks on edit #### What is it? This 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. #### What impact will there be? 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. #### What actions do I need to take? A Site Studio import is required to ensure that the system loads the updated JavaScript assets. #### Are there any risks I should be aware of? None. ### Replace removed `views_views_pre_render` function in Drupal 11.3 #### What is it? This 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. #### What impact will there be? The views and infinite scroll integration continues to function correctly in Drupal 11.3 and later versions without reliance on the removed function. #### What actions do I need to take? None. #### Are there any risks I should be aware of? None. ### Page Builder moderation state transitions #### What is it? 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. #### What impact will there be? 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. #### What actions do I need to take? None. The fix applies after you update to this version. #### Are there any risks I should be aware of? None. ### WYSIWYG field repeater performance #### What is it? 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. #### What impact will there be? Users can safely add, remove, and interact with multiple WYSIWYG fields in pattern repeaters without the page becoming unresponsive. #### What actions do I need to take? A Site Studio import is required to ensure that the system loads the updated JavaScript assets. #### Are there any risks I should be aware of? None. ### Auto-scroll to default open accordion item on page load #### What is it? 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. #### What impact will there be? On page load, the system only moves to the accordion if there is a hash in the URL. #### What actions do I need to take? Run a Site Studio import. #### Are there any risks I should be aware of? None. ### Cache metadata pollution from blocks in hidden regions #### What is it? 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. #### What impact will there be? 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. #### What actions do I need to take? None. #### Are there any risks I should be aware of? None.