Last updated: 7th August 2025
Released: 7th August 2025

• Known issues
• Highlights
• Bug fixes

Known issues¶

None.

Highlights¶

Site Studio API relocates¶

What is it?¶

Site Studio API is now available at a new location - https://api.sitestudio.acquia.com.

What impact will there be?¶

Site Studio style compilation services have a new architecture to improve API response times.

What action do I need to take?¶

Remove all API URL overrides that use dx8_editable_api_url.

Are there any risks I should be aware of?¶

After completing the upgrade steps, verify that all styles compile as expected.

Experimental decision tree feature¶

What is it?¶

A new form builder feature that supports conditional logic rules to control field behavior. Use the decision tree to:

• Show or hide fields based on conditions.
• Enable or disable fields based on dynamic criteria.
• Set or clear field values automatically.
• Create complex rules with AND or OR logic between conditions.

What impact will there be?¶

• Check the new Decision Tree tab in field configuration.
• Create if-then rules with multiple conditions and actions.
• Use complex expressions such as [field.name] equals "value" or [field.number] greater than 100.
• Configure conditional field interactions without custom code.

What actions do I need to take?¶

1. Enable the experimental feature in settings.
2. Open the decision tree builder in field configuration.
3. Define conditional rules using the visual interface.
4. Test all rules in different scenarios to verify correct behavior.

Are there any risks I should be aware of?¶

• Being experimental, this feature may have limitations.
• Complex rule sets can affect form performance.
• Test all conditional logic thoroughly before deploying to production.
• Evaluate the order of rules carefully when multiple rules impact the same field.

User roles can be exported in a sync package¶

What is it?¶

Site Studio package export supports inclusion of Drupal user roles.

What impact will there be?¶

Drupal user roles can be included in a Site Studio sync package if necessary.

What actions do I need to take?¶

1. Select user roles that you want to include in a sync package.
2. Include or exclude user roles in a full sync package export using the Full export settings page at /admin/cohesion/sync/export_settings.

Are there any risks I should be aware of?¶

None.

Filter components by dropzone¶

What is it?¶

Site Studio provides a filter for the component list by dropzone. This feature makes it easier to identify components that can use tagging.

What impact will there be?¶

Site builders can filter components by all components, components with dropzones, or components without dropzones. This filter helps identify components that benefit from tagging and works alongside existing filters.

What actions do I need to take?¶

No action is required. The component list interface includes the new filter.

Are there any risks I should be aware of?¶

None.

Bug fixes¶

Drush 13 compatibility for --diff option¶

What is it?¶

This fix addresses an error that occurred when using the drush sitestudio:package:import --diff command in Drush 13 or higher.

What impact will there be?¶

The --diff option works with the drush sitestudio:package:import command without compatibility errors.

What actions do I need to take?¶

No action is required.

Are there any risks I should be aware of?¶

None.

WYSIWYG editor button styles match active theme¶

What is it?¶

This fix resolves an issue where the WYSIWYG editor displayed incorrect button styles when using multiple Cohesion subthemes.

What impact will there be?¶

Button styles in the WYSIWYG editor match the current page theme, providing accurate previews.

What actions do I need to take?¶

No action is required.

Are there any risks I should be aware of?¶

None.