Version:

    Version 6.4.1 release details

    Last updated: 18th January 2021
    Released: 18th January 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.1 of Site Studio.

    Highlights 

    Provide optional flag for sync:import to prevent calls to the API

    What is it?

    Adds new optional argument --no-rebuild to the sync:import drush command. When using the command with the argument, no entity rebuilds are triggered reducing calls to the API. This is useful when a rebuild is likely to be run in a subsequent script during a deployment for example.

    What impact will there be?

    Reduce the time and memory required to run the sync:import process.

    What actions do I need to take?

    Usage:

    drush sync:import --no-rebuild

    Are there any risks I should be aware of?

    Ensure a rebuild step is included as part of your scripts when employing this flag.

    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.

    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.

    Provide optional flag for sync:import to prevent the site going in maintenance mode

    What is it?

    By default the sync:import drush command will put the site into maintenance mode, this feature provides a --no-maintenance flag to optionally disable this action. This is useful on platforms such as Acquia Site Factory where this behaviour is handled by the internal update hooks.

    What impact will there be?

    More granular control on how/when a site enters and leaves maintenance mode.

    What actions do I need to take?

    Usage:

    drush sync:import --no-maintenance

    Are there any risks I should be aware of?

    A site should be in maintenance mode during the sync:import procedure to avoid cache issues, ensure this is handled by either the platform or additional scripts when employing the --no-maintenance option.

    Compressing data to the Site studio API

    What is it?

    By default Site Studio will send data to its API using gzencode to reduce the traffic. It can be turned off by setting the config cohesion.settings compress_outbound_request to 0.

    What impact will there be?

    If enabled, when saving an entity through the UI or via drush cohesion:rebuild, the process will be faster as less traffic will be necessary.

    What actions do I need to take?

    If your server does not have zlib you might want to turn this off by doing drush config-set cohesion.settings compress_outbound_request 0 or install zlib.

    Are there any risks I should be aware of?

    This is now turned on by default, make sure zlib is installed on your server or you might see some failures. See What actions do I need to take?

    Added the ability to not run a cache clear on drush cohesion:rebuild

    What is it?

    The drush command for rebuild now has a new option --no-cache-clear which removes the cache clear from the batch it performs.

    What impact will there be?

    If the option is specified the rebuild will take less memory to run the rebuild process.

    What actions do I need to take?

    Usage:

    drush cohesion:rebuild --no-cache-clear

    Are there any risks I should be aware of?

    You will still need to run a drush cr after the rebuild.

    Bug fixes

    Entity browser element error appearing unexpectedly

    What is it?

    Fixes an issue where "This element requires the Entity browser or Media library modules enabled" error appeared even though users had either module installed. Also resolves another issue where you could not select "Typeahead" without "Entity browser" module being installed.

    When adding a new Entity browser element to a Layout canvas the default option is now set to Typeahead as this is not module dependent.

    What impact will there be?

    The Typeahead option in the Entity browser element can be used without Entity browser or Media library modules installed and users should no longer experience the any error messages appearing unexpected.

    What actions do I need to take?

    None.

    Are there any risks I should be aware of?

    None.

    Compatibility with Link attributes module

    What is it?

    Fixes an issue when using the Link attributes module with Site studio. This error would appear in the logs: User error: "0" is an invalid render array key in Drupal\Core\Render\Element::children() (line 97 of /var/www/drupal/standard/web/core/lib/Drupal/Core/Render/Element.php)

    What impact will there be?

    If using the Link attributes module and Site studio you should no longer see any errors on your site.

    What actions do I need to take?

    When upgrading a Site Studio import and rebuild should be run.

    Are there any risks I should be aware of?

    None.

    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.

    Deleting a component removes it's styles from stylesheet

    What is it?

    Deleting Components with inline styles in Drupal now removes the styles for such components from the stylesheet. Previously this would be done only during rebuilds.

    What impact will there be?

    Deleting Components with inline styles will reduce size of stylesheets immediately, without having to run rebuild.

    What actions do I need to take?

    None.

    Are there any risks I should be aware of?

    None.

    Limiting the number of twig cache file created when using inline styles

    What is it?

    A large number of twig cache file were created when rendering inline styles, causing the twig cache folder to grow overtime very quickly.

    What impact will there be?

    The number of twig cache file will stop growing when using inline styles.

    What actions do I need to take?

    If you want to clear the twig cache folder you should clear the websites cache.

    Are there any risks I should be aware of?

    None.

    Reducing new lines within the inline CSS

    What is it?

    Reducing new lines within inline CSS style blocks that are generated by Site Studio.

    What impact will there be?

    Websites that use inline CSS styles generated by Site Studio, will now take up less space within the head of the page.

    What actions do I need to take?

    None.

    Are there any risks I should be aware of?

    None.

    Inline editing pencil not always appearing

    What is it?

    Fixed a bug where in certain situations when the browser was zoomed in and at specific widths, the Site Studio inline editing pencils did not always appear.

    What impact will there be?

    The inline editing pencils should now always show.

    What actions do I need to take?

    None.

    Are there any risks I should be aware of?

    None.

    Translating with TMGMT, translated content sometimes resulting in "null"

    What is it?

    Fixes a bug where an error appeared when attempting to translate content, that had a Layout canvas field and other Drupal fields through TMGMT. This resulted in some translated content values being returned as "null".

    What impact will there be?

    Translating content using TMGMT in this scenario will no longer return an error and return the translated content.

    What actions do I need to take?

    None.

    Are there any risks I should be aware of?

    None.

    Saving translated nodes could result in stream wrapper exceptions in Drupal logs

    What is it?

    Fixes a bug where the translated:// stream wrapper and other hidden stream wrappers were being incorrectly passed into a Twig extensions function.

    What impact will there be?

    When saving a translated node you should no longer see these errors and it has been handled correctly.

    What actions do I need to take?

    None.

    Are there any risks I should be aware of?

    None.

    Sync import batch to consume less memory

    What is it?

    The sync import batch process has been reworked to hold less in memory.

    What impact will there be?

    Large sync package will use less memory when imported via the UI and therefore will be less prone to out of memory errors.

    What actions do I need to take?

    You might be able to decrease the memory limit needed to run a sync import via the UI if you had to increase it to overcome this issue.

    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.

    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.