Version 6.4.0 release details

Last updated: 25th November 2020
Released: 25th November 2020

When upgrading your website to the latest version of Site Studio, database updates will be applied and therefore you can't roll back to the previous version once upgraded.

It is recommended applying updates on your development environment and backing up your website including your database before upgrading Site Studio.

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

Known issues

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

Highlights

Provide an override for rebuild batch limit

What is it?

By default the rebuild process will handle 10 items at a time to reduce the memory required to run this operation. This feature exposes a method for increasing that number via Drupal settings.

What impact will there be?

Where more memory is available the rebuild_max_entity can be set to a number greater than 10 to process the rebuild faster.

What actions do I need to take?

Add a settings value such as:

$settings['rebuild_max_entity'] = 20;

Are there any risks I should be aware of?

Increasing the rebuild_max_entity value will require more memory to process each rebuild batch.

Style builder - field tokenization

What is it?

The ability to expose style properties as component form options.

What impact will there be?

The following style properties are no longer flagged and can now be tokenized:

• Text shadow > Horizontal
• Text shadow > Vertical
• Text shadow > Blur
• Text shadow > Color
• Position > Position
• Display > Display
• Box shadow > Horizontal
• Box shadow > Vertical
• Box shadow > Blur
• Box shadow > Spread
• Box shadow > Color
• Transition > Duration
• Transition > Delay

What actions do I need to take?

Create component fields that are connected to relevant style properties in your layout canvas elements, which will enable configurable styles in your component forms.

Are there any risks I should be aware of?

text-shadow and box-shadow are both shorthand properties and support multiple values.

This means values for all fields should be entered, to ensure styles are built correctly. You can do this in a number of ways:

1. Make all relevant component fields required.
2. Use component fields that provide set options that can't be cleared (eg Range and Select).
3. Hardcode values for style properties that have a fixed value and don't need to be configurable in your component form.

Button element - layout canvas child support

What is it?

You can now add child elements to the Button element.

What impact will there be?

It will enable more advanced button styles, such as:

• Animated menu buttons
• Buttons that look like on/off toggle switches

What actions do I need to take?

To update existing link elements, you will need to do a rebuild.

Both new and existing Button elements on the layout canvas will be collapsed by default.

Are there any risks I should be aware of?

None.

Component content with Dropzones

What is it?

Adds the ability to save Component content with a Dropzone.

What impact will there be?

This will expose the Layout canvas when editing a Component content. Editors will not be able to edit / add to the top level Layout canvas only the Dropzone.

What actions do I need to take?

drush cohesion:import

Are there any risks I should be aware of?

None.

Component content can be created directly

What is it?

Component content can now be created directly through the Site Studio menu Site Studio > Components > Component content > Add component content rather than having to save a component from a node.

What impact will there be?

Component content doesn't have to be created from a node and can now be created separately just like you would with other content entities. The ability to create a component content from a node is still available

What actions do I need to take?

None.

Are there any risks I should be aware of?

None.

Two Google Map API keys can be defined to follow Google's best practices

What is it?

Two Google Map API keys can now be defined through the Site studio UI. One for the Google Maps Javascript API which is used for rendering maps and previews, another for the Geocoding API which is used to fetch the coordinates.

What impact will there be?

This allows for restrictions to be applied to API keys as explained by in Google's best practice document: https://developers.google.com/maps/api-key-best-practices#best_practice_list.
If a second API key for the Geocoding is not defined, it will continue to use the first one.

What actions do I need to take?

None.

Are there any risks I should be aware of?

None.

Entity browser element can be used for content entities

What is it?

The Entity browser element now has the ability for more entity types to be used with the element. This allows more flexibility for site builders to create their own Entity browsers for other entities, and for contributed modules, such as content browser to be used with the Entity browser element.

Note that when using the contributed module content browser, the browser modal uses the active front-end theme for styling.

What impact will there be?

The ability for the content entities to be selected within the Entity browser element.

What actions do I need to take?

None.

Are there any risks I should be aware of?

None.

Bug fixes

There are no bug fixes in this release.

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.