Version 6.9.0 release details
Last updated: 7th June 2022
Released: 23rd June 2022
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
There are no known issues with version 6.9.0 of Site Studio.
Highlights
Custom components
What is it?
Adds a new feature to Site studio where developers can create their own components by coding them with Javascript/HTML/CSS or Twig/Javascript/CSS. Refer to the user guide for more detailed documentation on how to create and use custom components.
Custom component examples can be found in a submodule (example_custom_component). This module is intended for demonstration purposes only and should not be enabled on production.
What impact will there be?
Developers will be able to extend Site studio capabilities by defining their own custom components. This will enable Site Studio to have functionality that previously could not be built with Site Studio elements.
Javascript developers with limited knowledge of Drupal will be able to add custom component to Site Studio without the need for a Drupal developer. A Drupal developer will only be required for creating a module and file structure. Refer to the user guide for more information.
What actions do I need to take?
None.
Are there any risks I should be aware of?
None.
Package multi-import command for Drush
What is it?
A new drush command that takes package list file as an argument and imports multiple packages at once with a combined rebuild process based on imported changes.
What impact will there be?
This will allow specifying multiple packages to be imported into a site in a specific order with a single optimised rebuild process. There is also a PackageImportHandler (cohesion_sync.package_import_handler) service available to access such functionality via PHP and Drupal services.
What actions do I need to take?
The new command is sitestudio:package:multi-import --path=<path/to/package_list.yml. Package list needs to follow specific format for the command to work, more information is available here.
Are there any risks I should be aware of?
Only new format packages (exports containing multiple yaml files, rather than single aggregated yaml file) are supported. Strict format of package list file needs to be followed. Import happens in the same order as listed in a package list. If multiple package import the same entity, only the last import will be taken into consideration. Reading documentation before attempting to use the new command is strongly recommended.
Next generation images
What is it?
Adds the ability to use Next generation images such as .avif and .webp images when using the Picture Element (subject to Drupal supporting these image formats).
What impact will there be?
This will fix an issue where the fallback image was the first image added to a Picture Element. The last image added to the Picture Element will now be used as the fallback.
What actions do I need to take?
drush cohesion:rebuild
Are there any risks I should be aware of?
None.
Bug Fixes
Missing permission check for saving components/helpers from a layout canvas
What is it?
The "Save" option allowed a user to save the layout canvas (or an item on it) both as Helper and as Component even if the user did not have permission to do so.
What impact will there be?
Users will now need the 'administer helpers' and/or 'administer components' permissions to use the Save functionality on layout canvases.
What actions do I need to take?
You may need to update user permissions if you were relying on this functionality.
Are there any risks I should be aware of?
None.
Site Studio generated CSS will now be aggregated
What is it?
Any stylesheet generated by Site Studio will now be aggregated with the rest of the website styles
What impact will there be?
All styles will now be aggregated increasing frontend performance.
What actions do I need to take?
None.
Are there any risks I should be aware of?
None.
Component contents not rendering
What is it?
Fixes an issue where component contents were not rendering after reverting to a previous revision or publishing a draft.
What impact will there be?
Component contents will now render as expected.
What actions do I need to take?
Run a rebuild as part of upgrading to this version.
Are there any risks I should be aware of?
None.
Inline css media queries will not render if all component fields are empty
What is it?
In the event where one or multiple fields attached to a style on a specific media query are not populated when the component is used, the media query will not render at all.
What impact will there be?
This will fix an issue where empty media query css would render, having no effect on the page
What actions do I need to take?
drush cohesion:rebuild
Are there any risks I should be aware of?
None.
Improvements to the link auto complete endpoint
What is it?
Some improvements made to the link auto complete endpoint used in the link element, which should improvement performance and use less memory. When inserting an external link the endpoint won't continue to look for content.
What impact will there be?
The auto complete functionality used in the link element should use less memory. When using the entity type selection within the link element, it now correctly displays the supported types. These types include: nodes, views, taxonomy terms, users, media and files.
What actions do I need to take?
None.
Are there any risks I should be aware of?
None.
Uncaught ReferenceError: _ is not defined console error
What is it?
Fixes a bug when editing a component on a layout canvas, the sidebar editor would throw a console error. If aggregation was enabled the sidebar browser did not load as expected.
What impact will there be?
This error will no longer appear and the sidebar editor will load as expected if aggregation is enabled.
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.
