Last updated: 6th December 2023
Released: 6th December 2023

• Known Issues
• Highlights
• Bug Fixes
• Steps before upgrading

Known issues¶

None.

Highlights¶

JSON:API support¶

What is it?¶

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

What impact will there be?¶

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.

What actions do I need to take?¶

In order to get familiar with updated JSON:API integration, please refer to documentation.

In order to enable updated JSON:API integration:

1. Download "Site Studio JSON:API" submodule: composer require acquia/sitestudio
2. Enable "Site Studio JSON:API" submodule: drush en sitestudio_jsonapi -y

Are there any risks I should be aware of?¶

Some known issues with JSON:API integration are listed here

CSS Variables¶

What is it?¶

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

What impact will there be?¶

CSS variables will be included in the Site Studio theme stylesheet.

What actions do I need to take?¶

drush cohesion:rebuild

Are there any risks I should be aware of?¶

None.

Bug fixes¶

Fixed regression where CKEditor did not work inside a field repeater inside another field repeater¶

What is it?¶

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.

What impact will there be?¶

Users can now use WYSIWYG fields inside repeaters inside repeaters.

What actions do I need to take?¶

Site Studio import.

Are there any risks I should be aware of?¶

None.

Fixed data corrucption when using nested field repeaters¶

What is it?¶

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.

What impact will there be?¶

Fields can now be used inside repeaters inside repeaters.

What actions do I need to take?¶

Site Studio Import

Are there any risks I should be aware of?¶

There is still an outstanding known issue where using Tab Items and Tab Containers inside a repeater is not working correctly.

Fixed issue with deleting a row containing an Entity Browser element from a field repeater¶

What is it?¶

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.

What impact will there be?¶

Entity Browser fields inside repeaters will no longer prevent the row from being deleted.

What actions do I need to take?¶

Site Studio import.

Are there any risks I should be aware of?¶

None.

Updates to various cohesion.settings config schema¶

What is it?¶

Adds missing schema to the following cohesion.settings config:

• cohesion_sync.cohesion_sync_package.
• image_browser.content.dx8_imce_stream_wrapper
• image_browser.content.cohesion_media_lib_types
• image_browser.config.cohesion_media_lib_types

cohesion_media_lib_types default value has been update from an integer to a string.

What impact will there be?¶

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.

What actions do I need to take?¶

Run database updates.

Are there any risks I should be aware of?¶

None.

Support for Drush 12.¶

What is it?¶

This adds support for Drush 12 and introduces minimum Drush version requirement of 11.6.

What impact will there be?¶

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.

What actions do I need to take?¶

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.

Are there any risks I should be aware of?¶

Verify if other third-party modules are compatible with Drush ^11.6 or Drush 12.

Media library filter issues¶

What is it?¶

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.

What impact will there be?¶

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.

What actions do I need to take?¶

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.

Are there any risks I should be aware of?¶

None.

Tokenizing an input to attributes such as ID, in a component with no value resulted in empty attribute¶

What is it?¶

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.

What impact will there be?¶

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.

What actions do I need to take?¶

Site studio rebuild.

Are there any risks I should be aware of?¶

None.

Fix for type ahead validation not working¶

What is it?¶

Validation, in particular "required", was not running on type ahead (e.g. link to page) fields.

What impact will there be?¶

The validation will now run before a form can be applied.

What actions do I need to take?¶

Site Studio import.

Are there any risks I should be aware of?¶

None.

Fix instance where certain browser/computer speed configurations could result in data loss in the Style Tree¶

What is it?¶

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.

What impact will there be?¶

The issue is resolved.

What actions do I need to take?¶

Site Studio import.

Are there any risks I should be aware of?¶

None.

Fix for issue where fields in the Style Builder could lose values when navigating the Style Tree.¶

What is it?¶

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.

What impact will there be?¶

Values should no longer be lost.

What actions do I need to take?¶

Site studio import.

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.