#Smartling app changelog

#2026-02

Improvements

Security - Next.js dependency updated to address CVE-2025-66478.

Fixes

Asset uploads skipped in certain component translations – While translating content that contained image assets inside components with no translatable text, the asset file upload was skipped. This left localized assets stuck in the ASSET_CREATE_PENDING state and prevented publishing. All referenced assets are now uploaded during sync, even when the surrounding component has no translatable fields.
String array translations missing or incorrect – Localized string arrays could be split into multiple Smartling segments or returned in an unexpected structure, causing translations to appear incorrectly or not at all in Hygraph. String arrays are now sent as single translation units and properly unwrapped when updating content.
Smartling tab error for models with acronyms in API IDs – Selecting models with acronyms in their API IDs (for example, FAQItem) could trigger a Failed to fetch entries error and a GraphQL error field 'FAQItem' is not defined due to incorrect field name generation. Acronym casing is now preserved so entries load correctly.

#2026-01

Fixes

Empty Smartling jobs when title field API ID was missing – Submitting entries for translation could create Smartling jobs without content if the model did not include a configured title field API ID. The app now handles this case correctly so content is always included in the translation job.
Translations not appearing in Hygraph after successful sync – In some cases, sync completed successfully but translations were not visible in the editor. This occurred because Smartling job files were missing id and __typename fields for component union items. These fields are now included so translations can be applied correctly.
Missing localized assets after re-importing Smartling jobs – Re-importing localized jobs could result in image assets appearing greyed out or missing in non-default locales. Assets nested inside deeply structured components were not always uploaded. Nested asset references are now correctly detected and uploaded so localized images appear in all locales.
Incorrect entry selection when switching models – Changing the selected model did not reset entry selection, which could cause the selection count or chosen entries to be incorrect. Entry selection now resets when the model changes and is tracked using entry IDs instead of indices.
Import failures caused by empty asset list items – Empty asset translations within list or component array fields could cause import errors. These empty entries are now skipped so imports complete reliably.

#2025-11

Improvements

Clear section and field context in Smartling exports – With smarter key and instruction generation, Smartling exports now include clearer section and field context, making translations easier to understand.
Preserved localized assets – When reuploading assets, existing localized files are retained instead of being overwritten.

Fixes

Complete export coverage – Entries now export with all nested components and Rich Text content included.
Accurate filter counts – Adjusting Smartling search filters no longer leaves behind an incorrect or stale selection count.
Reliable asset array handling – Empty asset arrays within component arrays no longer cause Smartling import errors.

#2025-10

Improvements

Asset translation support – You can translate assets directly.
Smartling job updates – When updated strings are pushed to an existing Smartling job, they show the Awaiting authorization status.
Rich text translation – Rich text fields in both basic and modular components are translated.

#2025-09

Improvements

Stale translation detection – Outdated entries are clearly highlighted, with filters to view All, Only Outdated, or Only Up to Date translations.
Enhanced navigation – Edit links for entries open in a new tab for a smooth workflow.
Support for modular components – Fixed issues that previously caused crashes during import or export.
Better error handling – Clearer messages help you troubleshoot issues faster.

#2024-11

Fixes

Boolean exports - Boolean fields are no longer included in exports. Previously, exported boolean fields (true/false) were translated to strings, which resulted in import failures.

#Smartling app changelog

#2026-02

Improvements

Security - Next.js dependency updated to address CVE-2025-66478.

Fixes

Asset uploads skipped in certain component translations – While translating content that contained image assets inside components with no translatable text, the asset file upload was skipped. This left localized assets stuck in the ASSET_CREATE_PENDING state and prevented publishing. All referenced assets are now uploaded during sync, even when the surrounding component has no translatable fields.
String array translations missing or incorrect – Localized string arrays could be split into multiple Smartling segments or returned in an unexpected structure, causing translations to appear incorrectly or not at all in Hygraph. String arrays are now sent as single translation units and properly unwrapped when updating content.
Smartling tab error for models with acronyms in API IDs – Selecting models with acronyms in their API IDs (for example, FAQItem) could trigger a Failed to fetch entries error and a GraphQL error field 'FAQItem' is not defined due to incorrect field name generation. Acronym casing is now preserved so entries load correctly.

#2026-01

Fixes

Empty Smartling jobs when title field API ID was missing – Submitting entries for translation could create Smartling jobs without content if the model did not include a configured title field API ID. The app now handles this case correctly so content is always included in the translation job.
Translations not appearing in Hygraph after successful sync – In some cases, sync completed successfully but translations were not visible in the editor. This occurred because Smartling job files were missing id and __typename fields for component union items. These fields are now included so translations can be applied correctly.
Missing localized assets after re-importing Smartling jobs – Re-importing localized jobs could result in image assets appearing greyed out or missing in non-default locales. Assets nested inside deeply structured components were not always uploaded. Nested asset references are now correctly detected and uploaded so localized images appear in all locales.
Incorrect entry selection when switching models – Changing the selected model did not reset entry selection, which could cause the selection count or chosen entries to be incorrect. Entry selection now resets when the model changes and is tracked using entry IDs instead of indices.
Import failures caused by empty asset list items – Empty asset translations within list or component array fields could cause import errors. These empty entries are now skipped so imports complete reliably.

