Last updated: 14th January 2022
Released: 14th January 2022
Adds a new feature to the layout canvas to allow you to undo changes to the layout canvas and redo. Two buttons are added to the top of a layout canvas allowing you to go back and go forward with your changes.
Two new buttons added to the layout canvas.
None.
There is the risk of manually deleting data by using the buttons inadvertently.
Adds a new feature to the layout canvas to allow you to copy the token value of the layout canvas node. This allows you to easily copy and paste tokens without having to type them manually any more.
A new button on layout canvas nodes. Improved usability.
None.
None.
We have updated the entity definition of Package config entities - config_prefix now matches entity id. Where previously entity id was cohesion_sync_package and config_prefix was package, now both are cohesion_sync_package.
There is no impact to packages exported via Site Studio package management mechanisms. Package entity definitions exported via Drupal should be renamed to use updated prefix.
If package entity definition was exported as an individual file via Drupal config, the file should be renamed in order for it to work correctly. For example, file exported as cohesion_sync.package.pack_test_package.yml should be renamed to cohesion_sync.cohesion_sync_package.pack_test_package.yml.
If Site Studio Package entity was exported via Drupal configuration management and package file is not renamed, importing such file will prevent the entity from behaving as expected, for example it will not appear in Package list.
Custom elements can now be containers, this allows other elements to be placed inside them. This gives developers more flexibility when creating custom elements.
There is no impact on existing custom elements.
To make a custom element a container you need to implement a few extra bits of code. Please see an example in the example element module of how to implement: example_element/src/Plugin/CustomElement/ContainerExample.php
Please see how to create a custom element user guide for more information.
None.
When a rebuild operation is run, an event is dispatched at the time the operation starts and completes. This allows developers to write event subscribers to listen for these events and trigger further actions if required.
Events will be dispatched during a Site Studio rebuild.
To take advantage of these events, event subscribers will need to be created in custom code.
None.
A message will appear when installing Site Studio via composer suggesting to install the node revision delete module. If the node revision module isn't installed a message will also appear on the Drupal status page.
None.
None.
None.
A new drush sync command drush sitestudio:package:list which lists available sync packages created using the package manager.
Running the command will list out available sync packages names and IDs in the CLI.
None.
We are adding new Drush command that allows Site Studio Package export and import via individual files. This command no longer encodes Images and keeps Config files individually, allowing for better Developer experience. Config files are exported with pretty-printed Json, allowing for human readability and review of exported config. Images and other files exported with the package are now exported in their respective formats. Both individual files and full package export options are available.
The new commands will not be compatible with config exported by using old commands. Old commands are still available for use. The new Package export and import will behave in a way that is very similar to the Drupal config export and import via Drush.
We encourage trying new Import and Export commands as they significantly reduce the time required for Package import and export. Additional information about the new commands is available here
Mysql settings for max_allowed_packet on the environment needs to be large enough to be able to handle whole package in a single Database transaction.
In context editing functionality is being deprecated in Drupal core, therefore support for in context editing on Components and Component content on the front-end has been removed in line with this.
Components and Component content in context editing will no longer be available. The Visual page builder can be used to edit a Site Studio layout canvas on the front end - please see using the visual page builder for building pages and editing content.
None.
None.
Fixes a bug where an error would be thrown in the console when using menu template Uncaught TypeError: Cannot read property 'xl' of undefined on menu template.
Using template will not throw that error.
None.
None.
Fixes a bug where some components content was not rendering when within a patter repeater.
Components that use pattern repeaters and are not rendering content will start rendering as expected.
None.
None.
The permission "access contextual links" is no longer needed to use the Visual page builder.
Access contextual links permission is no longer needed to use the Visual page builder.
To use the Visual page builder these permissions are needed:
If the permission "access contextual links" was applied to a role specifically to allow access to the Visual page builder this can be removed.
None.
Fixes a bug when using a paragraph and entering some multilingual letters which included line breaks, were not breaking onto separate lines as expected.
Multilingual letters will now line break as expected within paragraph elements.
You should perform a drush cohesion:import & drush cohesion:rebuild
None.
The visual page builder would not work and return an error if the page contains a block that has a layout canvas. This could be a custom block or a view rendering entities with layout canvases
No impact but it is worth noting that only the layout canvas of the page can be edited with the Visual page builder. Any entity rendered by a layout canvas that itself contains a layout canvas would need to be edited in the admin
You should clear cache: drush cr
None.
Adds the relevant data handler to enable component_content entities to be utilised with the views module.
It will now be possible to create custom views listing component_content entities.
None.
None.
Fixes a bug where modals used on an Ajax enabled view, would not open after the Ajax action had been triggered.
Modals loaded with Ajax will now work as expected.
You should perform a drush cohesion:import
None.
Fixes a bug where inputting a Youtube no cookie URL was still using the normal embed URL.
Youtube no cookie URLs will now work as expected.
You should perform a drush cohesion:import
None.
Fixes a bug where templates that are more specific would not be deleted and still be selected as the template to render. Only deleting all templates and run a drush cohesion:rebuild would fix the issue
There is not impact, follow the instructions below to resolve the issue
You should perform a drush cohesion:rebuild
None.
Fixes a bug when changing the Base font size is Base unit settings from 16px, CSS media queries were being incorrectly calculated into rem units.
All Site studio generated CSS styles will now use pixel (px) units on CSS media queries.
drush cohesion:rebuild
None.
This fixes a bug where some PHP notices were appearing when using Better exposed filters on a view.
No PHP notices will appear relating to Better exposed filters.
None.
None.
The package entity was appearing within the exclude entity types list when creating a package in the UI, this could produce a blank package export if "packages" was selected to be excluded.
The package entity can no longer be excluded from packages.
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.