Issue in translation of metafield

Retired Boards Appdev Metafields
,

Topic summary

Issue: Rich text product metafield (“care details”) fails on the German (“de”) domain, which instead shows a multiline metafield. The goal is to display only the rich text metafield across markets; adding a translation didn’t fix “de.”

Context: Shopify rich text metafields are stored as JSON (a structured data format using braces and brackets). If the JSON is altered or invalid after translation, Shopify may reject it, preventing display/save.

Tools/experiences: Langify is being used; reports indicate it struggles with rich text JSON, producing broken structures that require manual fixing (comparing to the English source).

Guidance: Use a code editor (e.g., VS Code) to pretty-print and inspect JSON for missing brackets or commas; validate with an online JSON validator. Another option is jsoneditoronline.org (live errors, auto repair). In Langify, “Import content from original” then “Translate JSON Object” to edit values while avoiding changes to non-translatable keys (e.g., type keys like “text”).

Caveat: Auto-translate/auto-repair may still yield JSON invalid for Shopify; proceed carefully.

Status: No confirmed resolution; actions focus on validating JSON and limiting key changes. Images/screenshots illustrate tool steps.

Summarized with AI on December 28. AI used: gpt-5.
1

Hi,

First i wanted to know can we translate and localize the rich text metafields?

Second I am facing some issues regarding the references of metafiels i.e.. I have two product metafields by the name of care details . one is of rich text and other one is of multiline.

My store is live on multiple markets. The issue is that the rich text metafield of care details is beign pulled/shown on the store front end of all domains except for “de” domain, While the multiline meta field of care detail is somehow being pulled/shown to the store frontend of “de” domain. I want to show only rich text metafield, I ve tried adding the translation agains it but no luck it sttill pulls/shows only the multiline care detail metafield.

1 Like
2

What are you using to translate this metafield?

The problem is that rich text fields are saved in JSON format on Shopify backend. I assume that if the JSON data has not been translated properly or it has been altered, then Shopify won’t accept it and therefore it won’t be shown/saved.

We use Langify which does have problems translating rich text. The translation of the JSON is all over the place. I find myself manually re-structuring the minified JSON to be able to save it onto Shopify through Langify (comparing it against the english version).

I hope this helps.

2 Likes
3

Hi Jesusg,
Could you please guide me on how to re-structuring the minified JSON to be able to save it onto Shopify through Langify?

1 Like
4

Hi Nehall.
This is not an easy task since the data can be long. Usually the problem is missing closing brackets { } or or commas.
It is better to use a free code text editor for this such as ‘VS Code’ (probably the best there is). Then break the text into lines and indentations like this JSON example:

{
  "squadName": "Super hero squad",
  "homeTown": "Metro City",
  "formed": 2016,
  "secretBase": "Super tower",
  "active": true,
  "members": [
    {
      "name": "Molecule Man",
      "age": 29,
      "secretIdentity": "Dan Jukes",
      "powers": ["Radiation resistance", "Turning tiny", "Radiation blast"]
    },
    {
      "name": "Madame Uppercut",
      "age": 39,
      "secretIdentity": "Jane Wilson",
      "powers": [
        "Million tonne punch",
        "Damage resistance",
        "Superhuman reflexes"
      ],
    },
    {
      "name": "Eternal Flame",
      "age": 1000000,
      "secretIdentity": "Unknown",
      "powers": [
        "Immortality",
        "Heat Immunity",
        "Inferno",
        "Teleportation",
        "Interdimensional travel"
      ]
    }
  ]
}

By doing this you might suddenly realise there are characters missing. Just be aware that data is ‘nested’.
You can also use a free ‘JSON online validator’ (there are many if you search for it). This validator might give you clues of what the problem is or if it has been resolved.
I hope it helps.

1 Like
5

@jesusg @Nehall

You can also use https://jsoneditoronline.org/ which also gives you helpful JSON errors on the fly and offers an Auto repair option to automatically fix any JSON-related issues

json editor auto repair
json editor auto repair1815×1863 59.2 KB

If you’re using Langify you can translate or edit JSON Metafields as well but without touching the JSON code structure (except for the keys) by hovering over the grey caret and clicking on “Import content from original” to copy the whole code from left to right

import content from original langify
import content from original langify3259×1124 48.1 KB

Then click on the “Translate JSON Object” Icon in the top right corner of the Langify editor

json edit button metafield langify
json edit button metafield langify3259×1125 63.2 KB

There you’ll be able to edit or manually translate the JSON Metafield (almost) without touching the code.
Unfortunately, there you can also translate some JSON keys that shouldn’t be translated like the “text” type in my example

langify JSON editor labels types
langify JSON editor labels types2246×1844 97.9 KB

However, if you only change or translate the fields that you know for sure you can change for example the labels then there shouldn’t be any issues with this approach.

6

@michaelivanov_1
The initial problem is that Langify translations result in a JSON with bad structure. I think it does not matter what button you press to auto-translate on the Langify app, you can get a bad result.

https://jsoneditoronline.org/ seems like an interesting tool but it’s not perfect. Automatic fixes might not put characters in the right place resulting in a wrong Shopify structure. Tested.

1 Like