WPML Elementor Widget Missing in Translation Editor? How to Fix It with wpml-config.xml
You can see the text on the Elementor page. You can edit it in the widget. Yet when you open WPML’s Advanced Translation Editor, the field is nowhere to be found. That wpml elementor widget missing in translation editor problem is rarely a broken translation—it usually means WPML has not been told which controls inside that custom or third-party widget contain translatable text.
Elementor widgets can store content in ways WPML cannot reliably infer on its own, especially when a widget comes from an add-on or custom development. The fix is often a small wpml-config.xml configuration file that registers the relevant widget fields with WPML. Once those fields are declared and the page’s translation package is refreshed, the missing content can finally appear where it should.
Why Is an Elementor Widget Missing from the WPML Translation Editor?
How WPML reads Elementor content for translation
A widget can be visible on the page and still be invisible to WPML. That is the crucial distinction behind a wpml elementor widget missing in translation editor report. Elementor stores each widget’s controls, content, and layout choices as structured page data. WPML does not simply scan the rendered front end for every string it finds; instead, it creates a translation package from fields it knows are translatable.
Native Elementor widgets are generally registered correctly, so a Text Editor or Heading field usually appears automatically. Custom widgets and third-party Elementor add-ons are different. Their developer must declare which control IDs contain text and how WPML should handle them. Without that declaration, WPML may safely ignore the value rather than risk translating a URL, CSS setting, ID, or other non-text configuration.
Common reasons widget text does not appear
- Unregistered custom controls: the widget’s text field has not been declared in its WPML configuration.
- Incorrect control IDs: the ID in the widget code and the ID declared for WPML do not match exactly.
- Repeater fields: text inside slides, tabs, pricing rows, or other repeaters needs its own nested configuration.
- Copy-only settings: a field configured to copy will be transferred from the original rather than offered for translation.
- Version or workflow issues: outdated Elementor, WPML, or addon versions can affect compatibility, as can opening an old translation job or the wrong translation mode.
Confirm that the problem is limited to one widget
Start with a quick control test: add a native Elementor Text Editor widget, enter a distinctive phrase, and update the page. If that phrase appears in WPML’s Translation Editor, the overall connection is working. The issue is likely isolated to the missing widget.
Next, identify its source: Elementor core, a third-party addon, or custom theme/plugin code. Finally, check where the missing wording originates. Text entered directly in the widget settings can be registered through wpml-config.xml; text generated from a shortcode, dynamic tag, template, database field, or external feed requires a different translation path. That diagnosis prevents a common mistake: trying to configure WPML for text the widget never actually stores.
Add a wpml-config.xml File for the Missing Elementor Widget
Find the Elementor widget name and control IDs
A wpml elementor widget missing in translation editor issue is usually not a WPML failure; WPML simply does not know which custom-widget fields contain language. Open the widget class and find the value returned by get_name(). Then record every internal control name passed to add_control() or add_repeater(). These identifiers, not labels such as “Heading” or “Button Text” shown in Elementor, are what WPML needs.
Register simple text and textarea controls
Place wpml-config.xml in the custom widget plugin or child theme, preferably under version control. Do not add this mapping to page content: it is code-level widget metadata and should survive routine edits, imports, and template changes. A basic configuration can expose a heading, body copy, and button label like this:
<wpml-config><elementor-widgets><widget name=”promo-card”><fields><field id=”heading” type=”Heading” editor_type=”LINE”>translate</field><field id=”body_text” type=”Body text” editor_type=”AREA”>translate</field><field id=”button_label” type=”Button label” editor_type=”LINE”>translate</field></fields></widget></elementor-widgets></wpml-config>
Handle repeater fields and nested widget content
Repeaters need an extra mapping layer. A slider, FAQ, tab set, or feature-card widget may have one repeater ID, such as items, containing subcontrols such as title and description. Register the repeater and each text-bearing subfield using their exact IDs. Otherwise WPML may recognize the widget yet leave every individual slide or FAQ answer absent from the translation editor.
Choose the correct translation action for each field
Use translate for visitor-facing headings, descriptions, labels, and calls to action. Use copy for layout settings, spacing values, colors, and switches that must remain identical across languages. Copy-once suits a value initially shared but later editable per language. Use ignore for IDs, URLs, dynamic tags, query settings, and other technical data that translators should not touch. Registering everything is a common mistake; register only fields that need deliberate multilingual handling.
Refresh the Translation Job and Check That the Fields Appear
Clear the old translation package safely
A correct wpml-config.xml file will not retroactively rewrite a translation job that WPML has already packaged. That is why a wpml elementor widget missing in translation editor problem can persist even after you fix the configuration.
Open the original Elementor page, make a small harmless change—such as adding and removing a space in a text field—then update the page. Next, use WPML’s current Translation Management workflow to update or resend the translation. This prompts WPML to build a fresh content package and include the newly mapped widget fields. Do not edit translation-job records in the database; it is risky, unsupported, and rarely necessary.
Update caches and confirm WPML has loaded the configuration
Caching can make a successful fix look like a failure. Clear the WordPress cache, persistent object cache, CDN cache, and any host-level cache in use. In Elementor, regenerate CSS and data if your setup provides that option, then clear Elementor’s cache as well.
Reopen the translation in WPML’s Advanced Translation Editor after the page has been updated. The previously missing fields should now appear as separate translation segments. If they do not, verify that wpml-config.xml is in the active theme or plugin directory, is valid XML, and uses the widget’s actual Elementor control names.
Test the translated page on the front end
Complete or publish the translation, switch to the target language, and inspect the page rather than relying only on the editor. Check every mapped field, including repeater rows, button labels and URLs, responsive text variants, headings, and links. These details matter for usability and international SEO: a translated heading paired with an untranslated button or destination URL is still an incomplete localization.
For sites using WPML with LATW AI Translator for WPML, remember that LATW translates the fields WPML exposes in the job; the configuration fix must come first.
What to Do If the Widget Is Still Missing
Check XML syntax, file location, and identifier mismatches
A correct-looking mapping can fail because of one character. If you are still seeing a wpml elementor widget missing in translation editor problem, validate the XML first: unclosed tags, invalid nesting, and copied smart quotes can stop WPML from loading the entire configuration. Then confirm that wpml-config.xml sits in the active custom plugin or theme context, not in a child folder WPML never scans. Finally, compare every declared widget name and control key with the PHP code. WPML needs the actual widget ID and setting identifier, not the label shown in Elementor’s panel.
Rule out dynamic tags and generated content
Not every sentence visible on an Elementor page belongs to the widget’s saved settings. Text returned by a shortcode, remote API, dynamic tag, post-query loop, or template condition may be generated only when the page renders. XML cannot expose a value that is not stored in the widget data. In those cases, translate the underlying post, custom field, template, string, or source-system value instead. A useful test is simple: save a plain text value in the control and check whether it appears; if it does, the issue is likely dynamic output rather than the mapping.
Document the mapping for future widget updates
Keep the XML beside the custom widget code and treat it as part of the widget’s public interface. Retest after Elementor, WPML, or addon updates, especially when developers rename controls or replace repeater fields. Each new visitor-facing field should receive a mapping before it reaches production. That small discipline prevents a translation backlog from appearing months later.
Use an AI workflow after WPML can see the fields
For sites already running WPML, LATW AI Translator for WPML can translate page content once those widget fields are correctly exposed. It is an add-on, not a replacement for WPML, and requires an active WPML installation. In local mode, it sends content directly from WordPress to supported AI providers using your own API key; optionally, it can use LATW Cloud for background translation. The practical order matters: fix field visibility first, then automate the translation work.
Make the Widget Visible Before You Translate It
When a wpml elementor widget missing in translation editor issue appears, the translation editor is rarely the real problem. WPML can only translate fields it knows how to find. Identify the widget’s control IDs, register the text-bearing fields in wpml-config.xml, rebuild the translation job, and then check the published language version—not just the editor—to confirm the result behaves as expected.
This approach turns a frustrating one-off bug into a repeatable workflow for every custom or third-party Elementor widget on the site. Once the field mapping is in place, WPML has a reliable translation path for that content, so future updates can move between languages with far less guesswork.