Last updated: 9th October 2023
Released: 9th October 2023

• Known Issues
• Bug Fixes
• Steps before upgrading

Known issues¶

None.

Bug fixes¶

Some fields in components will load the default value back in after the user has cleared them¶

What is it?¶

This fixes an issue where on certain fields (image browser, typeahead, select, colour picker) the default value will load when the sidebar is opened if the user has previously removed the value.

What impact will there be?¶

Default values will only load in if the user has not edited the field.

What actions do I need to take?¶

Site Studio import.

Are there any risks I should be aware of?¶

None.

Keyboard shortcuts executing when using Sidebar Editor.¶

What is it?¶

This fixes an issue where you could envoke a keyboard shortcut when editing content via the Sidebar Editor.

What impact will there be?¶

You can no longer use the layout canvas node shortcuts when using the sidebar editor.

What actions do I need to take?¶

Site Studio import.

Are there any risks I should be aware of?¶

None.

Accordion/Tabs Element Start State option not working correctly¶

What is it?¶

Accordion/Tabs Elements configured to show in Accordion mode and set to have the Start State of "All Closed" were not loading with all the sections closed as they should.

What impact will there be?¶

Accordions will now behave correctly as per the user settings

What actions do I need to take?¶

Site Studio import.

Are there any risks I should be aware of?¶

None.

Font files not found when using Youtube video background Element¶

What is it?¶

When using the Youtube video background Element several font files were requested by the browser, but not found.

What impact will there be?¶

The font files will no longer be requested by the browser.

What actions do I need to take?¶

Site Studio import.

Are there any risks I should be aware of?¶

None.

Color palette field showing both tabs¶

What is it?¶

Fixes a problem with the color palette field where both tabs would appear on top of each other.

What impact will there be?¶

The tabs will work as expected, and only show one at a time.

What actions do I need to take?¶

Site Studio import.

Are there any risks I should be aware of?¶

None.

Entity browser preview not displaying for non-media or file entities¶

What is it?¶

When using an Entity browser field to select an entity that was not media or a file entity no preview was shown to indicate that the entity browser had a selection.

A 500 error would also appear in the browsers network tab.

What impact will there be?¶

When selecting non-media or file entities in the Entity browser field the preview will now show the entities title. This indicates to the user that a selection has been made on the entity browser field.

What actions do I need to take?¶

Cache clear.

Are there any risks I should be aware of?¶

None.

Syntax error occurring with _0042EntityUpdate¶

What is it?¶

When running a rebuild users would get the following error:

Unable to decode output into JSON: Syntax error TypeError: Drupal\cohesion\Plugin\EntityUpdate_0042EntityUpdate::updateFormElement(): Argument #1 ($model) must be of type Drupal\cohesion\LayoutCanvas\ElementModel, null given

What impact will there be?¶

Running a rebuild users should no longer get this error.

What actions do I need to take?¶

Cache clear & rebuild.

Are there any risks I should be aware of?¶

None.

Entity browser with Typeahead not showing selected entity¶

What is it?¶

Fixes an issue where if using a Typeahead with the entity browser, no content entity was rendered.

What impact will there be?¶

It will now show your selected entity

What actions do I need to take?¶

Import, Cache clear & rebuild.

Are there any risks I should be aware of?¶

None.

When setting database transaction isolation level to READ-COMMITTED a warning is displayed¶

What is it?¶

Drupal provides a mechanism for setting database transaction isolation level (see: https://www.drupal.org/node/3264101). This requires all tables to have a primary key which is introduced with this fix.

An additional index of source_uuid is also added to optimise database queries.

What impact will there be?¶

Warning messages will no longer display when setting database isolation level to READ-COMMITTED.

What actions do I need to take?¶

Run database updates.

Are there any risks I should be aware of?¶

None.

Error: Call to undefined function component_contents_mass_update()¶

What is it?¶

Fixes a bug when canceling a users account that had component content associated with it, users would receive a Drupal white screen "This website encountered an error" and the following error in the Drupal logs: Error: Call to undefined function component_contents_mass_update() in cohesion_elements_user_cancel() (line 651 of /app/web/modules/contrib/cohesion-dev/modules/cohesion_elements/cohesion_elements.module)

What impact will there be?¶

When canceling a users account in this scenario the user will no longer get this error the action will successfully complete.

What actions do I need to take?¶

Cache clear.

Are there any risks I should be aware of?¶

None.

Content moderation, translation & revision issues¶

What is it?¶

Using Site Studio with content moderation and translations enabled can lead to unexpected behaviour whereby translated content and moderation states can impact upon each other.

What impact will there be?¶

Issues relating to translations and content moderation are resolved.

What actions do I need to take?¶

None.

Are there any risks I should be aware of?¶

None.

Improving package refresh endpoint performance¶

What is it?¶

Editing, viewing or building a complex package could result in poor performance when loading or refreshing package contents due to slow response from /admin/cohesion/sync/refresh endpoint in Drupal. This has been improved and editing, viewing or building complex packages should not result in timeout errors.

What impact will there be?¶

Faster loading and building packages, no timeout errors.

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.