Site Studio
Site Studio 6.4.1 - January 18, 2021
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.
There are no known issues with version 6.4.1 of Site Studio.
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.
Reduce the time and memory required to run the sync:import process.
Usage:
drush sync:import --no-rebuild
Ensure a rebuild step is included as part of your scripts when employing this flag.
Adds the ability to set the font-display CSS property when uploading a new web font.
None.
drush cohesion:import
None.
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.
More granular control on how/when a site enters and leaves maintenance mode.
Usage:
drush sync:import --no-maintenance
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.
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.
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.
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.
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?
The drush command for rebuild now has a new option --no-cache-clear which removes the cache clear from the batch it performs.
If the option is specified the rebuild will take less memory to run the rebuild process.
Usage:
drush cohesion:rebuild --no-cache-clear
You will still need to run a drush cr after the rebuild.
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.
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.
None.
None.
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)
If using the Link attributes module and Site studio you should no longer see any errors on your site.
When upgrading a Site Studio import and rebuild should be run.
None.
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.
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
None.
None.
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.
Deleting Components with inline styles will reduce size of stylesheets immediately, without having to run rebuild.
None.
None.
A large number of twig cache file were created when rendering inline styles, causing the twig cache folder to grow overtime very quickly.
The number of twig cache file will stop growing when using inline styles.
If you want to clear the twig cache folder you should clear the websites cache.
None.
Reducing new lines within inline CSS style blocks that are generated by Site Studio.
Websites that use inline CSS styles generated by Site Studio, will now take up less space within the head of the page.
None.
None.
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.
The inline editing pencils should now always show.
None.
None.
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".
Translating content using TMGMT in this scenario will no longer return an error and return the translated content.
None.
None.
Fixes a bug where the translated:// stream wrapper and other hidden stream wrappers were being incorrectly passed into a Twig extensions function.
When saving a translated node you should no longer see these errors and it has been handled correctly.
None.
None.
The sync import batch process has been reworked to hold less in memory.
Large sync package will use less memory when imported via the UI and therefore will be less prone to out of memory errors.
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.
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.
Site Studio