Last updated: 6th October 2021
Released: 6th October 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 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.7.0 of Site Studio.
We are moving default functionality when using Acquia ContentHub into a new contrib module. The new module is called "Site Studio Contenthub" and contains two new submodules sitestudio_contenthub_publisher and sitestudio_contenthub_subscriber. They add additional Site Studio support for Content publishing and importing via ContentHub.
Customers leveraging Content hub for Personalization/Lift integration with Site Studio will be required to take manual action to ensure continued operation, Site Studio related entities will no longer be published and imported until the new "Site Studio Contenthub" is downloaded and appropriate submodule is enabled. Once the submodules are enabled, the functionality will resume, but integration behaviour might be different, depending on how it was used until 6.7.0. Please refer to the documentation to find out more.
If integration with Acquia ContentHub is required, please read updated documentation, download the new "Site Studio Contenthub" and enable submodules relevant to the Publisher and the Subscriber sites.
This update removes default integration with ContentHub. If no actions are taken, Layout Canvas entities will no longer be published and imported via ContentHub. Once the new module is downloaded relevant submodules are enabled, ContentHub integration with Site Studio will resume, but will behave differently compared to 6.6.0 and earlier versions. More information is available here.
When exporting site studio assets you can now set a setting to export all json values non serialised. This is to increase the readability of packages when doing diffs, as it will output json values in multiple lines.
None.
To enable this functionality add $settings['site_studio_package_multiline'] = TRUE to your settings.php
None.
PHP 8 has added supported for named arguments. This can cause problems when using call_user_func_array() as is the case with batch operations - see https://wiki.php.net/rfc/named_params for the changes in question.
Site Studio batch operations will operate as expected on php 8.0 base environments as of 6.7.0.
None.
None.
This fixes a bug where config would be loaded before bootstrap causing side effect on other services.
None.
None.
None.
This fixes a bug where entity references inside field repeater would not be updated properly resulting in a broken reference.
There is no impact and entity references should now be linked to the right entities.
drush cohesion:rebuild
None.
Fixes a bug where nested components inside pattern repeaters with tokenized fields where not rendering.
Components that are nested inside another component and use a pattern repeater, that contain tokenized values will now render as expected.
Run a rebuild.
None.
Fixes a bug when using a components configure links on a layout canvas on a sub-directory multi-site setup, the URL returned was incorrect.
The component layout canvas configure links 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.
Fixes a bug where the edit page of a component content would throw a Call to undefined method isReusable() error when moderation is enabled.
Editing component content while having content moderation enable on it will now work.
None.
None.
Component content that is placed on a layout canvas is now referenced by its UUID rather than ID. This makes it compatible with modules such as Contenthub and default content.
There should be no impact from a users perspective. Any existing component contents on layout canvases will be updated to reference by UUUID, and new ones will be referenced by UUIDs.
When upgrading be sure to follow the upgrade guide and run a rebuild when stated.
None.
Fixes a bug where the warning "Tokens or token types missing name property." appears on the Drupal status page when using the template selector field.
This warning will no longer appear.
Run drush updb as usual when upgrading.
None.
Fixes an issue where if a context is missing it would appear as "undefined" in the context visibility select where it had been used.
If a context has been selected in the context visibility select and is subsequently then removed, it will now show "Selected context is missing."
drush cohesion:import
None.
Fixes a bug where a users account is cancelled and component content that they had created should be reassigned, unpublished or deleted, was not being re-assigned or deleted correctly.
When cancelling a user account that has created component content it will be re-assigned, unpublished or deleted correctly based on what the user selects when cancelling the users account.
None.
None.
Fixes a bug when installing Site Studio through a profile, would result in a 403 rather than being logged in as user 1.
Installing Site Studio through a profile will now log the user in after installation as expected.
None.
None.
Fixes a bug where Entity browser URLs don't respect sub-directory multi-site setup and the URL returned was incorrect for this setup.
The URLs are now correct for both sub-directory multi-site setup and standard Drupal setups.
None.
None.
Fixes a bug where the component builder elements category did not show in the sidebar browser as expected on component creation and edit forms, if certain referer policies were in place.
The component builder elements category will now appear as expected even if certain referer policies are in place.
None.
None.
Fixes a bug where the sync file chunk URL was hardcoded rather than generated through Drupal.
No error will be encountered when importing a sync file through the UI on a sub-directory site.
None.
None.
Fixes a bug where a call to an undefined method for entity types that do not use the trait EntityPublishedTrait and as such do not have a isPublished() method.
The error will no longer appear.
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.
Tue Mar 25 2025 21:22:26 GMT+0000 (Coordinated Universal Time)