Problem: The client needed to receive the "new order" admin email in just one language (English), despite the site running in five languages.
Solution: We explained that the notification email sent to the admin is always in the site's default language. If the client wants to receive the notification email in a different language, they should change the language in their user profile by navigating to "Users > Profile". After adjusting the language settings in the profile, they can use the following hook to receive emails in the language set for their profile:
We also clarified that translating fields in the email template will not affect the customer side, as the content will be shown in the translated language to the customers.
If this solution does not apply to your situation, or if it seems outdated, we recommend checking the related 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.
Problem: The client needs to modify a string in the default language (English) on their theme for mobile devices. Specifically, they want to change the text on a button from "Check" to "Book Now" on the English version of their site.
Solution: We recommend finding the string in WPML > String Translation and changing the default language for that specific string to a language that is not currently set up on the website. Here's how to do it: 1. Locate the string in WPML > String Translation. 2. Check the box to the left of the string. 3. Scroll down and change the default language of that string to a language not in use on the site, like Italian. 4. You will then have the option to add the string you want to show in English. By doing this, you can create a translation for the English language and change the default string.
Please try this solution and let us know how it goes.
Note that this solution might be irrelevant if it's outdated or not applicable to your case. If you encounter any issues or if the solution does not work for you, we highly recommend checking related 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.
Problem: The client was experiencing issues with a missing column
ate_sync_count
in the
wp_icl_translate_job
table and had errors related to automatic translation. Solution: We offered to fix the issue manually but needed the client to provide temporary access credentials (wp-admin and FTP). We emphasized the importance of making a backup before providing access and provided instructions on how to securely submit the credentials using the private response form. We also shared a video tutorial on how to submit the information.
After receiving access, we resolved the missing column issue and tested the automatic translation by creating a draft post and translating it with the Classic Translation Editor. We asked the client to test again and contact us if they needed further assistance.
Problem: The client updated the Traveler theme and encountered a warning message. They followed a post with similar error instructions, but the issue persisted. Solution: 1) We recommended closing the warning by clicking "X" and then refreshing the page to see if the warning would reappear. 2) We advised the client to check their database to ensure that the
wp_icl_strings
table exists.
Issue was resolved by clicking the "X" and refreshing the page.
If this solution does not seem relevant to your issue, please feel free to open a new support ticket with us.
Problem: The client is experiencing issues with the installation of WPML on a site using the Traveler Theme. After attempting to install WPML, the site's theme options, styles, and configurations were misconfigured. The client faced errors when accessing settings, a never-ending loop during plugin settings, and issues related to PHP version compatibility. Solution: We have resolved the issue with the workaround from this errata https://wpml.org/errata/missing-_icl_strings-_icl_string_translations-data-tables/ .
If this solution doesn't look relevant to your situation, please open a new support ticket with us for further assistance.
