Last updated: 6th March 2025
Released: 6th March 2025
Known issues¶
- A regression introduced in Drupal core 10.2.5 relating to CKEditor can impact content editing whilst using Site Studio - please apply this patch to maintain data consistency when editing content.
Highlights¶
Component tagging¶
What is it?¶
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.
What impact will there be?¶
Components can now be tagged and drop zones can now be restricted to only accept components with certain tags.
What actions do I need to take?¶
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.
Are there any risks I should be aware of?¶
None.
Workspace Compatibility¶
What is it?¶
Provides compatibility with Drupal's Workspace module, allowing users to take advantage of Workspace functionality within Site Studio projects.
What impact will there be?¶
With workspace compatibility, content entities using layout canvases can now be created, edited, and published within workspace contexts, improving staging and publishing workflows.
What actions do I need to take?¶
None.
Are there any risks I should be aware of?¶
None.
Content Locking (Anti-Concurrent Editing) Compatibility¶
What is it?¶
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.
What impact does this have?¶
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.
What actions do I need to take?¶
To leverage this functionality; version 3.0+ of the Content Lock module must be installed.
Are there any risks I should be aware of?¶
None.
Iframe title for YouTube video embed element¶
What is it?¶
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.
What impact will there be?¶
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.
What actions do I need to take?¶
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.
Are there any risks I should be aware of?¶
None.
Default font stack is indicated when setting font family in the style builder¶
What is it?¶
When setting a font family in the style builder, the default font stack is now indicated in the font family dropdown.
What impact will there be?¶
The default font stack is now indicated in the font family dropdown, making it easier to identify the default font stack.
What actions do I need to take?¶
None.
Are there any risks I should be aware of?¶
None.
Bug fixes¶
Improved Link Handling for Multisite Setups¶
What is it?¶
The Link Element in Site Studio now automatically includes the correct site base path for multisite setups, removing the need for manual adjustments.
What impact will there be?¶
For multisite setups using subdirectories, the correct subdirectory path will be automatically included in link paths, ensuring consistency.
What actions do I need to take?¶
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.
Are there any risks I should be aware of?¶
If you have manually added the subdirectory path in link elements, you will need to remove them to avoid incorrect URLs.
Advanced select field values being stripped when retrieved from a dynamic source¶
What is it?¶
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.
What impact will there be?¶
The advanced select field values will now be rendered as expected.
What actions do I need to take?¶
None.
Are there any risks I should be aware of?¶
None.
Autocomplete typeahead dropdown options not showing special characters correctly¶
What is it?¶
When using the autocomplete typeahead field on elements such as entity reference, special characters were not being displayed correctly in the dropdown options.
What impact will there be?¶
Special characters will now be displayed correctly in the autocomplete typeahead dropdown options.
What actions do I need to take?¶
None.
Are there any risks I should be aware of?¶
None.
Tokenized URL Link converting special characters¶
What is it?¶
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.
What impact will there be?¶
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.
What actions do I need to take?¶
None.
Are there any risks I should be aware of?¶
None.
Drupal core navigation module compatibility¶
What is it?¶
Resolves some layout issues when using the Drupal core navigation module.
What impact will there be?¶
The layout issues will be resolved when using the Drupal core navigation module.
What actions do I need to take?¶
None.
Are there any risks I should be aware of?¶
None.
Steps before upgrading¶
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.
Upgrade¶
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.