Translations
The six languages the addon ships with, how to override a string, and the one rule to follow when translating widget names yourself.
What ships
English, plus five fully translated locales:
| Locale | Language |
|---|---|
es_ES | Spanish |
de_DE | German |
fr_FR | French |
it_IT | Italian |
nl_NL | Dutch |
Every string is translated in all five — panel labels, control descriptions, frontend text and admin messages. The glossary matches the core's, so setting is Fassung in German in both plugins, not two different words on the same screen.
How the language is chosen
WordPress decides. Set your site language in Settings → General and the addon follows, exactly like any other plugin. Multilingual plugins that switch the locale per request are honoured too.
If a locale has no translation the addon falls back to English rather than showing untranslated keys.
Overriding a string
The addon uses the standard WordPress translation system, with the text domain nivosync-elementor, so any tool that works for other plugins works here:
- Loco Translate is the usual choice. It finds the addon, lets you edit strings in the browser and saves the override into
wp-content/languages/plugins/where updates cannot overwrite it. - Poedit if you prefer editing
.pofiles directly.
Adding a language we do not ship
Copy languages/nivosync-elementor.pot into your translation tool, translate, and save the result as nivosync-elementor-{locale}.po plus its compiled .mo in wp-content/languages/plugins/.
A .po without its compiled .mo does nothing — WordPress reads the .mo. Loco Translate compiles automatically; if you use Poedit, make sure "compile on save" is on.
The rule for widget names
If you are translating the widget titles yourself, keep them short — around two words per line.
Elementor's widget panel renders each name inside a small tile. A long translation wraps awkwardly or gets clipped, and a panel of clipped names is genuinely hard to use. The shipped translations follow this rule deliberately, sometimes choosing a shorter word over a more literal one.
The CSS forces a line break as a safety net, but it cannot invent space that is not there.
What is not translated
Data from your catalogue: shape names, colour and clarity grades, lab names. Those come from the Nivoda feed through the core, and the core formats them. If you need shapes localised, that is a core setting, not an addon one.