Last updated: 1st September 2020
Released: 1st September 2020
There are no known issues with version 6.3.0 of Site Studio.
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:
For more information, see Adding repeatable fields to a component
None.
drush cohesion:import
None.
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
None.
None.
None.
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.
Existing templates will not be affected and continue to work as expected. New templates can have longer names without causing errors.
None.
None.
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.
The error message will display some more useful information to help debug the file causing the error to display.
None.
None.
If a component is used on a custom block layout canvas field, the component will now show as in-use by the custom block.
Allows for components in-use on a custom block to be tracked.
None.
None.
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.
Using the inline edit functionality now loads the correct translation.
None.
None.
Fixed a bug where importing a sync package containing components would not always categorize them correctly.
Importing components should now be categorized correctly.
None.
None.
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()
When previewing an unsaved node containing a layout canvas, you will no longer get this error.
None.
None.
Fixes an issue where attempting to clone a node with a Layout canvas field and component containing a file produced an error.
You can now use the quick clone module to clone nodes with components containing files without error.
None.
None.
Fixes an issue where the focal point module image widget did not load as expected on Drupal image fields.
You can now use the focal image widget on Drupal fields.
None.
None.
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.
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.
If this content did not answer your questions, try searching or contacting our support team for further assistance.