Problem: The client was unable to translate a few words on a page, even after using WPML's Advanced Translation Editor. The untranslated strings were part of templates created with the Porto Templates Builder and custom Elementor/Porto Modules.
Additionally, we provided a custom XML configuration to be added in WPML settings to ensure the strings from the custom modules are available for translation:
<wpml-config>
<elementor-widgets>
<widget name="porto_archive_posts_grid">
<fields>
<field type="ID of the template">builder_id</field>
</fields>
</widget>
</elementor-widgets>
</wpml-config>
The client was instructed to: 1) Go to WPML>>Settings>>Custom XML Configuration. 2) Add the provided WPML language configuration and save it. 3) Update the specified template to refresh the translation settings. 4) Update the translation. 5) Translate the *porto_archive_posts* id from WPML>>String Translation.
If the solution provided is not relevant due to being outdated or not applicable to your case, we highly recommend checking the related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket: Contact WPML Support.
