Last updated: 1st September 2020
Released: 1st September 2020

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

Known issues¶

There are no known issues with version 6.3.0 of Site Studio.

Highlights¶

Feature: Component field repeater¶

What is it?¶

Components can now include repeating sets of fields within the component form. A new form element called a Field repeater allows the form builder to wrap one or multiple fields within a repeatable group. The field repeater includes a button which allows the content author to add another group of fields as an array. The field repeater can be limited to a maximum number of repeats.

The Field repeater form element is used with another new component layout element called a Pattern repeater. This allows a section of layout on the layout canvas to be repeated. When linked together, the Field repeater will repeat the layout within the Pattern repeater. The result is a component that can include a repeating set of fields that repeats a corresponding layout.

There are many use cases for this functionality. Some examples include:

• A gallery component where the content author can add multiple images to a single component.
• A map component where the content author can add multiple map pins to a single component.
• A slider where the content author can add multiple slides to a single component.
• A list where the content author can add multiple list items to a single component.
• A table where the content author can add multiple rows to the table.

For more information, see Adding repeatable fields to a component

What impact will there be?¶

None.

What actions do I need to take?¶

drush cohesion:import

Are there any risks I should be aware of?¶

None.

TMGMT compatible¶

What is it?¶

You can now use Site Studio with TMGMT to translate text based content within your components on the Layout canvas. By default, all text based fields in your components will be translatable. You can choose to exclude fields from being translatable in a new section on the component form page named Translation settings. This only shows if the TMGMT module is installed and configured.

Translation suggestions have also been implemented so that TMGMT will display component content and other referenced content entities as suggested content to translate.

For more information, see Translations using TMGMT

What impact will there be?¶

None.

What actions do I need to take?¶

None.

Are there any risks I should be aware of?¶

None.

Update to content template machine name prefix¶

What is it?¶

The content template machine name prefix has been shortened to ctn_tpl when creating additional full content templates. Previously, if your content bundle had a long name it could take the machine name over the 32 character limit enforced by Drupal core. The new shorter prefix provides more scope for longer names.

What impact will there be?¶

Existing templates will not be affected and continue to work as expected. New templates can have longer names without causing errors.

What actions do I need to take?¶

None.

Are there any risks I should be aware of?¶

None.

File Sync error message updated¶

What is it?¶

When importing a file through Site Studio Sync where the UUID already exists, but the URI doesn't match an error message is displayed. The error message now displays more information to help debug which file is causing the error.

What impact will there be?¶

The error message will display some more useful information to help debug the file causing the error to display.

What actions do I need to take?¶

None.

Are there any risks I should be aware of?¶

None.

Custom block usage plugin¶

What is it?¶

If a component is used on a custom block layout canvas field, the component will now show as in-use by the custom block.

What impact will there be?¶

Allows for components in-use on a custom block to be tracked.

What actions do I need to take?¶

None.

Are there any risks I should be aware of?¶

None.

Bug fixes¶

Using inline editing to edit components loaded the incorrect translation¶

What is it?¶

Fixes a bug where on a multilingual site where using the inline edit functionality to edit components on the frontend of a website was loading the incorrect translation.

What impact will there be?¶

Using the inline edit functionality now loads the correct translation.

What actions do I need to take?¶

None.

Are there any risks I should be aware of?¶

None.

Components not always being correctly categorized¶

What is it?¶

Fixed a bug where importing a sync package containing components would not always categorize them correctly.

What impact will there be?¶

Importing components should now be categorized correctly.

What actions do I need to take?¶

None.

Are there any risks I should be aware of?¶

None.

Using Drupal preview on a node that has not yet been saved produces an error¶

What is it?¶

Fixes a bug where previewing an unsaved node containing components on a layout canvas caused the below error.

Symfony\Component\Routing\Exception\InvalidParameterException: Parameter "revision_id" for route "cohesion_elements.components.settings_tray_iframe" must match "[^/]++" ("" given) to generate a corresponding URL. in Drupal\Core\Routing\UrlGenerator->doGenerate()

What impact will there be?¶

When previewing an unsaved node containing a layout canvas, you will no longer get this error.

What actions do I need to take?¶

None.

Are there any risks I should be aware of?¶

None.

Error when cloning a node using quick clone module¶

What is it?¶

Fixes an issue where attempting to clone a node with a Layout canvas field and component containing a file produced an error.

What impact will there be?¶

You can now use the quick clone module to clone nodes with components containing files without error.

What actions do I need to take?¶

None.

Are there any risks I should be aware of?¶

None.

Support for focal point module¶

What is it?¶

Fixes an issue where the focal point module image widget did not load as expected on Drupal image fields.

What impact will there be?¶

You can now use the focal image widget on Drupal fields.

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 Site Studio, we recommend that you backup your websites database and code before upgrading the version of 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 Site Studio by following our upgrade guide.