Version 7.0.0 release details
Last updated: 9 December 2022
Released: 9 December 2022
When upgrading your website to the latest version of Acquia Site Studio, database updates will be applied and therefore you can't roll back to the previous version of Acquia Site Studio once upgraded.
It is recommended applying updates on your development environment and backing up your website including your database before upgrading Acquia Site Studio.
Known issues
- When Visual Page Builder sub-module is enabled Javascript errors are printed to the console due to incorrect dependency ordering.
Apply the following patch to rectify this issue: https://www.drupal.org/project/drupal/issues/3222107
Highlights
Drupal 10 compatibility
What is it?
Site Studio v7.0 is compatible with Drupal 9.4, 9.5 and 10. A number of changes have been implemented due to Drupal 10 requirements:
- CKEditor 5 support added
- jQuery UI and Stable theme contrib dependencies added
- PHP 8.1 support added
- Drupal 8 support removed
What impact will there be?
Site Studio will no longer be installable on Drupal 8, however, it can now optionally be installed on Drupal 10 with support for PHP 8.1
What actions do I need to take?
Site Studio v7.0 supports CKEditor 5 only; you are required to manually migrate text formats from CKEditor 4 to CKEditor 5, this should be completed on Drupal 9.x before upgrading to 10.x
For details on migration steps visit.
Are there any risks I should be aware of?
Some CKEditor plugins do not currently have support for CKEditor 5.
For more details please refer to the following: https://www.drupal.org/docs/core-modules-and-themes/core-modules/CKEditor-5-module/upgrade-coordination-for-modules-providing-CKEditor-4-plugins
CKEditor 4 support removed
What is it?
Site Studio v7.0 only supports CKEditor 5, support for the now deprecated CKEditor 4 has been removed.
Note: A fresh install of Site Studio will provide a pre-configured CKEditor 5 text editor/format.
What impact will there be?
CKEditor 4 based text formats are not supported in Site Studio v7.0.
What actions do I need to take?
You are required to manually migrate text formats from CKEditor 4 to CKEditor 5, this should be completed on Drupal 9.x before upgrading to 10.x.
For details on migration steps visit.
Are there any risks I should be aware of?
Some CKEditor plugins do not currently have support for CKEditor 5.
For more details please refer to the following: https://www.drupal.org/docs/core-modules-and-themes/core-modules/CKEditor-5-module/upgrade-coordination-for-modules-providing-CKEditor-4-plugins
Legacy Site Studio Sync user interface now hidden by default
What is it?
The legacy Site Studio Sync user interface options are only shown if a site builder enables "Show legacy sync in UI" within the Site Studio system settings. Legacy drush command are not affected.
What impact will there be?
The legacy sync options for importing and exporting Site Studio config will only appear in the UI if the "Show legacy sync in UI" has been enabled within the Site Studio system settings.
What actions do I need to take?
Toggling on "Show legacy sync in UI" in the Site Studio system settings is required to show the legacy options in the UI. We recommend for users to use the updated sync system, and only toggle this option on if required.
To enable this by default add the following to your settings.php file:
$config['cohesion.settings']['sync_legacy_visibility'] = TRUE;
Are there any risks I should be aware of?
None.
Module API hooks namespace update
What is it?
Module API hooks previously had the namespace of dx8, this has been updated to sitestudio. Previous hooks have been marked as deprecated.
What impact will there be?
The deprecated hooks will continue to work for the time being until removed, it is recommended to update any API hooks that your websites uses to the new namespace sitestudio.
What actions do I need to take?
If a website is using one of the API hooks, the namespace should be updated from dx8 to sitestudio.
Are there any risks I should be aware of?
If the API hooks namespace is not updated, then they will not work in a future version of Site Studio where the previous namespaces are used.
Custom element form HTML class change
What is it?
The format of the HTML classes used to layout custom element forms has been updated. Previously 'col-xs-12' is now 'ssa-grid-col-xs-12'.
What impact will there be?
If a site uses custom elements, the elements form will need the htmlClass in the form element array updated.
What actions do I need to take?
Custom elements forms will need the htmlClass in the form element array updated to the new format, or the form will not be laid out as expected. See 'example_element' module for examples.
Are there any risks I should be aware of?
If no action is taken, then the custom elements form will not be laid out as expected.
stable contrib module added as a dependency of Site Studio
What is it?
To provide support for both Drupal 9 & 10 a dependency on the stable module has been introduced to Site Studio.
Site Studio uses on stable theme as base theme for cohesion_theme theme, however, the stable theme this has been removed in Drupal core 10.x see https://www.drupal.org/node/3309392 for details.
What impact will there be?
Site Studio frontend features will continue to function as expected.
What actions do I need to take?
Download and enable the stable module and install stable theme.
Are there any risks I should be aware of?
None.
jquery_ui contrib module added as a dependency of Site Studio
What is it?
To provide support for both Drupal 9 & 10 a dependency on the jquery_ui module has been introduced to Site Studio.
Site Studio relies on jQuery UI for a number of frontend features, however, the library definition for this has been removed in Drupal core 10.x see drupal.org/project/drupal/issues/3277744 for details.
What impact will there be?
Site Studio frontend features will continue to function as expected.
What actions do I need to take?
Download and enable the jquery_ui module.
Are there any risks I should be aware of?
None.
Custom components can be ordered by a defined weight
What is it?
Custom components can now have a weight defined within the yml file, which allows them to be ordered with other custom components in the same category.
What impact will there be?
Custom components can now be ordered by weight, but only with other custom components in the same category. They will not be ordered within all components in the same category.
What actions do I need to take?
When adding a weight to the yml file the Drupal cache should be cleared for the ordering to take effect.
Are there any risks I should be aware of?
None.
Form helpers can be used in the custom component builder
What is it?
When building a custom component using the custom component builder, developers can now use form helpers to help with the development of their custom component forms.
What impact will there be?
Form helpers are now available from the sidebar browser on the custom component builder page and can be used to help build a custom components form.
What actions do I need to take?
A Site Studio import & Drupal cache clear.
Are there any risks I should be aware of?
None.
Custom components in-use tracking
What is it?
Custom component's usage can now be tracked via the Site Studio in-use system. Within the components list builder page, next to a custom component it will now display either an "in-use" link, so users can see where a custom component has been used or be shown as "Not in use".
What impact will there be?
Users can see where custom components have been placed.
What actions do I need to take?
None.
Are there any risks I should be aware of?
None.
Removing the "clone" option from Site Studio list builders
What is it?
Removing the "clone" option that the Entity Clone module adds, from Site Studio configuration list builders as Site Studio provides its own "duplicate" functionality. The "clone" functionality did not work as expected for Site Studio configuration entities.
What impact will there be?
If the Entity clone module is installed, the "clone" option will not appear in the operation list on Site Studio list builders.
What actions do I need to take?
If users want to "clone" a Site Studio configuration entity, use the "duplicate" operation.
Are there any risks I should be aware of?
None.
Create a component content from a custom component via the UI
What is it?
The ability to create a component content from a custom component direct in the UI at Site Studio > Components > Component Content > Create Component Content rather than from the Layout Canvas.
What impact will there be?
Component contents can be created from a custom component directly in the UI as is possible with components and no longer has to be created from a Layout Canvas.
What actions do I need to take?
None.
Are there any risks I should be aware of?
None.
Limit allowed HTML tags filter is now enabled by default on Site Studio text format
What is it?
The Limit allowed HTML tags and correct faulty HTML filter is now enabled by default on the Site Studio text format.
What impact will there be?
New Site Studio module installations will have theLimit allowed HTML tags and correct faulty HTML filter enabled on the Site Studio text format.
What actions do I need to take?
Existing sites are not affected by this change, but it is recommended to enable the Limit allowed HTML tags and correct faulty HTML filter on the Site Studio text format.
Are there any risks I should be aware of?
New Site Studio module installs or reinstalls, the "Site Studio" text format will now limit the use of HTML tags within WYSIWYGs to the specific HTML tags configured in the text format.
On existing Site Studio installs no change will occur and user action is required to limit the allowed HTML tags in the text format by enabling the Limit allowed HTML tags and correct faulty HTML filter in the "Site Studio" text format.
View filter labels
What is it?
The View filter element has a new toggle option, "Show filter label", which when set will render the filter or sort label set within the Drupal view. By default, this option is toggled off for backward compatibility.
What impact will there be?
View filters can have labels that have been set within the Drupal view.
What actions do I need to take?
If a view filter should display a label, the "Show filter label" option should be toggled on within the view filter element.
Are there any risks I should be aware of?
None.
Bug fixes
The menu-link tokens not working in menu templates
What is it?
The menu-link tokens were not rendering any values within menu templates.
What impact will there be?
The menu-link tokens will now work as expected in menu templates.
What actions do I need to take?
None.
Are there any risks I should be aware of?
None.
Custom menu link attributes were not being added to menu links as expected
What is it?
Fixes an issue were when using the menu link attributes module, and adding custom attributes they were not being rendered as expected.
What impact will there be?
Custom menu link attributes added to menu items will now be rendered on menu links.
What actions do I need to take?
Perform a Site Studio import & rebuild as per the upgrade steps.
Are there any risks I should be aware of?
If custom attributes were added to menu links in the past they will now render.
Menu template loses menu link context after rendering menu links
What is it?
Fixes a bug where menu templates with multiple levels were losing token context depending on where the elements were placed within the menu template.
What impact will there be?
The token context will not be lost and the token content will now render as expected within the menu.
What actions do I need to take?
A Site Studio import & rebuild.
Are there any risks I should be aware of?
We recommend visually testing menu layout of a rendered pages for sites that have multi-level menus and are using tokens to display content for specific links.
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.