#2025-11

Improvements

Clear section and field context in Smartling exports – With smarter key and instruction generation, Smartling exports now include clearer section and field context, making translations easier to understand.
Preserved localized assets – When reuploading assets, existing localized files are retained instead of being overwritten.

Fixes

Complete export coverage – Entries now export with all nested components and Rich Text content included.
Accurate filter counts – Adjusting Smartling search filters no longer leaves behind an incorrect or stale selection count.
Reliable asset array handling – Empty asset arrays within component arrays no longer cause Smartling import errors.

#2025-10

Improvements

Asset translation support – You can translate assets directly.
Smartling job updates – When updated strings are pushed to an existing Smartling job, they show the Awaiting authorization status.
Rich text translation – Rich text fields in both basic and modular components are translated.

#2025-09

Improvements

Stale translation detection – Outdated entries are clearly highlighted, with filters to view All, Only Outdated, or Only Up to Date translations.
Enhanced navigation – Edit links for entries open in a new tab for a smooth workflow.
Support for modular components – Fixed issues that previously caused crashes during import or export.
Better error handling – Clearer messages help you troubleshoot issues faster.

#2024-11

Fixes

Boolean exports - Boolean fields are no longer included in exports. Previously, exported boolean fields (true/false) were translated to strings, which resulted in import failures.

#Smartling app changelog

#2026-02

Improvements

Security - Next.js dependency updated to address CVE-2025-66478.

Fixes

Asset uploads skipped in certain component translations – While translating content that contained image assets inside components with no translatable text, the asset file upload was skipped. This left localized assets stuck in the ASSET_CREATE_PENDING state and prevented publishing. All referenced assets are now uploaded during sync, even when the surrounding component has no translatable fields.
String array translations missing or incorrect – Localized string arrays could be split into multiple Smartling segments or returned in an unexpected structure, causing translations to appear incorrectly or not at all in Hygraph. String arrays are now sent as single translation units and properly unwrapped when updating content.
Smartling tab error for models with acronyms in API IDs – Selecting models with acronyms in their API IDs (for example, FAQItem) could trigger a Failed to fetch entries error and a GraphQL error field 'FAQItem' is not defined due to incorrect field name generation. Acronym casing is now preserved so entries load correctly.

#2026-01

Fixes

Empty Smartling jobs when title field API ID was missing – Submitting entries for translation could create Smartling jobs without content if the model did not include a configured title field API ID. The app now handles this case correctly so content is always included in the translation job.
Translations not appearing in Hygraph after successful sync – In some cases, sync completed successfully but translations were not visible in the editor. This occurred because Smartling job files were missing id and __typename fields for component union items. These fields are now included so translations can be applied correctly.
Missing localized assets after re-importing Smartling jobs – Re-importing localized jobs could result in image assets appearing greyed out or missing in non-default locales. Assets nested inside deeply structured components were not always uploaded. Nested asset references are now correctly detected and uploaded so localized images appear in all locales.
Incorrect entry selection when switching models – Changing the selected model did not reset entry selection, which could cause the selection count or chosen entries to be incorrect. Entry selection now resets when the model changes and is tracked using entry IDs instead of indices.
Import failures caused by empty asset list items – Empty asset translations within list or component array fields could cause import errors. These empty entries are now skipped so imports complete reliably.

#2025-11

Improvements

Clear section and field context in Smartling exports – With smarter key and instruction generation, Smartling exports now include clearer section and field context, making translations easier to understand.
Preserved localized assets – When reuploading assets, existing localized files are retained instead of being overwritten.

Fixes

Complete export coverage – Entries now export with all nested components and Rich Text content included.
Accurate filter counts – Adjusting Smartling search filters no longer leaves behind an incorrect or stale selection count.
Reliable asset array handling – Empty asset arrays within component arrays no longer cause Smartling import errors.

#2025-10

Improvements

Asset translation support – You can translate assets directly.
Smartling job updates – When updated strings are pushed to an existing Smartling job, they show the Awaiting authorization status.
Rich text translation – Rich text fields in both basic and modular components are translated.

#2025-09

Improvements

Stale translation detection – Outdated entries are clearly highlighted, with filters to view All, Only Outdated, or Only Up to Date translations.
Enhanced navigation – Edit links for entries open in a new tab for a smooth workflow.
Support for modular components – Fixed issues that previously caused crashes during import or export.
Better error handling – Clearer messages help you troubleshoot issues faster.

#2024-11

Fixes

Boolean exports - Boolean fields are no longer included in exports. Previously, exported boolean fields (true/false) were translated to strings, which resulted in import failures.