--- title: "Site Studio 8.2.5 - May 13, 2026" date: "2026-05-08T07:38:24+00:00" summary: image: type: "announcement" url: "/drupal-starter-kits/add-ons/site-studio/release/2026-05-13/97626-site-studio-825-may-13-2026" id: "c0da3102-e9c2-4201-9a7e-bac84adb77bf" --- Last updated: 13th May 2026 Released: 13th May 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 ---------- ### Update PHP annotations to PHP attributes #### What is it? When you update PHP annotations to PHP attributes in the codebase, they align with modern PHP standards and make the code easier to read and maintain. The main bulk of these changes is internal, with the exception of `CustomElement`. `CustomElement` uses a PHP attribute to define metadata instead of docblock annotations. You can still use the annotation until support is removed in a future release. Acquia recommends that you update custom elements to use the new PHP attribute syntax to ensure compatibility with future versions of Site Studio. #### What impact will there be? Modern PHP attributes make the code easier to read and maintain. The update provides backward compatibility with existing annotations until support is removed in a future release. #### What actions do I need to take? Ensure that you update custom elements in the codebase to use the PHP attribute syntax to ensure compatibility with future versions of Site Studio. The annotation syntax functions currently, but you must transition to the attribute syntax. #### Are there any risks I should be aware of? None. Bug fixes --------- ### React application dependencies report high severity vulnerabilities #### What is it? This fix addresses an issue where outdated dependencies in the Site Studio React application were reported as high severity vulnerabilities by `npm audit`. #### What impact will there be? The Site Studio React application uses updated dependency versions and patched transitive dependencies. This reduces security risk with no changes to the existing Site Studio UI behavior. #### What actions do I need to take? 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. ### Incompatibility with the [Acquia Web Governance](/web-governance/overview "Overview") module #### What is it? This fix addresses an issue where Site Studio was incompatible with the Acquia Web Governance module. The incompatibility caused JavaScript errors and prevented the Web Governance interface from opening correctly. #### What impact will there be? The Acquia Web Governance scan works correctly on sites with Site Studio installed. Users can access the Web Governance interface without errors. #### What actions do I need to take? None. #### Are there any risks I should be aware of? None. ### Component canvas preview width option applies incorrectly #### What is it? This fix addresses a bug where the component canvas preview width option applied incorrectly. This caused the preview to always render at 100% width regardless of the selected option. #### What impact will there be? The component canvas preview correctly applies the selected width option to allow for more accurate previews of components. #### What actions do I need to take? Clear the Drupal cache. #### Are there any risks I should be aware of? None. ### Pattern repeater item removal leaves empty rows #### What is it? This fix addresses an issue where removal of a pattern repeater item that contains WYSIWYG fields left an empty row instead of removing the item. #### What impact will there be? You can correctly remove pattern repeater items with WYSIWYG components without creating empty rows. #### What actions do I need to take? 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. ### Color Palette SCSS variables render incorrectly ### What is it? This fix addresses an issue where the system did not replace a Color Palette SCSS variable with the correct value. Instead, the generated CSS displayed the variable name. #### What impact will there be? The system correctly replaces Color Palette SCSS variables with corresponding values in the generated CSS. #### What actions do I need to take? Perform a Site Studio rebuild to regenerate stylesheets with the correct variable replacements. #### Are there any risks I should be aware of? None. ### Views exposed filters displayed as blocks clear after a page reload #### What is it? This fix addresses an issue where the values of Views exposed filters displayed as blocks cleared after form submission and page reload. #### What impact will there be? Views exposed filters retain selected values after submission. The reset button also functions correctly. #### What actions do I need to take? No action required. The fix takes effect immediately after the update. #### Are there any risks I should be aware of? None. ### Desktop-first media queries mismatch on element CSS link tags #### What is it? This fix addresses an issue where element breakpoint CSS `` tags had incorrect `media` attribute values in desktop-first mode. The `media` attribute used the width of the breakpoint instead of the previously larger breakpoint width. This caused element styles to load at incorrect viewport widths. #### What impact will there be? Element breakpoint CSS `` tags have the correct media attribute values in desktop-first mode. This ensures that element styles load at the intended viewport widths. #### What actions do I need to take? Save the Website Settings responsive grid configuration to regenerate the stored media queries. #### Are there any risks I should be aware of? None. ### "Hide if no data" legacy settings lost after upgrade #### What is it? This fix addresses an issue where the **Hide if no data** settings token on components was lost. This caused elements to remain visible even when associated fields contained no data. #### What impact will there be? The system correctly migrates components with the legacy **Hide if no data** setting to the new schema. #### What actions do I need to take? Perform a Site Studio rebuild. #### Are there any risks I should be aware of? None. ### Remote media references broke page cacheability #### What is it? This fix addresses an issue where the Dynamic Page Cache did not cache pages that contain remote media references, such as Bynder, in Site Studio layouts. This resulted in slower page load times. #### What impact will there be? The system correctly caches pages with remote media references in Site Studio layouts to improve page performance. #### What actions do I need to take? None. #### Are there any risks I should be aware of? None. ### Tokenized styles do not render on view blocks #### What is it? This fix addresses an issue where tokenized styles from components did not render when used in a view block. #### What impact will there be? Tokenized styles from components used in view templates render correctly on view blocks. #### What actions do I need to take? Perform a Drupal cache rebuild using the following command: `Drush cr`. #### Are there any risks I should be aware of? None.