Last updated: 6th March 2025
Released: 6th March 2025
Site builders can now create tags which can be applied to components & custom components.
Drop zones can then be restricted to only accept certain tags. This allows for greater control of which components can be nested in drop zones.
Components can now be tagged and drop zones can now be restricted to only accept components with certain tags.
To take advantage of this feature, tags will need to be created and applied to components.
Drop zones of components will also need to be restricted to accept specific tags where required.
None.
Provides compatibility with Drupal's Workspace module, allowing users to take advantage of Workspace functionality within Site Studio projects.
With workspace compatibility, content entities using layout canvases can now be created, edited, and published within workspace contexts, improving staging and publishing workflows.
None.
None.
The Visual Page Builder is now compatible with the Content Lock module (version 3.0 onwards), preventing multiple users from editing the same page simultaneously.
Restricts simultaneous editing of the same page in Page Builder by enabling content locking. It also supports the option to break the lock if needed.
To leverage this functionality; version 3.0+ of the Content Lock module must be installed.
None.
A new video iFrame title field has been added to YouTube embed element. This allows users to add a `title` attribute to iframe element when using the YouTube embed element.
The YouTube embed element now includes a video iFrame title field to add a `title` attribute for the iframe.
This improves accessibility by providing descriptive titles for screen readers and enhances SEO.
If you want to add a title attribute to the iframe, you need to enter a title inside the Video iFrame Title field in the YouTube embed element settings.
None.
When setting a font family in the style builder, the default font stack is now indicated in the font family dropdown.
The default font stack is now indicated in the font family dropdown, making it easier to identify the default font stack.
None.
None.
The Link Element in Site Studio now automatically includes the correct site base path for multisite setups, removing the need for manual adjustments.
For multisite setups using subdirectories, the correct subdirectory path will be automatically included in link paths, ensuring consistency.
If you use a subdirectory-based multisite setup, rebuild your site to apply these changes. This will ensure that the subdirectory path is automatically added to all Link Element fields. Alternatively, you can resave the relevant components to apply the update.
If you have manually added the subdirectory path in link elements, you will need to remove them to avoid incorrect URLs.
In Site Studio 7.5 advanced select field capabilities were introduced to provide dynamic sources for select values. However, if the values were not stored with the component they were being stripped at the point of render.
The advanced select field values will now be rendered as expected.
None.
None.
When using the autocomplete typeahead field on elements such as entity reference, special characters were not being displayed correctly in the dropdown options.
Special characters will now be displayed correctly in the autocomplete typeahead dropdown options.
None.
None.
This fix resolves an issue where a URL field from a content type, used in Site Studio Content Template Link Elements as a tokenized value, would incorrectly encode special characters such as & to & in the rendered link.
Links in Site Studio templates that previously displayed incorrectly due to encoding issues will now render correctly. There are no breaking changes or regressions introduced.
None.
None.
Resolves some layout issues when using the Drupal core navigation module.
The layout issues will be resolved when using the Drupal core navigation module.
None.
None.
As with any version of Acquia Site Studio, we recommend that you backup your websites database and code before upgrading the version of Acquia Site Studio. There are no other specific steps to carry out before upgrading to this version.
It is recommended that you backup and upgrade your website on a development environment before applying to a production website. You can upgrade your version of Acquia Site Studio by following our upgrade guide.
If this content did not answer your questions, try searching or contacting our support team for further assistance.