Version 7.0.4 release details
Last updated: 21st March 2023
Released: 21st March 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
Color palette performance
What is it?
The color palette had performance issues when using a lot of different colors. Now there are no issues when using a large number of colors on the color palette page.
What impact will there be?
The performance on the website settings color palette will be improved.
What actions do I need to take?
A Site Studio import or drush cohesion:import
Are there any risks I should be aware of?
None.
Component dropzone content in component content
What is it?
There was an issue when saving a component as component content when it had a nested component in a component dropzone. When saving it didn’t include the component in the dropzone.
What impact will there be?
You will now be able to save component with nested components as component content.
What actions do I need to take?
A Site Studio import or drush cohesion:import
Are there any risks I should be aware of?
None.
Config entities no longer regenerate IDs
What is it?
When a config entity was saved via UI, Site Studio regenerated ID based on a hash of UUID. If entity was created via UI and UUID would match ID, this would not be noticeable. However, in the instances when entity ID or UUID was manually edited or the entity was not created via UI this would result in entity ID being changed on save.
What impact will there be?
Site Studio will only generate IDs for new entities or entities that don't have ID yet.
What actions do I need to take?
Entities re-saved via UI will retain their IDs, even if their ID is not based on UUID.
Are there any risks I should be aware of?
None.
Fixed logic on conditional form fields applying incorrectly in field repeater
What is it?
A regression in 7.0.x meant that component form fields inside field repeaters were no longer correctly showing/hiding based on other fields within the same repeated row.
What impact will there be?
Conditional display of fields will now behave as they did in versions prior to 7.0.x
What actions do I need to take?
A Site Studio import or drush cohesion:import
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.
