Version 7.4.3 release details
Last updated: 4th March 2024
Released: 4th March 2024
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
Fixed Exception thrown in relation to nested repeaters
What is it?
Fixes an issue where nested pattern repeaters could result in Twig syntax exception when adding items to the outter pattern repeater.
What impact will there be?
Pattern repeater field should now work more reliably.
What actions do I need to take?
Site Studio rebuild or individual affected node resave, if you were affected by this issue.
Are there any risks I should be aware of?
None.
Warning message during database update 9004
What is it?
Fixes an issue where running database update cohesion_update_9004 would trigger warning message like so:
[warning] foreach() argument must be of type array|object, null given cohesion.install:1372
What impact will there be?
The warning message will no longer be displayed.
What actions do I need to take?
Drupal cache clear if the cohesion_update_9004 has not been performed yet.
Are there any risks I should be aware of?
None.
TMGMT support for custom components
What is it?
Adds support for custom component field content to be translated using TMGMT.
What impact will there be?
Custom component fields can be translated using TMGMT and toggled as they can for UI components in the custom component builder. If these settings are changed the form JSON will need to be re-downloaded and added to the custom component module.
What actions do I need to take?
Drupal cache clear.
Are there any risks I should be aware of?
None.
Acquia DAM pagination un-styled while using the page builder
What is it?
When using Acquia DAM through the media library in page builder, the pagination was un-styled.
What impact will there be?
The pagination is now styled when using the page builder.
What actions do I need to take?
Drupal cache clear.
Are there any risks I should be aware of?
None.
Layout canvas appearing as a reference option when creating new fields
What is it?
Stops the layout canvas appearing as a reference option when creating a new reference field on a content type in Drupal 10.2 and Entity Reference Revisions 1.11. This option has been removed as layout canvases shouldn't be referenced this way.
What impact will there be?
The layout canvas will no longer appear as an option when creating a new Drupal reference field on a content type.
What actions do I need to take?
Drupal cache clear.
Are there any risks I should be aware of?
None.
Exception thrown when attempting to render certain types of links using the link to page field
What is it?
Fixed an exception that was thrown when attempting to render external links that contain colons.
What impact will there be?
These types of links should now render as expected and no exception is thrown.
What actions do I need to take?
Drupal cache clear.
Are there any risks I should be aware of?
None.
Editing translations in page builder result in wrong translation being updated
What is it?
When editing a multilingual website using the page builder; with specific language detection and selection setup, saving changes would sometimes apply to the incorrect translation.
What impact will there be?
Editing a multilingual website using the page builder with any language detection and selection setup should result in saving the correct translation.
What actions do I need to take?
Drupal cache clear.
Are there any risks I should be aware of?
None.
Resolved issues around behaviour of field repeaters and conditional fields
What is it?
Fixed several issues where in certain circumstances a Component form could be configured in such a way that the values of form fields inside a field repeater would be mixed up or set incorrectly when re-arranging or removing rows from the form.
What impact will there be?
Field repeaters should behave in a more consistent way in these cases.
What actions do I need to take?
Site Studio Import.
Are there any risks I should be aware of?
None.
Improved Entity Browser field stability when on slow internet connections
What is it?
Fixed an issue where selecting an entity using the Typeahead Entity Browser would sometimes appear to select the wrong entity as a result of a race condition triggered by requests to the server taking longer than expected.
What impact will there be?
The Typeahead Entity Browser should now work more consistently.
What actions do I need to take?
Site Studio Import.
Are there any risks I should be aware of?
None.
Fixed Typeahead Entity Browser field displaying incorrect value when inside a Field Repeater
What is it?
Fixed an issue where Typeahead Entity Browser's inside Field Repeaters could get out of sync when changing the order of or removing rows from the Field Repeater.
What impact will there be?
The Typeahead Entity Browser should now work more consistently.
What actions do I need to take?
Site Studio 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.
