Problem: The client was unable to translate the Divi theme's Global Header and Global Footer using WPML. When attempting to add these items to the Translation queue, the queue remained empty with the Classic Translation Editor, and a critical error occurred with the Advanced Translation Editor. Solution: We checked the issue and discovered that some WPML tables in the database were missing keys, such as
wp_icl_translate
and
wp_icl_translate_job
. We manually created the missing keys for the client. We then asked the client to try translating the templates again to see if the problem was resolved.
If you're experiencing similar issues with translating Divi's Global Header and Global Footer, we recommend checking your database for missing keys in WPML tables and creating them if necessary. However, please note that this solution might be outdated or not applicable to your case. If the issue persists, we highly 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 is trying to create a bilingual homepage with Divi and WPML but encounters an issue where the 'Translations queue' shows 'No Data' after attempting to add a translation for the homepage. The client also wants to have an English page 'Home' and a corresponding French page with a different design.
Solution: 1. Ensure that the client's user account is added as a translator with the correct language pairs (English to French and French to English) in WPML > Translation Management > Translators tab. For more information, check the guide on how to set up local translators and language pairs. 2. If the client intends to create a different design for the second language and not just translate content, they should follow the guide on how to use manual translation to translate the page manually.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we 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 you still need assistance, please don't hesitate to open a new support ticket. For further assistance, you can reach out to us on the WPML support forum.
Problem: The client wants to add a space between the native language name and the language name in the current language in the WPML language switcher. Solution: We recommend adding custom CSS to create the desired space. You can do this by navigating to WPML → Languages → Language switcher options and inserting the following CSS in the Additional CSS text area:
.wpml-ls-display {
margin-left: 5px;
}
If this solution does not work for you, or if it seems outdated or irrelevant to your case, please do not hesitate to open a new support ticket. We also 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.
