Last updated: 13th May 2026
Released: 13th May 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.
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.
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.
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.
This fix addresses an issue where outdated dependencies in the Site Studio React application were reported as high severity vulnerabilities by npm audit.
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.
Site Studio import is required to ensure that the system loads the updated JavaScript assets.
None.
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.
The Acquia Web Governance scan works correctly on sites with Site Studio installed. Users can access the Web Governance interface without errors.
None.
None.
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.
The component canvas preview correctly applies the selected width option to allow for more accurate previews of components.
Clear the Drupal cache.
None.
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.
You can correctly remove pattern repeater items with WYSIWYG components without creating empty rows.
Site Studio import is required to ensure that the system loads the updated JavaScript assets.
None.
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.
The system correctly replaces Color Palette SCSS variables with corresponding values in the generated CSS.
Perform a Site Studio rebuild to regenerate stylesheets with the correct variable replacements.
None.
This fix addresses an issue where the values of Views exposed filters displayed as blocks cleared after form submission and page reload.
Views exposed filters retain selected values after submission. The reset button also functions correctly.
No action required. The fix takes effect immediately after the update.
None.
This fix addresses an issue where element breakpoint CSS <link> 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.
Element breakpoint CSS <link> tags have the correct media attribute values in desktop-first mode. This ensures that element styles load at the intended viewport widths.
Save the Website Settings responsive grid configuration to regenerate the stored media queries.
None.
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.
The system correctly migrates components with the legacy Hide if no data setting to the new schema.
Perform a Site Studio rebuild.
None.
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.
The system correctly caches pages with remote media references in Site Studio layouts to improve page performance.
None.
None.
This fix addresses an issue where tokenized styles from components did not render when used in a view block.
Tokenized styles from components used in view templates render correctly on view blocks.
Perform a Drupal cache rebuild using the following command: Drush cr.
None.