Site Studio
Site Studio 7.4.0 - December 06, 2023
Last updated: 6th December 2023
Released: 6th December 2023
When upgrading your website to the latest version of Acquia Site Studio, database updates will be applied and therefore you can't roll back to the previous version of Acquia Site Studio once upgraded.
It is recommended applying updates on your development environment and backing up your website including your database before upgrading Acquia Site Studio.
None.
There is a new separately available submodule for Site Studio called "Site Studio JSON:API". It's available via Github repository https://github.com/acquia/sitestudio_jsonapi and can be installed via composer by running composer require acquia/sitestudio_jsonapi.
Note: This feature is compatible with Drupal 10 only.
Site Studio JSON:API has dependency on JSON:API Extras and it ships pre-configured with Field Enhancer that improves JSON:API output for Site Studio Layout canvas.
More information is available on https://sitestudiodocs.acquia.com/7.4/user-guide/site-studio-jsonapi
It will be possible to read content stored within Site Studio Layout Canvas on Nodes in JSON:API format via the "Site Studio JSON:API" submodule.
If the new submodule is not downloaded and enabled - no changes will occur.
In order to get familiar with updated JSON:API integration, please refer to documentation.
In order to enable updated JSON:API integration:
composer require acquia/sitestudiodrush en sitestudio_jsonapi -ySome known issues with JSON:API integration are listed here
This feature introduces the availability of CSS variables from Site Studio website settings pages. These variables are now accessible for utilization in Custom Elements/Components and Custom Drupal themes.
Detailed instructions can be found at https://sitestudiodocs.acquia.com/7.4/user-guide/css-variables
CSS variables will be included in the Site Studio theme stylesheet.
drush cohesion:rebuild
None.
Nested field repeaters caused a number of issues. CKEditor's initialisation code was behaving incorrectly when the editor instance was inside multiple levels of repeater.
Users can now use WYSIWYG fields inside repeaters inside repeaters.
Site Studio import.
None.
Nested field repeaters caused a number of issues. Dragging and dropping fields within nested repeaters was incorrectly changing the form data and resulting in data being lost or appearing in the incorrect row.
Fields can now be used inside repeaters inside repeaters.
Site Studio Import
There is still an outstanding known issue where using Tab Items and Tab Containers inside a repeater is not working correctly.
Nested field repeaters caused a number of issues. Deleting a row in a field repeater that contained an Entity Browser field would, in some instances, fail and the row would be immediately re-added to the repeater resulting in the user being unable to remove rows.
Entity Browser fields inside repeaters will no longer prevent the row from being deleted.
Site Studio import.
None.
Adds missing schema to the following cohesion.settings config:
cohesion_media_lib_types default value has been update from an integer to a string.
There should no longer be any missing schema for cohesion.settings config. The cohesion_media_lib_types default value has been update from an integer to a string.
Run database updates.
None.
This adds support for Drush 12 and introduces minimum Drush version requirement of 11.6.
You will have to update Drush. This should be handled via composer, as updated version requirement has been added to Site Studio composer.json file.
Update to Drush ^11.6 or Drush 12. If using composer, composer update should be able to handle update, but the results may vary depending on your other third-party dependencies and how Drush is installed on your environment.
Verify if other third-party modules are compatible with Drush ^11.6 or Drush 12.
From version 7.1.0 of Site Studio the media library was loaded within an iframe, which caused multiple issues. We have reverted this change and media library will be loaded in a Drupal modal.
The previous implementation was to resolve "styling" issues with the media library when using the visual page builder. There is a new submodule sitestudio_claro which can be optionally installed to resolve these styling issues in the visual page builder when using the claro admin theme. If a website is using a different admin theme, it's not recommended to use the sitestudio_claro module.
The media library should now function as expected, and there should be no issues using filters. By default, the media library will not look styled when using the visual page builder, unless users install the sitestudio_claro submodule.
Site Studio import & Drupal cache clear, enable the sitestudio_claro submodule if a website is using visual page builder and the claro admin theme. If a website is using a different admin theme, it's not recommended to use the sitestudio_claro module. A similar approach/custom module maybe required to style the media library for other admin themes when using the visual page builder.
None.
Fixes an issue where tokenizing an input to attributes such as ID, in a component and entering no value resulted in empty attribute in the markup.
If a markup field such as ID has been tokenized in a component and no value is entered, then the attribute is not rendered in the DOM.
Site studio rebuild.
None.
Validation, in particular "required", was not running on type ahead (e.g. link to page) fields.
The validation will now run before a form can be applied.
Site Studio import.
None.
Fixed a race condition in which in some browsers on slower computers values entered into one level in the Style Tree could be lost when navigating to a different level.
The issue is resolved.
Site Studio import.
None.
In some rare circumstances it was possible for values entered into the CSS fields on the Style Tab of a component or in the Style Builder to be lost when navigating to a different level in the Style Tree. The issue was especially noticible in some browsers, on slower computers and with forms containing many fields.
Values should no longer be lost.
Site studio import.
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.
Site Studio