If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 the problem persists, please open a new support ticket.
Problem: The client is experiencing an issue where translations appear correctly when the 'Look for strings while pages are rendered' option is enabled in WPML > String Translation, but appear differently when the option is disabled. Solution: We recommend the following steps to address the issue: Basics: - Add the textdomain in 'Localization options > Automatically load the theme's .mo file using 'load_textdomain'' under WPML > Theme and plugin localization. - Generate the MO file from WPML > Support > Troubleshooting > 'Show custom MO Files Pre-generation dialog box' option. - Ensure that the DB charset is configured under config.php to utf8mb4. - Go to WPML > Languages > Edit languages and re-save the settings. - Delete the strings completely, register them again, and retranslate. - Visit WPML > Support > troubleshooting and try all the suggested actions: https://prnt.sc/rqcSNCt3DVLY Advanced: - Check how these strings are called in your code and change the domain of the string. - Scan and re-translate strings via WPML String translation. - Check what the plugin uses to load the textdomain. These steps should help resolve the issue, which is likely related to incorrect code or a compatibility issue.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. We also 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. For further assistance, you can contact us directly at the WPML support forum.
