The configuration #️⃣

Every time a collection type is modified (add, update, delete a field or a whole collection), the Content Transfer Setup needs to be checked and updated according to the collection types. Otherwise, the plugin won’t be able to determine whether a user wants to transfer the field or not, and consequently, it won’t let the user proceed with upload or download.

The Content Transfer Setup screen looks similar to the screen below.

Some of the fields are disabled (shown as grey). This is due to the fact that the fields are not texts. For instance, a field named Pages in the Books collection is a number and therefore doesn’t have to be translated. Similar applies, e.g., for relations.

Disabling the whole collection #️⃣

The whole collection can be disabled from transferring by toggling the switch on the right side of the collection’s name. This way, the transfer setup of the collection can be kept intact for when a user decides to transfer it later without a need to click on the fields repeatedly.

To enable localization for the field (or collection), go to Advanced Settings and make sure the checkbox named Enable localization for this field (or Content-Type) is checked.

Dynamic Zones support #️⃣

The plugin supports localization of Dynamic Zones.

In the Content Transfer Setup, a Dynamic Zone component is marked with the “infinity icon”.

In the image below, the lesson_type is a Dynamic Zone field with lesson.lecture, lesson.quiz and lesson.survey components available to choose from.

Localazy Strapi Plugin: JSON Fields Support (Beta) #️⃣

With the release of the JSON Fields Support (Beta) in the Localazy Strapi Plugin, users can now leverage advanced content structures, allowing for deeper flexibility when localizing JSON data in their Strapi projects. Here’s a breakdown of this new feature and its current limitations.

Key Features and Limitations of JSON Fields Support

1. Support for JSON Structures in Components JSON Fields can now be used in components, repeatable components, and Dynamic Zones (first-level support only). Note: This means that JSON fields located directly within a component or a repeatable component are supported, but a JSON field within a nested component (i.e., a component within a component) does not currently work.

2. Deep Merging on Localized Entry Creation When creating a localized entry, JSON data with numeric, boolean, and other primitive values will be deep merged with the source entry. This ensures that non-string data types within JSON maintain their structure and values, enhancing consistency between source and localized entries.

3. Limited Regex Key Support Currently, JSON fields with keys containing the dot “.” character are not supported due to limitations with regex-based matching. We recommend using alternative key structures if you intend to localize such fields within JSON.

CKEditor 5 Strapi Plugin Support #️⃣

The plugin supports both unofficial and official versions of the CKEditor 5 Strapi plugin, providing flexibility for users leveraging CKEditor 5 for rich text content within their Strapi projects.