From 5fa8f69e10c547a83da488c8f4f9aa145163a8d3 Mon Sep 17 00:00:00 2001 From: Anthony Bouch Date: Mon, 10 Apr 2023 13:34:52 +0700 Subject: [PATCH 1/2] docs: localization warning for existing data --- docs/configuration/localization.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/configuration/localization.mdx b/docs/configuration/localization.mdx index a2f7779d93f..ad8b99d4457 100644 --- a/docs/configuration/localization.mdx +++ b/docs/configuration/localization.mdx @@ -72,6 +72,15 @@ All field types with a `name` property support the `localized` property—even t Enabling localization for field types that support nested fields will automatically create localized "sets" of all fields contained within the field. For example, if you have a page layout using a blocks field type, you have the choice of either localizing the full layout, by enabling localization on the top-level blocks field, or only certain fields within the layout. + + Important: +
+ When converting an existing field to or from `localized: true` the data + structure in the document will change for this field and so existing data for + this field will be lost. Before changing the localization setting on fields + with existing data, you may need consider a field migration strategy. + + ### Retrieving localized docs When retrieving documents, you can specify which locale you'd like to receive as well as which fallback locale should be used. From 013c96f0db79b3c56b21901174738d7fb90ada7d Mon Sep 17 00:00:00 2001 From: Anthony Bouch Date: Mon, 10 Apr 2023 13:37:27 +0700 Subject: [PATCH 2/2] docs: fixed sentance error in warning --- docs/configuration/localization.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration/localization.mdx b/docs/configuration/localization.mdx index ad8b99d4457..3e90019b26a 100644 --- a/docs/configuration/localization.mdx +++ b/docs/configuration/localization.mdx @@ -78,7 +78,7 @@ All field types with a `name` property support the `localized` property—even t When converting an existing field to or from `localized: true` the data structure in the document will change for this field and so existing data for this field will be lost. Before changing the localization setting on fields - with existing data, you may need consider a field migration strategy. + with existing data, you may need to consider a field migration strategy. ### Retrieving localized docs