Site Studio
Site Studio 8.2.6 - July 07, 2026
Last updated: 7th July 2026
Released: 7th July 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.
Before a rebuild through Drush begins, the system verifies that API keys exist. This process prevents a rebuild from running without the necessary API keys and eliminates potential rebuild errors.
API keys are checked when running a rebuild via Drush. If the API keys are absent, the rebuild does not proceed, and an error message displays.
None.
None.
The new Drupal token [media-entity-reference:media-alt] is available to fetch the alt text of media entities selected in Image and Picture elements in components.
This token enables site developers to use the existing media alt text instead of entering alt text manually for an Image element when using media entities in Image and Picture elements. This feature saves time and ensures that the alt text matches the media entity alt text, which improves accessibility and SEO.
Navigate to a component that uses an Image or Picture element.
Enter the token [media-entity-reference:media-alt] in the alt text field to fetch the alt text from the media entity selected in the Image or Picture element.
No action is required if a website uses the entity reference or browser elements to select media.
None.
The system adds WAI-ARIA Tabs pattern role and state attributes on accordion tab elements in tabs mode to improve accessibility. This update includes the role="tablist", role="presentation", role="tab", role="tabpanel", aria-selected, aria-controls, and aria-labelledby attributes. The system removes all tab-specific ARIA attributes when the component switches to accordion mode.
The addition of ARIA role and state attributes enhances the accessibility of accordion tabs for users who rely on assistive technologies such as screen readers. This addition provides better context, state information, and navigation cues for users who interact with tab components.
Run a Site Studio import.
None.
A new system setting enables users to globally set the Link element to link directly to media files instead of the media entity. When a user selects a media item in the Link element, the system links directly to the file associated with that media item rather than the media entity.
This change enables users to link easily to referenced media files where a Link element is used.
Navigate to the system settings if you want to enable this behavior.
Toggle on Link to media file to ensure that all Link elements that reference media entities link directly to media files instead of the media entities.
None. This is a global setting that you can toggle on or off based on requirements.
Users can set the trigger HTML element for accordion items to use a <button> or <a> element.
Using a <button> element for accordion triggers improves accessibility by providing better semantics and built-in keyboard support. The default trigger element remains an <a> tag to maintain backward compatibility and styling.
Run a Site Studio import.
Update accordion items to use the new button trigger option to take advantage of improved accessibility.
Configure this option in the Accordion tabs item element under Accordion settings > Trigger HTML element.
The new button trigger option is optional. If you update an existing accordion item from an <a> tag to a <button> element, the trigger styles must be adjusted.
Performance improvements reduce redundant processing when rendering pages that contain multiple Site Studio components. The system caches and reuses component style calculations and template lookups in a single page request.
Pages that contain many Site Studio components render faster, particularly pages with repeated use of the same components or custom styles. Sites with complex layouts show noticeable improvements in page load times.
No action is required. The performance improvements apply automatically.
None.
The column-count CSS property was not applied as expected, which caused layout issues when using multi-column layouts.
This fix ensures that the system applies the column-count property correctly to enable proper multi-column layouts.
Run a Site Studio rebuild.
None.
Token replacement values were incorrectly encoded in templates, which caused UI HTML entities to display instead of the intended characters.
This issue affected content that uses tokens, such as links or dynamic text, where the replacement value contains special characters. The values displayed as HTML entities, such as & instead of &, which caused confusion and incorrect content display.
Resave affected template entities or run a rebuild.
None.
A bug is resolved where multiple custom components in a module shared the same template filename, which caused the system to use the wrong template.
This fix ensures that each custom component uses its own template correctly, even if multiple components share the same template filename.
Run a cache clear.
None.
A bug is resolved where modifier classes were not applied correctly in certain cases, which caused styling issues.
This fix ensures that the system applies modifier classes correctly, which resolves styling issues related to missing classes.
Run a Site Studio rebuild.
None.
An issue is resolved where an SQL error occurred when the content access module was installed and a user attempted to view layout canvas content.
The SQL error no longer occurs when the content access module is installed.
None.
None.
A bug is resolved where font libraries that contain fonts with numbers in their names, such as Avenir LT Std 55 Roman, failed during a rebuild operation.
Font libraries that failed to rebuild due to font naming issues rebuild successfully.
No action is required. Previously affected font libraries can be rebuilt.
None.
A bug is resolved where pseudo selectors, such as :nth-child(), :hover, and :focus, were stripped when used multiple times in a complex CSS selector chain.
Styles that use pseudo selectors in complex selectors are generated correctly, which ensures that the expected styling applies.
Run a Site Studio rebuild.
None.
Site Studio