[Resolved] String Translations present/correct in l10n.php files and Database, but not displayed as translated ...

Problem:
The client reported an issue where string translations are correctly present in l10n.php files and the database but are not displayed as translated on the French or German versions of their website. The problem appears randomly, with about 90% of strings correctly translated and 10% remaining untranslated. The client suspects a conflict between l10n.php, .json, and .mo files in the /wp-content/languages/wpml folder.
Solution:
We suggested that the issue might be due to the use of multiple text domains within the same plugin, which can complicate the translation process. WordPress guidelines recommend using a single, consistent text domain per plugin for proper localization. For more details, refer to the official WordPress Plugin Handbook.
Additionally, our second-tier support team advised loading all text domains using the

load_plugin_textdomain

function. Here is an example of how to implement this:

load_plugin_textdomain('leadup-frontend', false, dirname(plugin_basename(dirname(__DIR__))) . '/languages');

load_plugin_textdomain('leadup-admin', false, dirname(plugin_basename(dirname(__DIR__))) . '/languages');

If there are more text domains, they should add new lines accordingly.

If this solution does not resolve the issue or seems irrelevant due to updates or different circumstances, we highly recommend checking 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 problems persist, please open a new support ticket.