Version 6.4.2 release details
Last updated: 8th March 2021
Released: 8th 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 of Site Studio 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.4.2 of Site Studio.
Bug fixes
Typo/Incorrect permission for 'Add component content' route
What is it?
Fixes a permissions issue limiting access to the add component content page.
What impact will there be?
Users with administer component content can access Site Studio > Components > Component content > Add component content as expected.
What actions do I need to take?
None.
Are there any risks I should be aware of?
None.
Unable to create a translation of component content
What is it?
Fixes an issue where creating a translation of component content could result an error and it was not appearing the sidebar browser.
Error: Call to a member function getCategoryEntity() on null in Drupal\cohesion\Services\CohesionUtils->getPayloadForLayoutCanvasDataMerge()
What impact will there be?
No further error messages should occur when creating a translation of component content, they should also now appear as expected within the sidebar browser.
What actions do I need to take?
As part of the upgrade make sure to run drush updb.
Are there any risks I should be aware of?
None.
Can't tokenize styles in the style builder on a component when TMGMT module is enabled
What is it?
When the TMGMT module is enabled users are unable to tokenize Styles in Style builder.
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
Compatibility with the Webprofiler module
What is it?
Fixes an issue where enabling the webprofiler module prevents some actions (eg. drush commands) from completing properly.
What impact will there be?
No code related issues will be observed relating to the webprofiler module being enabled.
What actions do I need to take?
None.
Are there any risks I should be aware of?
None.
Empty styles in the head
What is it?
Fixes an issue where if you have a component which applies styles to an element but the editor does not specify any value when using the component, an empty style in the head would be generated
What impact will there be?
No empty css selector will be printed on the page
What actions do I need to take?
drush cohesion:rebuild
Are there any risks I should be aware of?
None.
Component content edit links containing two language prefixes
What is it?
Fixes an issue where if you have a default language prefix, the component content edit link from the layout canvas contained two language prefixes and therefore resulted in an invalid link.
What impact will there be?
If the default language has a prefix, the component content edit links from the layout canvas are now correct.
What actions do I need to take?
None.
Are there any risks I should be aware of?
None.
Unpublished content entities appearing in typeaheads
What is it?
Fixes an issue where unpublished content entities were appearing in typeaheads when searching for content. This meant that site editors could link to content that was not yet published and could lead to 404s.
What impact will there be?
Unpublished content entities no longer appear in typeaheads when searching for content in the Entity browser, Entity reference and link elements.
What actions do I need to take?
None.
Are there any risks I should be aware of?
None.
Can't insert media from media library after using the filters
What is it?
Fixes an issue where after using the filters in the Media Library you were not able to insert media, this resulted in an ajax error.
What impact will there be?
You will now be able to use the media library filters and insert media without error.
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.
