Version 7.3.2 release details
Last updated: 24th October 2023
Released: 24th October 2023
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
None.
Bug fixes
Unable to use special characters for colors in the website settings color palette
What is it?
Fixes a problem where users that had special characters in the name of their color caused an error when saving, and when trying to use in-use links.
What impact will there be?
You can now use special characters in the name of your colors
What actions do I need to take?
Site studio import and a cohesion rebuild
Are there any risks I should be aware of?
None.
Unable to save styles when using the CSS counter increment property.
What is it?
When using the CSS property counter increment and the value included a space you would be unable to save the style or rebuild.
What impact will there be?
Style can now be saved with a space in the value.
What actions do I need to take?
drush cohesion:rebuild
Are there any risks I should be aware of?
None.
Accordion and tab items not working as expected when used in pattern repeaters
What is it?
Fixes a problem when using accordions within a pattern repeater. Opening and closing accordions would no longer work, as well as various configuration options.
What impact will there be?
Accordion and tab items will now work as expected inside pattern repeaters.
What actions do I need to take?
Site studio import.
Are there any risks I should be aware of?
None.
Validation on boolean fields not working correctly
What is it?
Fixes a problem where certain boolean field weren't being validated correctly
What impact will there be?
Boolean field validation should work as expected now.
What actions do I need to take?
Site studio import.
Are there any risks I should be aware of?
None.
Unable to access custom styles on components
What is it?
Fixes a problem where certain users were unable to access the custom styles for elements.
What impact will there be?
Fixes the error that would occur if you were unable to reach the custom styles list.
What actions do I need to take?
Site studio import.
Are there any risks I should be aware of?
None.
Style preview not showing for Site studio styles in CKEditor
What is it?
Fixes a problem where you are unable to preview a style in the style dropdown for CKEditor
What impact will there be?
Styles will now be visible when you use the styles dropdown.
What actions do I need to take?
Site studio import.
Are there any risks I should be aware of?
None.
Fix generic heading styles from leaking into the visual page builder
What is it?
Fixes a problem that if a base style targeted the h3 selector, certain styles were overriden in the visual page builder.
What impact will there be?
No styles will leak onto the headings in visual page builder.
What actions do I need to take?
Site studio import.
Are there any risks I should be aware of?
None.
Error on theme appearance page when Style guide manager enabled and 'base_theme' for active theme is set to false
What is it?
Fixes an error that occurs on the theme appearance page when the Style guide manager module is enabled and 'base_theme' for active theme is set to false.
TypeError: property_exists(): Argument #1 ($object_or_class) must be of type object|string, null given in property_exists()
What impact will there be?
The error will no longer occur for themes that have 'base_theme' set to "false" and using the style guide manager.
What actions do I need to take?
Drupal cache clear.
Are there any risks I should be aware of?
None.
When tokenizing context visibility but no contexts are active & no condition set the context would wrongly fail
What is it?
Fixes a bug when tokenizing context visibility but no contexts are active and no condition set, the context would wrongly fail.
What impact will there be?
When tokenizing context visibility and no contexts are active and no condition set, the context will pass as expected.
What actions do I need to take?
Site Studio rebuild.
Are there any risks I should be aware of?
None.
Error in some scenarios when using TMGMT to translate
What is it?
Fixes a bug where the following error would occur in some scenarios when using TMGMT to translate components:
Error: Call to a member function getEntityTypeId() on null in cohesion_tmgmt_source_suggestions()
What impact will there be?
When translating using TMGMT in some scenarios the error will no longer occur.
What actions do I need to take?
Drupal cache clear.
Are there any risks I should be aware of?
None.
Entities are not displayed for anonymous users unless default language is published
What is it?
This addresses an issue whereby access to a translation is dictated by the default language status.
What impact will there be?
Translated entities rendered via Site Studio display independently regardless of default language publish status.
What actions do I need to take?
Drupal cache clear
Are there any risks I should be aware of?
None.
Steps before upgrading
As with any version of Acquia Site Studio, we recommend that you backup your websites database and code before upgrading the version of Acquia 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 Acquia Site Studio by following our upgrade guide.
