Last updated: 20th October 2025
Released: 20th October 2025

• Highlights
• Bug fixes

Highlights¶

CSS Property Search for Style Builder¶

What is it?¶

Site Studio includes a search function in Style Builder that helps you quickly find CSS properties by typing in a search bar. The search understands CSS property names, aliases, and technical terms to help you locate the properties faster.

What impact will there be?¶

• A search input with the placeholder Search CSS properties... appears in the Properties menu.

• You can search using standard CSS property names, such as font-family or background-color.
• Search also works with common aliases, such as bg for background or w for width.
• Technical terms, such as typography or flexbox, find relevant property groups.
• Results display property groups that match your search term.
• The system displays No results - try Custom CSS when no results are found.

What actions do I need to take?¶

• Use the search bar in the Properties menu to quickly find CSS properties.
• Try to search with terms such as color, spacing, font, background, or layout.
• Use the clear button (x) or press Escape to clear your search.
• Consider to use the Custom CSS option when no matching properties are found.

Are there any risks I should be aware of?¶

• Search results are based on property names and descriptions.
• Very specific or custom terms may not match existing properties.
• The search feature requires that JavaScript is enabled.

CSS Grid Selectors for Style Builder¶

What is it?¶

Site Studio includes CSS Grid support in Style Builder, which allows you to create grid-based layouts through the UI. This feature provides:

• Grid container controls: Configure grid containers with properties such as grid-template-columns, grid-template-rows, grid-gap, and alignment options.
• Grid item controls: Position and size grid items using grid-column, grid-row, grid-area, and alignment properties.
• Enhanced validation: Robust form validation ensures proper grid syntax and prevents invalid configurations.

What impact will there be?¶

• New CSS Grid layout options are available in the Style Builder interface.
• Existing layouts that use other positioning methods continue to work unchanged.

What actions do I need to take?¶

For developers:

• Familiarize yourself with the new CSS Grid options in the Style Builder.
• Review existing layouts that can benefit from grid-based approaches.
• Test grid layouts across different screen sizes and browsers.

For Content Editors:

• Explore the new Grid Container and Grid Item options in the Layout section of Style Builder.
• Experiment with grid-based layouts for more flexible content arrangements.

Are there any risks I should be aware of?¶

• CSS Grid has excellent modern browser support, but it may require fallbacks for older browsers. Test complex grid layouts thoroughly across target browsers.

Bug fixes¶

Component Form Builder: Field Group Data Preservation with Conditional Visibility¶

What is it?¶

Site Studio fixed an issue where existing field values in field groups were lost when conditional visibility rules were applied to parent containers. This occurred when updating an existing component with new conditional field groups, which caused previously saved data in existing field groups to not be retained or displayed after the component form was opened.

The fix ensures that nested conditional fields maintain their values when parent containers are hidden or displayed, which prevents data loss during component form updates.

What impact will there be?¶

• Field values in conditional field groups are properly preserved when parent containers are hidden or displayed based on conditional visibility rules.
• Existing component data remains intact when you add new conditional field groups to an existing component.
• Nested conditional fields maintain their values during parent condition changes.
• You do not need to remove conditional visibility as a workaround to retain field data.

What actions do I need to take?¶

• No action is required. The fix is automatic and preserves all field values in components with conditional visibility. If you previously removed conditional visibility rules as a workaround, you can now safely re-apply them.

Are there any risks I should be aware of?¶

• None. This fix prevents data loss and improves the reliability of conditional field groups.

Components list builder: reordering components¶

What is it?¶

Site Studio includes fixes for the Components administration list to ensure drag-and-drop and row-weight reordering work reliably in nested accordion structures.

What impact will there be?¶

• Drag-and-drop and row-weight reordering functionality for Components.

What actions do I need to take?¶

• No action is required.

Are there any risks I should be aware of?¶

• None

Orphaned Layout Canvas revision cleanup¶

What is it?¶

Site Studio provides safe cleanup of orphaned layout canvas revisions through two methods:

• Configurable automatic cleanup (disabled by default): A cron job can run at configurable intervals to identify and clean up orphaned layout canvas revisions from any entity type using layout canvas that may exist in the database. Choose from hourly, daily, every 2 days, weekly, or monthly intervals. This feature is off by default and must be enabled in settings.
• Manual cleanup command: A Drush command sitestudio:cleanup-orphans is available to manually identify and clean up existing orphaned revisions from any entity type using layout canvas.

What impact will there be?¶

• Database table size is reduced on sites with many orphaned layout canvas revisions.The cohesion_layout_revision table is cleaned up based on your configured interval or manual Drush commands.
• Performance improvements include better resource management and reduced memory usage during cleanup operations.
• Content operations, such as translations and component duplication, are not affected by cleanup processes.

What actions do I need to take?¶

• Initial cleanup (one-time):

  1. Run drush sitestudio:cleanup-orphans --dry-run to see the number of orphaned revisions that exist on your site.

  2. Run drush sitestudio:cleanup-orphans to clean them up.

• Configuration (optional to enable automatic cleanup):

  1. Go to /admin/cohesion/settings and enable Delete orphaned revisions on cron.

  2. Select your preferred interval.

• Ongoing maintenance:

  • Orphans are cleaned up automatically based on your configured interval, or you can run the Drush command manually as needed.

Are there any risks I should be aware of?¶

• The cleanup command and cron job permanently delete orphaned revision data. Always run with --dry-run first to review what is deleted. Consider backing up your database before you run the initial cleanup.