Viewing Non-Localized Fields in Single Locale Mode

Previously, non-localized fields were hidden in the editorial interface when selecting a single non-default locale. To provide a more intuitive experience, these fields will now always be visible, regardless of the locale you’re viewing. This update makes content management more predictable and aligned with Locale-Based Publishing.

Adjusting Asset Validation in Locale-Based Publishing

We’ve refined asset validation within Locale-Based Publishing. Initially, publishing an asset required a file upload for every locale—an approach that was inconsistent with the Content Delivery API. To align with expected behavior, only the default locale now requires a file upload for publishing. These improvements create a more consistent localization workflow.