Multilingual Support

UMIE integrates with WPML and Polylang to handle multilingual content across all operations. Language selectors appear automatically when a supported plugin is active.

Supported Plugins

Plugin	Detection	Notes
WPML	Automatic	Full support including translation linking
Polylang	Automatic	Full support including translation linking

Both plugins use a “one post per language” model — each translation is a separate WordPress post linked through a translation group. UMIE reads and writes language data through each plugin’s native API.

Requirements

WPML or Polylang installed and active
At least 2 languages configured in the plugin settings
Post type registered as translatable (configured in WPML/Polylang settings)

When these conditions are met, language dropdowns appear automatically in the UMIE interface.

Language Selectors

Source Language

Appears in the Source panel when a driver source is selected.

Purpose: Filters which records are read from WordPress.
Default: “All Languages” (reads every record regardless of language).
Example: Select “French” to only export or migrate French-language posts.

Destination Language

Appears in the Destination panel when a WordPress destination is selected.

Purpose: Assigns a language to every imported or updated post.
Default: “Default Language” (uses the site’s default language).
Example: Select “Latvian” to import all records as Latvian-language posts.

How It Works Per Operation

Import (File/AI to WordPress)

Select a Destination Language in the sidebar.
Every imported post is assigned that language.
If no language is selected, posts are created in the site’s default language.

Export (WordPress to File)

Select a Source Language in the source panel.
Only posts in that language are included in the export.
Exported JSON includes _language and _translation_group metadata on each record.

Update (WordPress to Same Driver/Target)

Source Language filters which existing records are loaded.
Destination Language reassigns language on updated posts (optional).

Migration (WordPress to Different Driver/Target)

Source Language filters which records to migrate.
Destination posts automatically inherit the source post’s language — no manual selection needed.
Translation group links are preserved during migration.

Cloud Bridge (Cross-Site Push)

Source Language filters which records and media are included in the push package.
Language assignment on the remote site is handled by the remote site’s configuration.

Translation Groups

When you export multilingual content, each record includes:

_language — the post’s language code (e.g., en, fr, lv)
_translation_group — a group identifier linking translations together

When you re-import this data, UMIE uses these fields to automatically link posts as translations of each other. For example, if three records share the same _translation_group value but have different _language values, they are linked as English, French, and Latvian versions of the same content.

Use Case: Translating Content with AI Rewrite

You can combine multilingual language assignment with the AI Rewrite transformer to translate content during import. Here’s an example workflow for importing an English product catalog as Spanish-language posts.

Set Input Source to File and upload your English-language data.
Set Destination to WordPress, select your driver and target post type.
Select Spanish as the Destination Language in the sidebar.
Map your fields in Node View or Table View.
On the connection lines for fields you want to translate (e.g., title, description), click + and add an AI Rewrite transformer.
Enter a prompt such as: Translate to Spanish. Keep brand names and product codes unchanged.
Click Test (3) to preview translations on sample records.
Once satisfied, click Process (All) to translate the full dataset.
Click Start Import — posts are created with translated content and assigned to Spanish.

For fields that combine multiple sources, use template variables in the prompt:

Translate to Spanish:
Product: {{title}}
Description: {{description}}

Tips

Language selectors reset each session. They are not saved between page loads — select the desired language each time you start an operation.
Post type must be translatable. If language dropdowns appear but have no effect, verify the post type is registered as translatable in your WPML or Polylang settings.
WPML auto-translation warning. If WPML’s “Translate Everything Automatically” mode is enabled, importing original-language posts can trigger automatic translation jobs for all secondary languages, consuming your WPML translation credits. Disable this setting before running bulk imports.
One language per import run. To import content in multiple languages, run separate import operations — one per language — using the same source file with language-specific records.