Version:

Acquia Cohesion renames to Site Studio from version 6.2. Tell me more.

    Version 6.3.5 release details

    Last updated: 19th November 2020
    Released: 19th November 2020

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

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

    Known issues

    There are no known issues with version 6.3.5 of Acquia Cohesion.

    Highlights 

    Save template in the database

    What is it?

    Adds the ability to switch a template storage from the file system to the key value storage

    What impact will there be?

    If enabled Site Studio will be using the database more often as it will save all config templates in the database

    What actions do I need to take?

    To enable this feature you need to change the alias of the cohesion.template_storage services to point to cohesion.template_storage.key_value

    You can do so by providing a site specific services.yml and provide the path to it in your settings.php

    Example:

    env.services.yml

    services:
    cohesion.template_storage:
    alias: cohesion.template_storage.key_value

    settings.php

    $settings['container_yamls'][] = '/path/to/env.services.yml'

    Are there any risks I should be aware of?

    Database utilisation will increase especially during rebuild and sync operations, be aware that this will also increase the size of your database.

    Bug fixes

    Unable to upload icon and font library files on Drupal 9

    What is it?

    Fixes a bug where attempting to upload an icon or font library file through the UI resulted in the error: Error occurred while uploading the file. and the file not being saved.

    What impact will there be?

    Icon and font library files can now be uploaded through the UI on Drupal 9 sites without error.

    What actions do I need to take?

    None.

    Are there any risks I should be aware of?

    None.

    Ability to execute javascript into the link element url

    What is it?

    Fixes a bug where site editors could inject javascript and potentially other harmful markup, into the link to page field on the link element and link to page component form field.

    What impact will there be?

    A user without the Bypass XSS validation in element forms permission will not be able to inject Javascript or HTML into the link to page field on a link element. If the value is not a valid link it will go through the XSS filter.

    Where a link to page field on a component has been used and the value input is not a valid link the value will not render out.

    Valid links values include: Using the autocomplete (node::1), /my-page, external links and mailto:.

    What actions do I need to take?

    None.

    Are there any risks I should be aware of?

    Any value that is not a valid link and been input into a component link field will no longer render out that value in the href.

    IMCE & Media library not loading on sub-directory multi-site setups

    What is it?

    Fixes a bug when using IMCE and Media library integration with Site studio used relative URLS, where in a sub-directory multi-site setup, the URL returned was incorrect.

    What impact will there be?

    IMCE and Media library will now work for multi-sites that are configured in a sub-directory setup. For example: www.domain.com/site1 www.domain.com/site2

    What actions do I need to take?

    None.

    Are there any risks I should be aware of?

    None.

    Cache context on menu items preventing inline style from rendering

    What is it?

    Fixes a bug where adding cache context to link inside a menu would prevent inline style on components living alongside the menu to render.

    What impact will there be?

    Adding cache context should not impact the rendering of styles.

    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 Acquia Cohesion, we recommend that you backup your websites database and code before upgrading the version of Acquia Cohesion. 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 Acquia Cohesion by following our upgrade guide.

    DX8 knowledge base icon

    Frequently asked questions

    Get instant answers to common questions. Available online 24/7.

    Find answers

    Raise a ticket icon

    Raise a support ticket

    To raise a ticket, sign into Acquia Cloud and select Help in the top menu.

    Raise support ticket

    Acquia

    Copyright © 2020 Acquia, Inc. All Rights Reserved. Drupal is a registered trademark of Dries Buytaert.