Version 6.5.0 release details

Last updated: 17th June 2021
Released: 23rd March 2021

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

• Attempting to add components to the Visual page builder can result in a Javascript error.
  If you encounter this error, please upgrade to 6.5.1.

Highlights

Site Studio Visual Page Builder Module

What is it?

A new module available as part of Site Studio that provides a front-end page building and content authoring experience using Site Studio drag and drop components. The visual page builder is a companion to the layout canvas that is used in the back-end Drupal user interface.

Find out more about the visual page builder

What impact will there be?

When installed, the module will add a new ‘Page builder’ button to pages that have a Site Studio layout canvas. When the button is clicked, users enter the new page builder mode.

What actions do I need to take?

To use the Page Builder you will need to install the Visual Page Builder module.

Are there any risks I should be aware of?

There are no known risks.

Provide an override for sync:import batch limit

What is it?

By default the sync:import 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 sync_max_entity can be set to a number greater than 10 to process the import faster.

What actions do I need to take?

Add a settings value such as:

$settings['sync_max_entity'] = 20;

Are there any risks I should be aware of?

Increasing the sync_max_entity value will require more memory to process each sync:import batch.

Link elements - support for rel attribute

What is it?

The rel attribute defines the relationship between a linked resource and the current document. Support has been added for three of the most important values:

• nofollow - prevents backlink endorsement, so that search engines don't pass page rank to the linked resource.
• noopener - prevents linked resource getting partial access to linking page, something that is otherwise exploitable by malicious websites.
• noreferrer - similar to noopener (especially for older browsers), but also prevents the browser sending the referring webpage's address.

What impact will there be?

For each of the following Site Studio elements:

• Link
• Container
• Slide item
• Column

Checkbox toggles for No follow, No opener and No referrer will appear when the following conditions are met:

• Link Type is set to URL
• Link Target is set to New window

When checked, they will be added to the created link HTML in the format rel="nofollow noopener noreferrer" (if all are enabled).

What actions do I need to take?

Existing components that you would like to use this feature on need to be updated, as these toggles are OFF by default.

Are there any risks I should be aware of?

• Use of the No follow toggle will have an impact on SEO, given that it stops search engines passing page rank endorsement to the linked resource. This is often used in blog comments or forums, as these can be a source of spam or low-quality links. Google and other search engines require nofollow to be added to sponsored links and advertisements.

• Use of the No referrer toggle will affect analytics, as it will report traffic as direct instead of referred.

Menu templates - support for Drupal <nolink> token

What is it?

When creating Drupal menus, it's possible to use a <nolink> token to render the link text only, which outputs as a span instead of an a tag.

This can be useful for creating headings for menu sub-levels.

What impact will there be?

Previously Site Studio menu templates would ignore the <nolink> token and still render an a tag with an empty href attribute.

Now as per Drupal behaviour, these are rendered as span tags.

If a different HTML element has been specified in the Site Studio menu template (Menu link settings), this setting will take priority.

This is recommended if you are using <nolink> for creating menu sub-level headings.

What actions do I need to take?

1. Update your Drupal menu with the <nolink> token where needed.
2. Re-save the relevant Site Studio menu template, or run a site rebuild. Both of these actions will refresh the menu template code.

Are there any risks I should be aware of?

You many need to create additional menu template styles to account for the tag change from a to span, depending on how current styles are being applied.

Accordion accessibility enhancements

What is it?

The accessibility of Accordion tabs elements has been improved, when in the accordion display mode.

What impact will there be?

• Accordion header links now have the aria-expanded attribute, which toggles between true and false when expanded and collapsed, respectively.

• Accordion header links now have aria-disabled="true" set if the parent Accordion tabs container has the Collapsible setting toggled OFF. This is only applied when the item is expanded, to indicate to a screen reader that the panel cannot be collapsed manually.

  When the panel is collapsed because a sibling accordion item is expanded, the aria-disabled attribute is removed.

• Accordion header links now have aria-disabled="true" permanently set if the accordion item has been disabled through Navigation link settings.

Option to add font-display on Font libraries settings page

What is it?

Adds the ability to set the font-display CSS property when uploading a new web font. For more information about font-display, see https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face/font-display

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.

Bug fixes

Sync package entity dependencies not being removed if no longer used on the entity

What is it?

Fixes a bug where a sync package contains entities that then have their dependencies updated, but the sync package contained both the original and new dependency. For example your component exists in a package, you then update that components default image, both images files were included in the sync package rather than the latest one.

What impact will there be?

Old entity dependencies should no longer appear in your sync package. Sync package files may also be smaller in size if there were multiple "old" dependencies.

What actions do I need to take?

You may need to re-save your sync package.

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.