TranslateSense reads translatable text from Elementor widget settings and uses its Elementor XML rules to identify which fields should be translated. If a field is missing from the translated page, first check whether the text was extracted from the source page, then check the field mapping and the saved target page.
Confirm the source content and widget
- Open the original page in Elementor and save its latest changes.
- Confirm that the missing text is stored in a widget setting and that the source page displays the expected text.
- Run a small test with one affected widget or a simple test page. Check whether other text on the same page translates correctly.
- After translation, open the target page in Elementor and confirm that you are checking the expected target-language post.
Review Elementor field mapping
TranslateSense uses Elementor XML rules to map widget setting paths to translatable fields. Open the TranslateSense admin screen and review the Elementor and XML Editor areas. Check the rule for the affected widget and field path, including nested settings or repeater fields where applicable.
- If the field is not mapped, use the available configuration or mapping tools to identify the correct widget field.
- Check that the field is not deliberately excluded from translation.
- Save the configuration if you have permission to manage the shared XML rules. If you cannot save those settings, ask a site administrator to review them.
- Retest the same field after confirming the mapping.
TranslateSense can discover some unmapped candidate text fields while parsing Elementor content. Saving newly discovered shared rules requires the appropriate administrator capability or an explicitly permitted filter, so discovery does not guarantee that every field has been permanently added to the configuration.
Check the result before changing more settings
Compare the source and target widget settings. If the source text is present but the target value is unchanged, the field mapping or translation result needs investigation. If the translated value exists in the target settings but does not appear on the frontend, check Elementor’s saved page data and the page’s display conditions or cache separately. Do not edit unrelated XML rules until the affected widget and field are identified.
If the issue affects all translation tools rather than only Elementor fields, see Why is TranslateSense not available in the editor?. For general provider errors, see Why does a provider connection fail?.
Screenshot to add: [TranslateSense Elementor widget field mapping in XML Editor]