Understand XML Configuration

TranslateSense reads XML configuration to identify content fields that should be extracted for translation. The configuration groups rules by content type, so a Gutenberg block, an Elementor widget, and a Classic Editor custom field can each have different mapping rules.

Understand the main XML sections

• gutenberg-blocks contains rules for named Gutenberg blocks and their keys. For example, the default configuration maps the content key for core/paragraph.
• elementor-widgets contains widget rules and their fields. The default configuration maps fields such as a button’s text and nested link>url.
• custom-fields contains custom-field names that the Classic Editor mapping can process.

Review a builder’s configuration

1. Open Languages → TranslateSense when Polylang is active, or Settings → TranslateSense otherwise.
2. Select the relevant editor tab.
3. Choose Edit [EDITOR] Config to open the configuration editor for that builder. The exact editor name appears in the button label.
4. Review the block, widget, or field name and its mapped keys or paths before making a change.
5. Select Save Config to save the configuration.

Validate and test changes

TranslateSense checks that the submitted configuration is non-empty and valid XML before saving it. A syntax error prevents the save and returns an error message. XML that passes syntax validation can still point to the wrong field, so test the relevant content after saving.

Configuration changes affect the rules used for later extraction. Before changing a shared builder configuration, keep a copy of the current XML and make a focused change rather than replacing unrelated rules.

Screenshot to add: [TranslateSense editor tab and XML configuration editor]