If you are using Elementor Pro or a different theme with customizable theme options, you may want to set a different logo per language.
Once you translate the logo, you may need to tell WPML which logo to display on the front-end in each language. You can do this by going to String Translation and translating the logo ID. If you cannot find the logo string in String Translation, you may need to click the Translate texts in admin screens link at the bottom of the page and add the text to the String Translation table.
Problem:
The client wants to translate the text added using the CSS "content" property.
Solution:
Sorry, you can’t translate strings from the CSS section/file using the WPML >> String Translation page. However, You can use the ‘:lang’ selector before other selectors to use different CSS for different languages.
Problem: While configuring WPML, the client encountered a database error indicating that the table 'dbam4gw1njitaz.wp_icl_strings' does not exist. Solution: If you're experiencing this issue, we recommend the following steps to recreate the missing icl_tables: - First, ensure to make a full backup of your site (files and database). - Add the following code to the bottom of the functions.php file in your theme's root folder:
- Visit your site's homepage at least once. - Remove the code from the functions.php file. - Finally, remove the keys "wpml_string_table_ok_for_mo_import" and "wpml_notices" from the options table (typically wp_options, where "wp_" is your database prefix). This should resolve the error. If the issue persists or if this solution seems outdated or irrelevant to your case, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket at WPML support forum for further assistance.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you need further assistance, please open a new support ticket: Contact WPML Support.
Problem:
Unable to add glossary with hidden languages
Solution:
Under your site Dashboard, go to Users > Profile, Or you can go to Users > All users, Select a User to edit there you can set the "Display hidden languages" and save.
Problem: If you are trying to translate your categories and notice that the slug is automatically changed to [category]-en and it seems strange, and you are wondering if changing it back without the -en could affect your site. Solution: By default, WordPress does not allow having two categories with the same slug, so WPML adds the language code at the end. However, WPML allows you to bypass this restriction if you edit the slug manually, which it sounds like you've already done. Therefore, you can use the same slug in different languages for your translated categories.
If the solution provided is not relevant to your case, because it could be outdated or simply not applicable to your situation, we recommend open a new support ticket. We also suggest that you review the known issues, check the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If you need more help, do not hesitate to contact us at the WPML support forum.
Problem: The client is encountering a database error indicating a duplicate entry '0' for the primary key when trying to save a translation. This error suggests that AUTO INCREMENT may be deactivated on the database table.
Solution: 1. Check the
icl_translation_status
table in the database to ensure that AUTO INCREMENT is enabled. 2. If AUTO INCREMENT is not enabled, it needs to be activated. This may also require checking other WordPress tables like
wp_options
,
wp_posts
, and
wp_users
to ensure they have AUTO INCREMENT enabled where necessary. 3. If there is an entry with '0' in a table where you are trying to enable AUTO INCREMENT, you must remove that entry before you can enable AUTO INCREMENT. 4. Always ensure you have a recent and working backup before making any changes to the database.
Please note that this solution might not be relevant if it's outdated or not applicable to your case. If the issue persists, 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: If you're unable to translate certain texts that appear in the Customize and Front end sections of your site, it might be because these strings have been recognized but not yet associated with the String Translation panel. Solution: We recommend visiting WPML>>String Translation and clicking on the Translate texts in admin screens » link at the bottom of the page. Then, search for the missing strings in the Admin Texts Translation screen to see if they are listed. If you find them, please add them for translation. For more detailed guidance, refer to our documentation on Finding Strings that Don’t Appear on the String Translation Page.
If this solution does not apply because it’s outdated or not relevant 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing two issues: first, imported XLIFF translations are visible on the front-end but not within the Advanced Translation Editor (ATE). Second, the Mega Menu breaks after synchronizing menus with WPML. Solution: For the XLIFF import issue, we explained that translation services rely on the Classic Translation Editor (CTE) and it is expected that translations will not be visible in the ATE nor editable there. To resolve this, we recommend disabling the ATE in the WPML translation editor options by navigating to WPML -> Settings. Switching to the CTE may serve as a workaround. Regarding the Mega Menu issue after WPML Menus Sync, we would need more information to provide a specific solution. If you're experiencing similar issues, please note that the solution provided might be outdated or not applicable to your case. 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 the problem persists, please open a new support ticket with us for further assistance.
The properties CPT are set to ‘Translate automatically’ in WPML -> Settings. The properties were imported using WP All Import. Nevertheless, nothing happened. The properties were not automatically translated.
Solution:
Imported posts (any post type) can not get automatically translated. This is expected behavior. To get the imported posts translated automatically, you need to go to Translation Management and send the imported posts to translation.
Problem: The client is trying to synchronize the French version of their website with the English version but is encountering issues. Specifically, there are extra social media icons in the footer, a generic header message that won't update, and a news page that is not reflecting changes. Additionally, the Page Title Bar is not supposed to show up in the French version, but it does. Solution: We recommended following the steps in our documentation to ensure that the Header and Footer are translated correctly when using the Avada theme. The documentation can be found here: Translating Avada Layout Sections.
If the client is not using an Avada layout for the header, the issue might be related to setting different global options with WPML, as described in the following documentation: How to Set Different Global Options with WPML.
If these solutions do not resolve the issue, we asked the client to provide more details on how they configured the sections causing trouble, and to ensure they have a backup of their website before providing us with access to their WordPress dashboard.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket for further assistance: WPML Support Forum.
Problem:
We defined the language and were almost done, but we noticed that we made a mistake with the code of the language. We need to change it so that the permalink goes from this ../pt-br/ to .../pt/.
Please advise how can we correct this.
Solution:
To change the slug of the Portuguese language, we'll need to apply a workaround, which is to create a custom language with the code 'pt'. To do it, please follow these steps:
- Go to WPML -> Languages -> Site languages - > Edit Languages
- Click on the button "Add New Language"
- Add a custom language and make sure that the 'code' is set to 'pt' since this is what shows in the URL. Also, use a different default locale from pt_PT as this is already taken (you can use just pt. Screenshot: https://cdn.wpml.org/wp-content/uploads/2018/02/1516916-Screen_Shot_2018_02_13_at_3.23.21_PM_1.png)
Once the language is added, if you have already created your Portuguese content (pages/posts./etc.), you will need to go to WPML -> Translation Management to duplicate them from the original PT language to your new PT language:
- In the WPML -> Translation Management dashboard, make sure to switch the language to Portuguese, and select content that you want to duplicate
- In "2. Select translation options" duplicate them into the new PT language
After this, you can remove the old PT language in WPML -> Languages -> Site Languages -> Add / Remove languages.
Problem: The client is trying to export the entire site content for external translation using XLIFF but is unable to find an option to create the package without activating a listed translator, as they are using a different one not listed. Solution: We recommend that if you're the admin of the site, you should assign yourself as both a translation manager and translator. Then, you can send translation jobs to yourself and export the XLIFF files, which you can then import back after translation. Here are the steps to follow: 1. Go to WPML > Translation Management > Translators, add yourself as a translation manager by choosing "Select an existing user and set as Translator", and then do the same to Add a Translator. 2. Send the job to translation. 3. Go to WPML > Translations and download all jobs, which will include the XLIFF files. For more detailed instructions, please refer to our article on configuring XLIFF file options.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If this doesn't resolve your issue, we highly recommend checking related known issues at WPML 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 in our support forum.
Problem: The client reported a WordPress database error related to invalid data in some tables, specifically mentioning an issue with a Jetpack plugin error message that persisted even after uninstallation. Solution: We identified that the error message contained an emoji, which might have contributed to the database issue. We removed the specific message from the database, and the error did not reappear. We recommend checking your site to confirm that the error message no longer displays. If you're experiencing similar issues, we suggest removing any special characters or emojis from database entries that could potentially cause errors.
Please note that this solution might be outdated or not applicable to your specific 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 was unable to see the translated versions of their pages using the language switcher. The expected translations were not appearing on the website.
Solution: We recommended the client to check the following steps: 1. Ensure the language is not hidden in WPML->Languages. 2. Verify that the translation is not in the trash. 3. Confirm that the translation is published and not set as a draft. 4. Make sure the translation is 100% complete, indicated by a pencil icon next to the default language page.
Upon further investigation, we discovered that the client was using the Blog license of WPML, which does not support Translation Management and the 'translations' tab. These features are only available with the CMS version of WPML. We advised the client that to use the translation editor, which their contractor was using, they would need to upgrade to the CMS version. The link to the purchase page is https://wpml.org/purchase/.
As a temporary solution, we suggested that the client could go directly to Pages or Posts and add the translation manually, but they would not be able to use the translation editor without upgrading their license.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket at our support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
